Easily exploited script functions for premium accounts only?

Surely this has been discussed before, but I haven't seen it so maybe it hasn't.

As I'm watching a popular Second Life establishment mercilessly and easily griefed without any way for anyone to stop it, I wonder if anyone has considered the idea that only premium users only be allowed to run certain of the more potentially abusive script commands, or have unlimited ability to rez objects, and so forth.

The ability to create a free account, untraceable to any user, and bring down any area in Second Life is just way too easy. The one I'm watching now just simply takes advantage of the ability to create temporary objects that multiply each other to no end. If there were an ultimate limit to the number of temporary prims that an avatar could rez at once, that would seem to cut off at least one easy griefing avenue. Make it available online to those who can be tracked if it is abused.

Discussed many times already. It aint gonna change!

The real problem is that there is no such thing as an "abusive" script command. Its how it is used not the script command itself that is the issue. Limiting access to a subset of the script commands would break almost everything that has a script in it except for those who have a premium account.

Consider water, in itself necessary, harmless and even fun until some jerk turns a firehose on you. It would not make any sense to limit access to water just because it can be misused by some people.

Some are more easily abused than others. I know with MUSH soft code, which looks the same to me as Second Life scripting and NWN scripting, we had the ability to put the more "dangerous" functions on different access levels.

(And your water example reminds me of an episode of South Park in which Butters, as his evil alter-ego Professor Chaos, decides to use that seemingly harmless water in a plot to destroy the world by flooding, and discovers that it takes an unbearably long time to flood the world by leaving a garden hose running.)

Of course, if some sort anticipation of limiting access to certain functions was not part of designing Second Life scripting, it may just simply be too late to add it without seriously disrupting everything that has ever been scripted in Second Life. So I guess problems like infinitely-multiplying-temporary-objects are problems that can't be locked back up in Pandora Linden's Box.

Your example of continuously rezzing items has already been countered by LL, by something called the 'grey goo defense'. Basically any amount of high speed rezzing is automatically throttled by this mechanism. It's usually the course of action LL will take in these situations. Not so much cripple the functionality, but prevent/diminish the possibility to misuse it.