Wulfie Reanimator

Neither side might be lying in your case. It could be that LL charged you for an amount, which (after your bank's conversation rate) was more than the rate "google" has given you. You can't expect "google" to give you The Truth, because different banks and payment processors use different rates for many reasons.

It works that way even without banlines! 🙂 That's why a skybox is actually a bit worse if you want privacy. If you're high in the sky, someone can enter the same "section" of the parcel and peek at you from thousands of meters away. But if you're hanging out at ground level, no one above that ~50 meter height is able to peek in, even if they are within the same parcel. (There's other freaky quirks about parcel privacy, like people outside of the parcel still being able to hear chat from inside the parcel...)

No, the store won't close this year because we know people are still buying products from the store. The owner may also have logged in recently (even if it's not in-world), so possibly none of their products will be unlisted.

You haven't swapped any physical parts of the PC either, right?

Ohhh, yeah, that rings a bell. What was confusing me is that mine works correctly - both moving parts (children) are exactly aligned with each other and the target. But if the root is rotated along with a child prim, it breaks horribly.

I have no idea why yours is askew like that.

The "last online" date only shows when they logged in-world. You can cash out by logging into the website. You can also log into the beta grid. The last time LL cleaned up old stuff from the Marketplace was 2019. They disabled products that hadn't been bought for 1 year, if the merchant hadn't logged in for 2 years. They will do the same cleanup this year. (Or maybe they've done it already, I'm not sure.) And while it's not great as a consumer... the merchant is never obligated to provide customer support for their products, or fix any issues with the product, or give refunds. If you've bought something and it's not working, write a review.

I like the disco dude.

The neat thing about Second Life is that pretty much everything happens server-side. In simple terms, the viewer just displays the world as it is, having no control over its behavior. (That's why we call it a "viewer.") And so, because the world isn't dependent on the client implemention, it's relatively painless to use any game engine as a viewer. There's nothing to migrate. 🙂

...unless you are within the "banline area" and they are above it, or vice versa (if there weren't banlines).

Here's code from an old project of mine, which does exactly that. rotation TurnTowards(vector pos) { vector this = llGetPos() + <0, 0, 1.06>; // Calculate the base (left/right rotation) vector direction = llVecNorm(pos - this); direction.z = 0; rotation final = llRotBetween(<1,0,0>, direction); // Calculate the turret (up/down rotation) float dist = llVecDist(<pos.x, pos.y, 0>, <this.x, this.y, 0>); rotation pitch = llRotBetween(<1,0,0>, llVecNorm(<dist, 0, pos.z - this.z>)); // Set both values llSetLinkPrimitiveParamsFast(2, [PRIM_ROTATION, final, PRIM_LINK_TARGET, 3, PRIM_ROTATION, pitch * final]); // This is used later for rezzing return pitch * final; }

If you have multiple (separate) tenants living in a shared parcel, you have to monitor their prim usage somewhat manually. You'll need a script to check how many prims a person has in the parcel, then do something if they have too many. It's not possible to directly prevent a person from rezzing objects past a certain Land Impact, if the overall parcel still has space.

LL does not display the listing date. There are ways to estimate it, but nothing absolute. For example, anyone could check the dates on reviews if there are any. Or you could check when the product images were uploaded to Marketplace. I've made a script that does this automatically and displays the oldest date.

inb4 "crypto in SL????" ...anyway... It feels pretty nice that LL is shining the light on the more scary and underrated parts of SL content creation. 😋

Oh, that I can see for sure. It becomes a kind of separate conversation, but maybe something like indexing 10K products of every category in addition to the overall 50K could help in that case. You may not be the best seller of Marketplace, but maybe you are the best seller of Residential Structures or Ground Vehicles. (The amount of products in a category quickly drops as you go to deeper levels, many don't even have 10K products and you don't want to recalculate the same product for every parent category. I work on a very big web store as my IRL job so I can imagine the work. 🙂)

Disabling stores that aren't constantly putting out new products seems like a very bad idea. Not all stores list all their products on MP, or operate on a release schedule. Last thing Maitreya listed on MP was a BOM applier... isn't it over a year old? Edit: Oh god. I checked, the listing was made in 2019. I feel old. Some stores sell service-level products that are bought/supported for years, so they don't even need/plan to keep releasing new stuff. I wonder how long gaps CasperTech has had... Edit: I checked, the most recent product listing is from 2018. The top 50k thing isn't preferential treatment. If your sales volume isn't in the top 50k, you can't be a best seller, so you don't get a best seller score (which now breaks sorting in single-store view after the update). It's been just a performance thing, and they are working on fixing it so stores will sort best selling products properly.

I agree that building/editing is dying, but I don't think that's because prim builds are getting removed from Marketplace.

Practical question, can you get a redelivery for a product whose listing is removed? Should be easy to test. I'm 98% sure that an unlisted product can still be redelivered.

The "carved out area" is transparent mesh. There's little you can do to fix it in the viewer while maintaining soft looking hair, so you will have to edit your photos after the image was taken. For example, take the photo without any depth of field effect and add that in a photo editor. You can take advantage of the "depth" type photo in the viewer, which you can use as a mask for adding depth of field to the actual photo.

If you mean a text with a link, something like this, you need to write: [www.google.com something like this] Link first, then the text, all wrapped in square brackets.

Flexi prims can only flop about while one end is static, meaning you can't really create a "rope" or anything that's connected at both ends with slack in the middle. That's why particles are often used for that effect.

Correct on both! An alternative method is to use a while-loop, which is similar / maybe simpler: integer a = 0; integer b = 10; while (a < b) { llOwnerSay((string)a); ++a; } ...just don't forget to increment, otherwise you end up with a very spammy infinite loop. 🙂 The for-loop may be better for your own memory! You don't have to worry about arrays - LSL doesn't have any. How are you storing your strings currently? It could be very simple if it's all in one list, maybe you don't even need a loop if each line is its own variable (or there are only a few lines). If all your strings are in single list already, you could do something like... list lines; // Your strings are here. integer max = llGetListLength(lines); integer i = 0; // "i" is commonly used to "iterate" through a loop. while (i < max) { string text = llList2String(lines, i); // Pick one line from the list. llRegionSayTo(avatar, PUBLIC_CHANNEL, text); // Send it to an avatar. ++i; // Increment the variable by one, so the next line will be picked on the next iteration. } ...and just for completeness: // Set i to 0 before the loop starts. (This is kinda redundant in this case and could be left out.) // Before each iteration of the loop, check that i is less than list length. // After each iteration of the loop, increment i by 1. for (i = 0; i < max; ++i) { string text = llList2String(lines, i); llRegionSayTo(avatar, PUBLIC_CHANNEL, text); }

I imagine that deleting the cache has very little to do with fixing the problem. Just relogging is probably enough!

Without seeing the whole script (which you may not have permission to post since you didn't make it), it's hard to say what the problem is. Many gun scripts will hide parts of the gun during actions like reloading (like the magazine while it's detached), so it's probably expecting a specific link number to be some specific part of the gun.

llRegionSayTo goes to a target key, using a specific channel. Both are required, hence "say to."