Yeah, I think we will need to decide on how to structure these.
For events, we could have for example first a guide for scripting for XXL1, and then have more detailed pages like a list of events.
Note that an event list would be quite long. Maybe we could keep how it was in the current list text file with just some formatting but not sure.
At least MsgActions have a smaller amount, we could for example have a page about MsgAction explaining the states, handlers, actions etc. then have a list of all actions at the end.
But yeah, I could make you a contributor to the GitHub repo, which should give you write access to its Wiki.
Maybe the list of events could contain all events, including the ones with parameters (although not sure if this would be beneficial for XXL1 events, as you cannot specify parameters in the sequences)
My Idea for the MsgAction documentation would be to make a squad from the ground up and make all the necessary stuff, like msgaction, choreo etc. and explain them along the way. Of course a glossary of states, actions and handler can be appended at the end to give some further context to the different events
Yeah, there is already a guide on making a squad, so maybe you could just extend it at the end, though there are some areas that might need more clarification, simplification etc.
Yeah, but just a squad with a single enemy ^^
And it would be inefficient to have a squad for every single enemy in the entire level
Yes, the idea is that a beginner would start with the simpliest squad, and then later end up with an advanced one.
So one could easily learn to make one without feeling overwhelmed.
Sure, I guess I can keep the demo and then making an advanced section for the different tabs
Notify me when you added me as an contributor 👍
you know what i am thinking
you guys need to create like a separate polygon showcasing different stuff
that way it would be easier to explain it to people with images
and how it all works instead of walls of text