RFC: About reworking the Non-Civilopedia Tutorials about unciv

[yairm210]

I am 100% in favor
Better tutorials are something that I've failed for years to make any real dent on, and this looks like a good way forward
Not sure we need "choices" though

[yairm210]

I don't think we need a "unavailable if X is complete" on each of them, since that's the default state for a tutorial 🤔

[SomeTroglodyte]

Better tutorials are something that I've failed for years to make any real dent on

Same here. There's code in master that was meant as preparation to unify all three kinds, way back to early Uniques or even before. The special treatment in WorldScreen and Civilopedia - I once had a vision they could all go. Now that we have triggers and events, the Event context seemed closer to these, which I partially dislike very much since - unify with other Tutorials now how now... Probably make the popup type another presentation type, and leave the pedia-only ones where they are, change pedia caption maybe to something more general, and really give Events some space in pedia?

Not sure we need "choices" though

Mad modders - can be quite useful I think. I don't have the imagination to make something out of the increased possibilities, but maybe they have. That's unfinished - I mean to make the existence of choices optional entirely, all presentation modes (dunno if the code is already there or not). No choices = normal float or alert with a default OK, and click-behind enabled. Choices exist = alert becomes modal. +documentation. +allow no-choice events that still trigger something, same as having only one choice but tighter presentation...
... Having them in a floating tut - as I said, I have the experiment in that json to allow simply clicking away with a "Got it" button the one that most often stays a long time, and can't be intentionally cleared quickly and reliably otherwise: Meet another civ. Works well. In the end, I believe we can allow modders to "invent" new "tutorial completed" keys and manage them with triggers, and say, have "offer" type time-spanning events.

I don't think we need a "unavailable if X is complete" on each of them

Definitely in the "unfinished" corner - to think about that, what's redundant, where loopholes may be or not....