llBreaklink (((Broke???))

This weekend My Friend and cohort developed a Rez/Link vendor for me.

Everything was going Great all aspects of the vendor worked beautifully in the initial testing. From the underpay/right pay/ overpay to the passing of all objects via a Folder.

We had it working and had eleminated having to use Listens(Reducing Lag) and die scripts(again reducing lag) that we had previously had used. Then we come to find out that the llbreaklink command was Bugged or featured still dont know which yet.

I had, on Saturday, placed out some 30 Vendors around Second Life. Each one cycling at a rate of 1 new rotation every 4 minutes. When I came on Sunday after noon I found that over 6000 prims had been Rezed and did not die. This was primarly due to the llbreaklink command either being broke or a feature the boxes never died.

Here is the Irony of it all. I made the boxes put the Vendors out and stood there for a good Hour watching them cycling them and they worked beautifuly. The old box would die and the new box would take its place never ghosting never leaving a live box active.


((after installing diagnostic testing scripts))
The Moment I left the sim through error checking after the second or third rotation of the vendor the llbreaklink would stop working. And I would start getting messages ever 4 minutes that the llbreaklink was not functioning.

The moment I returned to the sim cleaned up the boxes Reset the Vendor it worked fine the moment I left again it started with leaving boxes active and unlinked.

There is nothing on the wiki mentioning the llbreaklink command only works when the avatar is in the sim. There is nothing in the scripting notes mentioning this and nothing on the .pdf that is given out as far as commands and command structure of .lsl

So My question is this has anyone else had this issue previously?

Are there specific commands in the Scripting language that only work when an avatar is in that specific Simulator and if they leave that sim it no longer works?

I think this kind of information is Critical for Scripters to know as that kind of information can create some pretty sticky situations if its not known.

I had to Manually Delete some 6000 prims due to this because innitially through testing I thought it was ok but due to never leaving the sim had no clue that it was an issue till I came back on Sunday. If it's a bug or if its a feature either way I would like some information on it. Primarly if its a Feature it has just killed 9 major projects I had in mind because I cannot stay in one sim all the time.

Sincerely, Shadow Weaver

Help -> Report Bug

This is something that is (supposedly) fixed in 1.5.6. Give it a test in Preview if you can.

just guessing but maybe it's a permission issue? the wiki says llBreakLink has to have PERMISSION_CHANGE_LINKS set and maybe it can't do that when you're not around.

why are you rezzing and linking instead of rezzing and using llDie or making them temp on rez?

Is this true? This has been broken for as long as I can remember, if it's getting fixed, that's huge news!

Yeah, at the moment the person needs to be in the same sim for it to work. 1.5.6 removes this limitation.

Thanks gang least not all hope is lost, I was gettting really peeved about it cause it cost me two days in the progress of my rebuild.

But thank you for the info I appreciate it.

Shadow

Is that so... i never noticed. Guess thats why i haven't sold any dressers in a while... (they break links to move the drawers)

Yeah, it's in interesting bug in your scripts, because it ONLY happens if you're not there to see it.

if a tree falls in the forest... hehe

Shroedinger's Bug.

Yeah, I ran into the exact same problem last year, when I was dabbling with vendors. I had a seperate prim that would rotate the object being displayed, but I would need to link/unlink with it in order for it to work. Now, this was back when we had to pay L$10 per prim to rez... so when I logged in the next day and found out I had L$7 it was quite a shock, hehe.

Anyways, as was mentioned earlier, it is apparently fixed in 1.5.6.



Later =)

Xylor