Storing Information: An Abuse of Arrays

Information is a super important part of my game, since without it how could players choose which Hero to send to which World?  So finding a good way to share all that info is something I've been spending a lot of time on, as you can see with the current version of the World Info sheet:

There's a lot of room for details there, but how is it all stored in the game?  In variable arrays.

Variable arrays are possibly the most used thing in my game right now, I use them to store all sorts of info, from the Hero details to the MC's current mood and employment status.

Which means I have a pretty big autoevent that sets everything up.  That's not too bad, but it did make it hard to look at the event and be able to easily judge what each script call was setting up.

A shortened version of the first autoevent iteration.

Just look at that horizontal scroll bar!  It may not be too tough to find right variable like that, but it is definitely tough to make sure I'm tweaking the right part of the array when I'm testing things.

​I knew I needed to change how I set these up, just for my own ease of use.  So I decided to have only one variable per script call, and separated each section with a comment just so that I can quickly tell what I'm looking at.  I also used one of the minor bonuses of arrays, the comma, to break up the script call onto multiple lines.  Now while the event is much longer to scroll thru, it's much easier on me to be able to find just what I'm looking for.

Part of the current event.

I'm happy with how the event is set up now, since I can make edits to things as I go a lot more easily now.  It makes adding new Heroes and Worlds a lot simpler, which is great!  Now I can add as much as I want without ending up too lost in the event.