enablefeatures2/showstats2
 

The idea would be, instead of defining an absolute like it is for enablefeatures/showstats, enablefeatures2/showstats2 would add/subtract the feature/stat.

Say you do
showstats2 (1024); this will hide the player instead of having to do, allstats-1024, also, if done again, it will show the player. Same idea with enablefeatures2. This will hopefully get rid of the need to keep track of what features/stats are hidden or shown from other NPCs and such.

If thats all it does, then why cant you just script it yourself?

I don't even script on a server. So if someone wants to script one that would manage that stuff then be my guess.

Or you could just define the features and stats in a system weapon or something. this.normalstats, this.sparstats, this.otherstats and simply switch between them. On Aeon I use a client.world variable to show different areas. Each world has a level prefix to define it. Its checked every time you change level and if the world is changed from the last one it calls onWorldChange() in all weapons.

For one thing, you shouldn't even be using enablefeatures() or showstats() in more than one weapon, same with tiledefs.

Aeon is still alive? I remember like three months ago napo let me preview the new Opan, and that was the last I ever heard from Aeon

No not really, Napo decided to take a dive off of the end of the Earth or something, haven't seen him in forever. We're not going anywhere at the moment, I have plans for Opan but not the quality of staff that I need to produce the right levels and graphics. I'm the only active scripter also.

Right now I'm prettymuch using Aeon to develop my own little world to demonstrate my RP-related scripts and try to get out my original ideas. I want all my NPCs to have fully dynamic dialog just like in Morrowind and Oblivion :)

I never need to use enablefeatures() or showstats() more then once and that is when the player first logs in.