Wulfie Reanimator

But they don't have to be inworld to make the purchase, even if some are.

I was so confused until the halfway point...

Are you concerned about the performance of browser-based rendering at all (low FPS for the user)? Or does it not matter since it isn't using your resources?

Ah yes, a witch hunt. Very classy and guaranteed to work.

This is still false. A rezzed mesh object that has less textures, VRAM, links, and triangles can have higher complexity than other objectively worse items.

Bit annoying when people keep saying just "lag" without describing it when there are many kinds with totally unrelated causes. Framerate? Reduce mesh/textures. Unresponsive scripts? It's complicated. Hard to move? Possibly physics / agent updates. And that's not all.

Just to clarify in case this detail isn't clear (and to anyone reading to explain the drop): Script time is an average over the past (up to) 30 minutes, or since the script's last rez or restart.

Yeah, from the second link: That's a pretty scary content-destroying bug. If the viewer fails to resolve a texture UUID, it goes "whoops, dunno what that was, but it's this now." That looks to be exactly what happened, based on Chic's screenshots and the fact that she has modify rights to the plant.

When I say "normal" I mean "the viewer is specifically programmed to unload textures from memory when they aren't needed (in view)." It should be your normal, unless you are using a viewer that isn't LL's, Firestorm, or Black Dragon and it does things differently. The textures aren't unloaded immediately, but pretty quickly. (Like 5-20 seconds?) I believe you when you say "it's not your normal" but to me that sounds like there's more going on than your basic description of what happened.

It's not nesting. It's one line, that's it. Nothing needs to go "inside" of it. There's no Else or Else-If either. Also the griefing doesn't have to be targeted for you (general you) to be affected, if I did what I explained earlier, I'm almost guaranteed to break products from many creators at the same time. I just like plugging security holes, sue me. 😜

Oh, that is a more interesting question. Obviously I don't have the answer to that one, I haven't been able to write my own code to log myself into SL in any language though I've tried... If I could figure that one out, trying it with JS shouldn't be too different.

This is completely normal. Textures are unloaded when they are out of your view. If the textures keep reloading while they stay in your view, that's called texture thrashing and it's caused by running out of texture memory.

JS/WebGL/UnityWeb, no. They're just really slow for real-time 3D rendering on their own, but especially when considering how badly optimized SL content is. Rendering in a browser is just magnitudes slower than anything else. http://www.fishgl.com/ http://madebyevan.com/webgl-water/ https://airtightinteractive.com/demos/js/cubes/ https://hki.paris/xp/ Careful, you could be sued for using that word. LOL https://apple.news/AhitRufHOR2SvpJyQpciSKg That article isn't about somebody getting sued for that phrase. The case doesn't involve that phrase. That article is just highlighting how hip-with-the-kids the chief of justice is, for making a joke using that phrase. The very point of his joke was that someone saying "ok, boomer" offhandedly is not discrimination.

You aren't allowed to sell "non-items" on MP. The land market is a special exception. Edit: I guess if the item is 0 L$ you could argue otherwise, but you'll have to go re-read the MP listing rules or ask a Linden.

Blocking the object/script isn't going to do anything. The big group-invite popup cannot be sent from a script. It comes from an avatar (bot). The dialog tells you who sent you the invite, so you can just block them. Besides, even if you accidentally click "Join", there is at least a second confirmation:

I forgot you're already using RegionSayTo, so the "duplicate channel" issue isn't really a problem after all. The effort it takes to totally prevent any kind of exploit is literally one line of code that I already included in this thread. If you think it's not worth it, that's your choice. A choice I can't understand, but it's not my product so whatever.

That's fine, but I bet you're not using the official LL viewer to log into Second Life.

It depends entirely on how the object is scripted. You can't leash to yourself currently because the script is made to ignore either you or all avatars.

Not quite. I assume the HUD name is always the same, regardless of owner? Meaning if I had the HUD, it would be called "Some HUD" and if someone else had the same HUD, it would also be called "Some HUD". If your listener is acting on all messages heard from an object called "Some HUD", it's easy for me to break all of your products. A channel generated directly from the owner's key is not unique nor secure. "0x"+(string)ID creates a hexadecimal number with 4 bytes (8 characters, like 0x12345678). default { state_entry() { string avatar = llGetOwner(); llOwnerSay(avatar); // output: "779e1d56-5500-4e22-940a-cd7b5adddbe0" string hexadecimal = "0x" + avatar; llOwnerSay(hexadecimal); // output: "0x779e1d56-5500-4e22-940a-cd7b5adddbe0" integer number = (integer)hexadecimal; llOwnerSay((string)number); // output: "2006850902" (= 0x779E1D56) } } Note that the first part of a UUID is 8 characters long. It's the same number. The first problem is that there may exist other avatars who have a key that is identical no matter which 8 characters you pick. You can't pick more characters because they'll be ignored when typecast to an integer. Besides that, if I create a new object and rename it to "Some HUD", I can just put my own script in there so it starts sending random messages on channels based on the avatars around me. Even if I don't know which part of the key you're using, the options are pretty limited and I can just send messages within ~200 channel range of different parts of the key. For these reasons, you absolutely should add an additional check to make sure that "Some HUD" is owned by the same owner.

That's not true. The signin page asks for Speedlight account details. You can't login with your SL account. I created an account and added a very old test alt. Here's where you have to finally enter your password. And here we are: I can see the avatar in-world and I sent a test IM. Inventory management: No 3D view.

Are you able to edit the script? All you really need to do is set the leash target to be whoever should be holding the leash, instead of any other object. There's no real difference between avatars and objects as far as "scripted leashes" are concerned.

This does not limit the listener to objects owned by the owner. In that line of code you've created a listener that will never hear anything, because it's listening for a specific object name and a specific avatar key. By definition that's impossible to satisfy, you have to leave out the llGetOwner part and check for llGetOwnerKey separately. See: default { state_entry() { llListen(0, "Object", llGetOwner(), ""); } listen(integer channel, string name, key id, string message) { llOwnerSay("Heard!"); // Will never happen. } } Instead, you need: default { state_entry() { llListen(0, "Object", "", ""); } listen(integer channel, string name, key id, string message) { if (llGetOwnerKey(id) != llGetOwner()) return; // Heard a message from something owned by owner. } } Listens won't "just disappear by itself." It's good practice to close listens when they aren't needed. However in the case of scripted communication, there's no real way to "re-open" a listen without the user directly interacting with the clothing itself. I would just let the listen live forever with the channel and object-name filters.

This is just what happens because of how pages are cached. The search results page is showing an old version of what was in the profile contents.

Following this logic, all of the things you personally experience are fake because they're just signals in your brain.

No idea to be honest... it just irked me a bit So I thought. You shouldn't be irked by something you don't even know to be meaningful. Of all the things you could've been irked by, you chose the worst option.