Jump to content

Wulfie Reanimator

Resident
  • Posts

    5,707
  • Joined

Everything posted by Wulfie Reanimator

  1. Lindens definitely check them, the response just naturally varies based on how egregious the keyword spamming is, and whoever happens to be checking at the time. Here's a recent thread from a merchant who complained about their keyword spam getting unlisted: https://community.secondlife.com/forums/topic/505602-product-marked-as-spam
  2. Because the URL your script creates is incorrect. 😋 Your URL is this: secondlife:///app/teleport/Shermerville%20Central%2F114%2F125%2F16 When it should be this: secondlife:///app/teleport/Shermerville%20Central/134/97/27 To fix your script, replace llEscapeURL(region+slurl) with llEscapeURL(region)+slurl That said, the broken URL does cause the teleport-rate limit to show up on first attempt. That just indicates a bug in how the viewer or server handles the failed teleport / invalid request. Edit: Eh, better 2.5 weeks late than never.
  3. I would build a list and apply everything in one call to llSetLinkPrimitiveParamsFast. Script efficiency doesn't really matter when something is done as infrequently as 20 seconds. Even if the whole operation takes a full 20 seconds to complete, or you end up sending 15 individual object updates, it's not very significant in the grand scheme of things. The benefit of SLPPF is that all of the colors update at the same time. If you loop or just have a long list of llSetLinkColor, we can see each individual object being updated (or the script might even be forced to idle mid-update by the sim) and it just looks kinda silly (unless it serves some stylistic function, of course).
  4. That article has links to both sites: lslwiki is very old though, I'm not sure it's been actively worked on in years (but it is a nice archive). It was working recently (I checked like a week ago), it might still get fixed.
  5. Oh yeah, you're right. They replaced the flat fee with a sliding scale in 2021. That changes things a little bit, but buying more is still cheaper than buying less.. or I should say more economically efficient. If you buy 3700L right now, your fee is $1.50 (10% of total cost) If you buy 2000L right now, your fee is $1.49 (16% of total cost) Although the second option costs less money overall, you're also paying for nothing. To save money in the long run, you'll always want to buy at least $15 USD's worth of lindens so you match that minimum fee, even if that means waiting longer between purchases.
  6. For what it's worth, buying in large quantities is cheaper. Every time you buy, you have to pay a flat fee regardless of how little you buy. Instead of buying 3000L after 2 months, you could buy 6000L after 4 months and save the fee. Sounds like it could make a significant difference for weak currency.
  7. I don't recall, but I checked anyway and yup, the banline texture depends on your viewer skin. For example: viewer/skins/default/textures/world/NoEntryLines.png viewer/skins/starlight/themes/silver_pink/NoEntryLines.png You can replace the texture with whatever image you want, and it'll be tiled across the parcel boundaries.
  8. I understand your point but I don't think it's a good one, because even if all SLMC groups restricted their sims to only using weapons from certain creators... you've just created multiple closed systems (each sim having its own "approval list") that are really annoying and impractical to maintain when new groups are created or new devs join existing groups. This wouldn't be adopted by the SLMC, I would bet a significant amount of money on it. Other combat sims might, but I don't know of any existing combat things that aren't already closed-systems like VICE or roleplay sims using external GPHUD scripts. Even if you were using a closed (creator-exclusive) system like this, you would still have to moderate the kinds of weapons people use. Currently SLMC groups might ban individual weapons of certain groups/creators, not the whole group/creator. (Some groups allow vehicles or movement boosters, others don't.) And there will be cases where those creators have more than one theme available. Like modern vs futuristic, or medieval vs fantasy.
  9. By the same token, someone could come in with their own magic spell to kill everyone. What about creators who make magic spells and modern guns? I think a problem like this is easily solved by normal moderation, the shape of the weapon doesn't really matter.
  10. Your zoom level is off, the API specifies zoom levels between 1 and 8. Just changing the zoom value to 1 in your URL will get you the correct map tile.
  11. You could try putting up a Jira about it, that way devs are sure to look at it and check whether this is expected behavior or a bug.
  12. This may be related to your text having anti-aliasing on it, which causes different Roughness values for the outline. Not exactly sure why it shows up like that visually, though.
  13. There's no mention of any disabilities in your profile. The amount of details you've left out are a little telling that there's more to this than you let on.
  14. I tend to enter the local province/region, or just the country again. "N/A" should also work, or any similar "no state" text.
  15. The problem is line 19: if (intOffset == 0) { return strTimestamp; } In that case, it'll just output the raw string from llGetTimestamp() instead of doing any of the formatting below (eg. 2023-11-21T15:33:10.530729Z) If you remove that line, it'll format correctly again. (eg. 21-11-2023 15:33:29)
  16. Would you pass a copy (with modifiable scripts) to me in-world? Seems like an interesting problem.
  17. All the chatter tends to happen elsewhere, before code is submitted/merged into the viewer. Places like the public LL meetings, forums of TPVs, Jira tickets, and of course internally within LL that we can't see.
  18. To be fair, the signup bonus is terribly mentioned. On the page where you choose your plan, the "45 days" line is at the very bottom of the page, and there's no indication on the bonus that there's a caveat.
  19. If you were logged in when you paid it, you probably need to relog. The sign-up bonus is given to you only after you stay subscribed for 45 days consecutively. If you only subscribe for one month and stop, you have to start over and sub for 2 months, not counting the first.
  20. Anyone know where's the wiki page to actually edit those GLTF params?
  21. Try logging into a different sim.
  22. 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.
  23. 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.
×
×
  • Create New...