If it's just 'choose your move, execute move, choose your move, execute move' battle system then that's what the default engine is. I don't know anything about the recent ones and whether they are like action battle systems or anything. Of course, this is the early pokemon games.
A couple hours worth of actual coding relative to the number of lines you'll end up writing, not figuring out the system and ruby in general. The only real scripting that needs to be done is designing the HUD's, but everything else (scripts) is pretty straightforward and can be done in a couple hours if someone sits down and does it. When an actor dies you just need to check whether you still have any actors available in your battle_members list (eg: your reserve pokemon).įor the storage.well that's just a storage system where you store actors rather than items. Most of the things can be achieved with events and common events I believe.įor the battle system, you just need to insert a couple new methods to switch which actor (eg: your pokemon) that you want to use. I read over the pokemon system just now and it doesn't seem that much different from the default system. This would require a ton of custom scripting work.
