Wulfie Reanimator

Try logging into a different sim.

If you own the notecard, you can always read it. The "you do not have permission to view this notecard" message is only shown if you're trying to read a notecard you don't own, for example in someone else's object. What are you trying to do? If you want a scripted object to read a notecard without the owner being able to see the notecard.. you can read notecards by their UUID, the notecard doesn't have to be in the same inventory as the script.

The flickering you see is caused by the behavior described in the wiki. Ribbon particles are always connected to each other, regardless of distance. The last/oldest particle, which has arrived at the target, is only connected to the particle that will come after it. When its lifetime ends, the ribbon "chain" gets shorter because one particle has been removed. More burst rate and lifetime helps, but the flickering section grows with distance. One solution would be to use two particle systems, going both ways. That way the flickering is hidden by the other ribbon chain. Another solution might be getting LL/TPVs to change how ribbon particles are rendered, so that the oldest particle is also attached to the target, similar to the newest particle. That would probably cause a straight line between the source/target until enough time has passed for the particles to travel their actual path.

There's a whole bunch of "hidden" data in the page that's just not visible by default.

If you plan on making the kind of money that pays the bills (or at least groceries), you'll probably want to focus on just service/commission work. (In which case you could just invoice them through PayPal and avoid the LL fees.) I can't imagine any amount of games in SL (especially Portal Park) would get you enough lindens to cash out anything meaningful per week/month. Content creation is an option, but it takes significantly longer to build a store, let alone finding traction.

Yes, I understand. With the exception of that one caveat, what I said holds true.

Is there a difference? When you rez a new object with build-tools, that's when that object is originally created. When you upload a mesh file, that's when that object is originally created. (Whether it uses the current date or the source file's date doesn't matter much.) Either way, OBJECT_CREATION_TIME returns the same date for all copies of whatever the original asset had as its creation date.

This may be a side-effect of how uploading identical assets works. For example, if you upload a texture... and then upload the same texture again, you'll get the same texture UUID both times. Basically, LL will check if the asset already exists, and then give you that copy instead of creating a brand new one. I hadn't tried it with mesh, but it seems very likely that they handle all assets the same way. If you want two creation dates (neat thought), just make any change to the mesh (like move one vertex by 0.001 units) and it'll no longer match the other asset.

Europa immediately comes to mind. This is a creator who made original stylized content, before moving on to game development. I don't think it's a problem that users can change their lighting at will.

And just to be clear, PBR is not fully released yet. Sure, you can see PBR content in PBR-enabled regions, but many regions and most viewers don't have that functionality yet.

The "update" to petite/flat that was talked about earlier in this thread was about them becoming part of the body itself, instead of a separate attachment you wear with the full body. Similar to Legacy / Legacy Petite. I dunno if that's still accurate or if it was just speculation, or how it would affect the prices of those addons.

Some of your products definitely step into keyword spamming. You copypaste the same tags a lot, even between unrelated products. For example, a stack of 3 books with these keywords: drapes, curtains, couch, chair, desk, lamp, light, table, stool, barstool, fireplace, mugs, pouffe, daybed Or for example when you sell pants and shirts separately, you have the same keywords on both. Shirts tagged as pants, and pants tagged as shirts. I don't think you should cry about Big Brother when another user reports your items for keyword spamming, especially if it took 10 years. Just fix your keywords and move on.

If a bone is no longer animated by anything, it appears frozen in whatever position it was in previously. There's also a long-standing bug where an object whose UUID is lower than your avatar will stop all animations instead of just the animation it tried to stop.

Neve is another store that has a lot of very casual (covered shoulders, zero-clevage, knee+ length skirts) summer/fall wear. They have a lot of products though (1300 items at 0L) from over 10 years, so you have to dig a bit.

Even if it was impossible to cram your camera under that shirt, it'd still call it sexual/sexy. It's not just a tank/crop top that leaves the belly visible, the creator went out of their way to add detail to hike up one half of it while adding a bit of emphasis to her breasts with those creases.

Some people use capitals for Emphasis, similar to "some" people using quotes for the same thing...

Yeah, that's what I meant with the line you quoted. 🙂 The power of cheaper, mobile/laptop CPUs is pretty good on their own in current year. GPU optional as far as I can tell.

Yeah, it's the Iris Xe. I haven't done any benchmarks and don't plan on gaming on the laptop, SL was just one-off for funsies. Is there anything specific you want me to do?

Even the laptop processor I got recently (i5-1335U) can run Firestorm on ultra (without shadows) in a populated place with everybody (10-15) fully rendered. No real GPU, still 30 FPS. I think SL users tend to really underestimate modern hardware, myself included. And while the performance difference to my ridiculous desktop build isn't as big as it should be, anyone who says better hardware doesn't matter is just very wrong.

Meaning something like this, with llListReplaceList. Can't get inworld (let alone OS) to test it, but basically.. check for existing stride, get the land impact from it, add the new LI to it, then replace the old stride (start to start+1) with the new stride / updated sum. If the stride doesn't exist, just do the old logic. CalcPrims(vector Loc) { list TempList = llGetParcelPrimOwners(Loc); gListLength = llGetListLength(TempList); if (!gListLength) { llSetText("[ERROR]\n Couldn't get Parcel Prim Owners", <1,0,0>, 1); } else { // Produce a copy of the list suitable for sorting by count, i.e. count then key integer x; for ( ; x < gListLength; x += 2) { key owner = llList2Key(TempList, x); integer newLandImpact = llList2Integer(TempList, x+1); integer stride = llListFindList(gListCountsAndOwners, [owner]); if (stride != -1) // Found this owner before. { integer oldLandImpact = llList2Integer(gListCountsAndOwners, stride); list data = [ oldLandImpact + newLandImpact, osKey2Name(llList2Key(TempList, x)) ]; gListCountsAndOwners = llListInsertList(gListCountsAndOwners, data, stride); } else { gListCountsAndOwners += llList2Integer(TempList, x+1); gListCountsAndOwners += osKey2Name(llList2Key(TempList, x)); } } } }

How do you get this data right now? Frionil's suggestion works for cleaning up the data, but maybe we can get it in the right format before it needs to be sorted.

Just post bad code! Garbage in, garbage out.

I never knew communism was about this, thank you for educating me.

I can totally believe that, I've been (am) a really shoddy coder too! The script just has an AI-smell about it, especially after I saw that line. It's one thing to make a silly/redundant/impossible check. It's one thing to use an imaginary function-call. It's one thing to add extra comments on every line of logic. It's a whole other thing to do all of those things at once, with otherwise very good coding style (implying a reasonable level of understanding), and confidently present it just as "try this one." 😋

A human (even one that wasn't good at scripting) would not write this: // Check if the detected avatar is in the same group as the groupKey if (llSameGroup(detectedKey) && llGetAgentGroup(detectedKey) == groupKey)