Ok, I have now rewritten the `choices` function so it can accept functions instead of event numbers. This means that (about half of) eventParser.as can now be phased out, as events can be strung directly together.

Basically, previously, you'd call:
choices("Null", 0, "Credits", 63, "Instructions", 81, "four", 0, "five", 0, "Null", 0, "seven", 0, "Silly Toggle", 0, "Settings", 122, "",0);

and when a button was clicked, eventParser() in eventParser.as would be called, which would then go through it's GIANT if statement chain, to determine which function event [N] corresponds to.

Now, you can directly pass the functions that should be called on a button-press like such:

choices("Null", 0, "Credits", creditsScreen, "Instructions", howToPlay, "Null", 0, "Null", 0, "Null", 0, "Null", 0, "Null", 0, "Settings", settingsScreen, "Null",0);

Note that this is fully backwards compatible with the existing code, so updates to use function arguments to choices (and simpleChoices, which I still need to fix) can be rolled out gradually.