Page 1 of 1
Feature request: In conditions/scripts, always default to the last quest used
Posted: Sat Jun 08, 2019 10:48 pm
by AoF
I find that I usually am working on one quest at a time. Therefore, it's two extra clicks every time I'm writing a condition to select my quest or it's entry: One click to open the drop down, one click to pick the right quest. Since I think I usually want to pick the last quest I've picked, it would be nice if the dropdown always defaulted to the last one.
If this is going to be implemented, I think it should be one shared variable between conditions and scripts. That way, if I pick a quest in a condition, it'll be preselected when I pick a quest for a script, and vice versa. Same thing applies to whether I'm picking a quest, or a quest entry.
To clarify, I'm talking about this part of the UI:
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sun Jun 09, 2019 12:14 am
by Tony Li
Good idea! I'll add it to the list.
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sun Jun 09, 2019 1:38 pm
by AoF
Cool, thanks.
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Fri Jun 14, 2019 11:18 pm
by Tony Li
This feature is in hotfix 20190614 and will be in version 2.1.8.
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sat Jun 15, 2019 12:58 am
by AoF
Nice, thank you
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sat Jun 15, 2019 9:12 am
by Tony Li
Glad to add this one! I put together a short example for someone yesterday, and this feature already came in handy for myself.
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sat Jun 15, 2019 2:02 pm
by AoF
Sorry I didn't say this earlier, but consider enhancing this to apply to the wizard's first dropdown. I *think* if I selected a variable last time, I'm more likely to select a variable next time. Same goes for a quest or a quest entry. I'm not as confident that this request is the right solution to the problem, but I do know that Quest is picked by default and it's a relatively rare choice for me. I'm usually picking Variable or Quest Entry instead.
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sat Jun 15, 2019 2:48 pm
by Tony Li
What do you mean by the wizard's first dropdown? I think this should already work.
For example, say I edit node 1 and use the Conditions wizard to set Variable > PlantedCrops > Is > True.
Then if I edit node 2, click "..." to open the Script wizard, and click "+", the first dropdown will start at Variable > PlantedCrops.
Currently it forgets the value when you recompile code or switch into play mode. But otherwise it should remember your last choice. In version 2.1.8, I'll extend it to remember the choice even after recompiling code or switching into play mode.
Re: Feature request: In conditions/scripts, always default to the last quest used
Posted: Sat Jun 15, 2019 2:55 pm
by AoF
Tony Li wrote: ↑Sat Jun 15, 2019 2:48 pm
In version 2.1.8, I'll extend it to remember the choice even after recompiling code or switching into play mode.
I think that's the feature I'm asking for. Thanks!