I am excited for this if for no other reason than seeing an end to the many MrDollSteak for 90+% of work & a few additions patches. I’m not all that happy about throwing in JPAN’s Hacked Engine, but I suppose that it isn’t all that space consuming and users could simply not use it. I also think the base could do without animated sprites, but meh, they’re fine.



Could you explain the significance of the “923 Pokemon slots and 869 dex entries” to me? Are they for forms & such? You seem to be accounting for the limbo slots & egg/unknowns, but if you’re including all 721 pokemon, why don’t you map the forms of the same species to the same dex slot? On forms/megas, I’d say implement all of them 100%. Each of those Pokemon were built with forms in mind, and not having proper forms in some cases ruins their balance. I would also say that proper new evolution methods are a “must,” especially since public code for all of them already exists (ignoring obvious exclusions such as Inkay).



I don’t want to appear to be barking orders at you, so I have a few things that may alleviate some annoyances if you’d like them. If you’re expanding moves beyond 0x1FF (which would be a good idea, imo), I have a nice little (easily editable) .s file from a while back that you can “assemble” into ORAS learnsets for all 721 pokemon. All you’d need to do is change the defines at the top to match the order of your attacks. Same thing for egg moves (though I think the regular 3rd gen breeding mechanics have an egg move limit?). I have a similar file for habitats, but I’m not all that happy with how I arranged the pokemon. Although it is pointerless, I also have something that can be used for base stats for all 721 pokemon + forms. I know all of those are very easy to do, but the files would save you a lot of time if you haven’t already done those steps. Good luck on this!