01 Dec, 2009, Mudder wrote in the 21st comment:
Votes: 0
Whoops! :redface: Don't I feel like a damn fool now.
01 Dec, 2009, David Haley wrote in the 22nd comment:
If you make the functions null as the differentiating factor, won't that cause trouble if/when you eventually want to have skills that are implemented as functions like spells?
My advice would be to not layer a hacky solution on top of a hacky solution. If you really want to distinguish spells from skills, then put them in separate tables or add a boolean flag to the data structure.
My advice would be to not layer a hacky solution on top of a hacky solution. If you really want to distinguish spells from skills, then put them in separate tables or add a boolean flag to the data structure.
01 Dec, 2009, Runter wrote in the 23rd comment:
David Haley said:
If you make the functions null as the differentiating factor, won't that cause trouble if/when you eventually want to have skills that are implemented as functions like spells?
My advice would be to not layer a hacky solution on top of a hacky solution. If you really want to distinguish spells from skills, then put them in separate tables or add a boolean flag to the data structure.
My advice would be to not layer a hacky solution on top of a hacky solution. If you really want to distinguish spells from skills, then put them in separate tables or add a boolean flag to the data structure.
Yes, and there's really no down side. I mean, do you really need to iterate through all of your spells to lookup a skill on a table? You shouldn't.
Random Picks
