Quote:
Originally Posted by Paragon
In fact, since I did replace those weapons, that, I think putting the code in them is the the easiest way to go here. It means anyone adding a new axe to the .user file will need to copy the eval script off one of the extent ones to work right with the Edge, but so be it.
Thanks for everyone's responses.
|
Question, why would you not use a new tag on your axes and your code to check for that tag? It seems end users who add a new type of axe would be much less intimidated by adding a tag vs messing with eval scripts. IMHO, adding new tags seems to be the more extensible solution. Granted, I am just wetting my feet with this stuff, so could be wrong on my assumptions.