grid crash solution?

As we all know a self replicating script crashed the servers. I was thinking about a solution that minimizes the effects on scripters.

The solution I have is simple. Why no have an ingame virus scanner that looks for certain scripts?

As I said in another post. It's basic LSL functions that went put together create this. It's simple to make, basic to create. You bascily have to limit the llListen function (which wont happen) and the llRezObject function, (which won't happen (it already got nerfed)). Two core functions that make the 'grid go round'

I say with the information LL has about us from when we register, they should charge a hefty fine to those who cause something like this.

Agreed. I think a CC charge should apply to the one crashing the grid.

I am curious if there is anyway the grid can be made more smarter and proactive to these things. Perhaps some sort of grid monitor.

So when I'm screwing around with LSL and accident rez a few dozen objects in a half second on my plot of land, I get auto-banned and some hefty CC charge, and possible FBI after my ass? I really don't see that working.

The first time I ever made a self-creating object using llRezObject, I crashed the mainland sim where I was experimenting. The owner of the land I was on at the time has to this day never let me live it down...

Finer-grained land controls would help. Say, I want to enable rez flood controls, or such. But I don't ever see that happening (for us Mainlanders).

Yes, accidents do happen. I had a similar problem with a mass replicator (not self-replicator) and the rezzed objects that were supposed to die after 3 sec didn't because I had turned off the scripts to edit and forgot to turn them back on.

I have an idea though. You can have such a proactive grid monitor if you supply some kind of "max objects rezzed" option. That way a scripter who wants an object to make no more than 30 rezzes can set his option to 40 so if the script goes out of control the server can cap the simultaneously existing rezzes to 40 and signal the scripter of the problem.

This will require more development as an idea but it should be workable.

LOL i remember one time i played with llRezObject by making a crossbow (which i sell BTW in my vendors) that had a huge push (i don't recommend using it outside a combat zone o.-). i would take the basic Library object "Parrot" and make it really big and add physics and temp on rez, then shoot at them. I would hit them against my friends house and some penetrated the walls and wound up in the living room XD. Also one of them somehow made it 35 Sims away and ended up in ahern. Since it was a no script zone it wouldn't die. A Linden returned it and seamed pretty concerned about it too.

Can't be done.

IIRC, part of the agreement for credit card processing says you can't charge for anything but what you sell. Meaning, you can't make your own rules and charge as a punishment. Enough complaints, and your account will get closed.

A very good thing too, IMO. Imagine if any company could charge you $1000 just because it's written somewhere in a tiny font in some agreement.

Eww, virus scanners are about the worst way possible to fix a problem. They have a huge performance penalty, need constant maintenance, and won't fix anything in SL.

Virus scanners kind of work in the real world because the real world is huge, and viruses move relatively slowly. It'll only save you if the virus gets caught by the antivirus company, analyzed, added to the database, and the update downloaded before it hits you. That's not going to work in SL, where a virus is trivial to write, and where the time from release to bringing something down is probably easily measured in seconds.

Well made systems don't need antiviruses, anyway.