|
Post by BonzaiRob on Jul 18, 2007 10:55:57 GMT
I would just like to say that, even if you want to suggest new abilities, there's not such a big chance that it'll be accepted as there is with moves. Because of how they work, abilities need to be hard-coded into the battle engine, whereas moves can be read as needed. This means that moves are far more flexible. Feel free to suggest, however, as good ideas might still be used.
|
|
|
Post by FMY on Jul 29, 2007 20:53:10 GMT
Why should it be hard-coded into the engine? Reading it from XML is possible.
|
|
|
Post by BonzaiRob on Jul 30, 2007 23:24:56 GMT
Yeah, but think of all the extra lines we have to use. One, at least, for every possible ability trigger. They're so varied, it would be far, far easier just to code them into the engine.
|
|
|
Post by FMY on Jul 30, 2007 23:52:09 GMT
Wait, what do you mean with hardcoded? Hardcoded like the the actiontiles (that's not really hard coded, just not in XML), or really hardcoded (no dynamic class loading)?
Reading the traits completely from XML is indeed a little to much, but Dynamic class loading (like with the actiontiles) seems like a good solution for this. Really hardcoding them doesn't seem like a good idea to me.
|
|
|
Post by BonzaiRob on Aug 9, 2007 17:01:45 GMT
If you think you can make it work, then sure, we'll do it that way
|
|