That could be a good example/start for a "make 'own' trainer options"
I'm sure that it's on Cal's list to look into
nope...we've looked at this game up and down. the game uses a combination of LUA scripting and some string loop functions to store data haphazardly and to stay in touch with alot of the game variables and data. While I can access certain things (like griffin, etc.) by doing searches for memory changes, the problem comes in isolating it in a segment of game code. Right now we have hours and hours of reversing in this game, and most of the options that can be achieved by most trainer makers has been done at this point. If you notice not much new has been added by any of us since the initial releases, and this is because of the way the data is stored, and retrieved in memory.
It's likely that we wont have much else to add to this title, sorry..
Oh well that sucks, but great to know why at least. Thank you =)