HAHAHAHA THAT IS NOT HOW YOU DO A TURN-BASED RPG!

Actually, I've never even attempted a turn-based RPG, so I wouldn't really know how it should be done. I'd assume it couldn't be TOO complex, though.

This is the assumption that kills all turn-based RPG designs, Kilin. It's simple from way up on one's design pedestal, but… It becomes a very complicated beast later on.

I know, because I've started many.

I just remember someone making an action RPG and claiming it was because turn-based RPGs are slow and stupid. I personally thought it was because it was too hard to make.

And I don't feel like going over the requirements for that sort of thing, but I'd guess you'd have a variable that shows how many people (and monsters) are on the field, one to represent the turn, some random number generation, etc.

Maybe one day I'll take a shot at that. I miss good turn-based games.

Oh, wait. I forgot…

BWAHAHAHAHAHAHA THAT'S NOT HOW YOU MAKE A TURN-BASED RPG!

I actually kept the player party size and the enemy party size separate entities, but yes.

The turn "variable" was actually a list that corresponded to the ID of the player or of the enemy.

PEOPLE YOU NEED TO STOP ASSUMING THAT I CAN WRITE THINGS GOOD

The user events are actually really, really useful things.

I've only started a couple. In fact, the Seventh Iteration you have here is actually based on that assumption, and so was the To Kill A Mockingbird Engine (which was kind of like Chaos Weapon v.6.5)