Events appendable via .jsons?

[Toma400]

However this could be really tough from my perspective, events being created through .jsons (probably in worldpack? Or new type? Or statpack?) with custom behaviours could be AMAZING for modding possibilities. Currently those are put inside .py file and somehow "hardcoded", but they are not big thing yet, so I can change how those behave quite easily.

Having those easily appendable then could be really good decision.

[Toma400]

One of the ideas which can be good workaround for it is merging forged_events with what was earlier draft-called as dialogue events, or using similar system to implement the first one "on the fly". To explain:

• DIALOGUE EVENTS were meant to exist in dialogue and be just keys appended to lists, so devs & modders could know which dialogues were already read/made, putting conditions for events.
• FORGED EVENTS are similar to what Minecraft Forge API makes: in specific situation, Forged Event is added to the list and can be tracked and/or used by script of respective contents/filename (to be set in stone in development later).

Modding support can either switch Forged Events e n t i r e l y into .json use (hence removing a lot of code from scripts.py), or make it so you can have vanilla events (scripts.py) and some handlers done via .jsons. Or! It can be done on-the-fly just like dialogue events, so as additional key in .json which will create either just event stringed name, or even customise some behaviour within it.

One of important aspects to add is that those lists could be also added in MORE THAN ONE list. To explain: the bigger list gets, the worse it can become to use, so splitting one huge list into few categorised ones is preferred.

[Toma400]

Also important to tell is that FORGED EVENTS should be rather seen as temporary tools. What this means is that they should not be used as sole conditions for, for example, quests, but rather exist on different plane:

WITHIN QUEST:

• conditions: "is event X, dialogue event AY"
• event X, event Y
• dialogue event AX, dialogue event AY

WHEN QUEST ENDS:

• instead of "condition is event X, event Y" - condition "did quest end"
• events X, Y, dialogues AX, AY - out of the list, no longer fill the space

This means that it would be neat to make some sort of "autocleaner" for those and create separate categories: for both clean reading, and also previous note on list sizes. REMOVING ELEMENTS FROM EVENT LISTS SHOULD BE PRIORITY.

[Toma400]

Dropping #49 here