For like 490 different (or however many it is these days) pokemon. But then you have to actually enter the data. The actors themselves are fairly simple and only have a handful of real stats (the details of which are documented in depth in several websites and they're all really easy to calculate). Attacks that last multiple turns, weather effects, traits that change pokemon type affinities temporarily, the "6-tiered" stat buff/debuff system they have, etc. It gets complicated when you have to implement the actual attacks.
The basic battle system (1v1, switch pokemon on death, first one to run out loses, attacks just read type affinity from one or two tables) is fairly simple. The problem with pokemon isn't the systems, it's the content. 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.
0 kommentar(er)
