Quick Research & Development Thread
View Single Post
January 25th, 2013 (11:17 AM).
Join Date: Apr 2010
Originally Posted by
Okay, I know this isn't exactly what this thread is for, but whatever.
What I've been working on for the past few hours is a rewrite of the stone evolution checking routine. It, essentially, makes it much easier to add custom (stone) evolution methods. If this is unclear, essentially you could write a code to check just for gender (or really, whatever you wanted), put it somewhere, and put that pointer into a table, and it would allow you to evolve using a particular stone on a particular gender of Pokemon. It uses the evolution types above 'F' (as in, all the unused ones).
Right now, I'm doing stone evolutions, though I plan to work on doing the same for levelup and trade evolutions eventually.
What I was wondering, though, is - would it even be worth it to even release it once I finish working out the bugs? Sure, it makes it easier to implement custom evolution methods, but you still need to know ASM to even use it, and, so, the only people that would be able to even use it could do the exact same thing.
I think that you should. And just because someone can do something... doesn't mean they would want to go through all the work of designing such a system, ironing out bugs, building it and so on.
View Public Profile
Send a private message to wwmb
Visit wwmb's homepage!
Find all posts by wwmb
Find threads started by wwmb