Dyna Mole

Linden Memorial Park has been around since the early days of Second Life. Residents have enjoyed being able to visit and to leave a small marker in memory of people who are no longer with us. The system for placing markers is fairly simple, but it takes direct personal supervision from LDPW to keep adding new markers in the system's inventory and to keep expanding the places to put them. The system is working as designed, but its inventory of individual flower markers with pre-calculated target positions is empty. Like many of the legacy systems that we maintain in LDPW, this one needs upgrading. If we were designing it today, we would automate its time-consuming steps and make it more self-sustaining. Moles balance their time between redesigning venues like Memorial Park and Linden Realms, on the one hand, and creating new venues like Bellisseria and the new Halloween Neighborhood on the other. We're working as hard as we can, and there's a lot to do.

Right. Those two, plus the portal to TCMG, do not require you to be in an Experience.

Portal Park (http://maps.secondlife.com/secondlife/Portal Park 1/128/128/24) has been around for 5 or 6 years now. It's pretty heavily used. It's a main entry point for most of the LDPW projects like Paleoquest, Linden Realms, Horizons, Gaming Island, and the Cornfield as well as the seasonal areas (Halloween, Winter Wonderland, Isle of View), although you can teleport to many of them directly as well. Some of those places ask you to accept an Experience before you go through a portal but others, like Winter Wonderland and Isle of View, don't. They are all public venues, fun places to visit. We just opened the Halloween portal on Monday, so you can use it to get to the Haunted Halloween Ride, which is genuinely scary. From there, you can go through another portal to the new Haunted Neighborhood (or you can TP directly to Millbank). Moles put a lot of effort into these seasonal areas each year as well as the large-scale games, Bellisseria properties, and other LDPW projects around the grid.

Hang in there, GOH team! I have no idea what the release date is --- I just work here, after all 🤪 --- but stilt houses are coming Soon™. We'll need a distraction from the cooler weather ahead (well, at least in the northern hemisphere.... ). Keep thinking kind, summery thoughts about the beach.

Ah... That would be Chuck. Go say Hi.

Hmmm. The problem is a server throttle. The script uses an LSL function (llRequestUsername) that makes the servers complain if you call it too many times in a short period of time. When you have a rather long list of people in your whitelist and the script is verifying that each name is valid, it apparently hits that throttle limit. It's not a limit that I was aware of when I created the system. Short of rewriting the script's logic to make it slow down, there's not much we can do, but I will make a note to address it in a future upgrade. For now, I suggest keeping your whitelist to 15 or fewer of your close friends, since you know that's the number that the servers seem to tolerate. Sorry about the less than exciting reply.

Thanks, Mateo. That gives me a starting point. I'll see what can be done.

Hmmm.. Without an idea of what error message you may be seeing, it's a little hard to know where to start. I can't replicate the effect myself. If you can replicate the effect, gather as many details as you can and put them into a JIRA BUG report so we have something to work with.

It should be significantly greater than 15. Exactly what is the script error? Have you tried rezzing a new copy of the Security System?

I haven't heard of a gift policy, but there might be one. I should ask. Moles do get paid. and we have a lot of work to do. As far as I am concerned, I just like to know that I am doing something that people enjoy, so a friendly note means a lot more than a gift. It actually feels fells a little funny to get a gift from someone I don't even know, but I do appreciate the kindness.

Moles go to a lot of trouble to design local settings that match the mood of special builds like LDPW games ( think PaleoQuest or Linden Realms ) and seasonal regions like the Winter Wonderland, Halloween, and Isle of View (Valentine's Day). The moles who create textures and do all the landscaping always work in the custom EEP so that they know exactly what their work should look like to visitors. I feel a little sad when people decide to ignore the atmospherics and go with a blah standard noon sky. It really ruins the mood. 😯

So, you and your sorority sisters are planning to rent out rooms by the hour, and you want to be able to eject visitors who overstay their welcome? Yes, you should be able to do that. There's no upper limit on ejection time. Just a lower limit. Remember that you have to enter the time in seconds..... Be really careful about how visible your sorority's activities are, of course. I suggest a skybox. Remember the 2000m lower limit. 😏

I think we've got it. Welcome to Bellisseria.

There is a quotation mark missing in that line.

You can teleport to the Shop and Hop regions (or an adjacent cam region) by clicking on the upper Left or upper Right corners of any Teleport map in the SL17B regions. The map will take you there instantly. Distance is no object. 😉

Sneaky residents has found my Precious.ss..s.... 💍.......

Yes, indeed., Your Linden Homes covenant says: Security orbs are only allowed if they comply with the following restrictions: -Minimum of 15 seconds warning time (no shorter) -Eject from parcel only (not teleport them home) -Effective range cannot include the airspace between 400m and 2000m (to allow for people to fly overhead but not in the airspace where skyboxes are allowed) If you are uncertain, there is a free security system provided in the Linden Homes Content Pack. It does not have the ability to be set in a manner that does not comply with these restrictions. Click on the house controller outside of your parcel (the one used for changing house models) to get the most current content pack sent to you. The obvious advantage of using the Lab's system is that you know that it meets the covenant requirements (and it's free). You are welcome to use another system that you may be comfortable with, as long as you adjust it to comply with the covenant.

It's actually only incidentally because of the color changing ability, which is handled mostly in a separate temporary HUD. As you said, correctly: When we developed the Victorian theme, the big scripting change was to consolidate the door/window/blind functions into a single control script instead of treating them locally. Scripting always involves making tradeoffs among script efficiency, size, and complexity, as well as optimizing server load and making the system simple and reliable for the end user. When we made that big decision to consolidate, we ended up with fewer scripts and greater efficiency -- and some extra functions like custom coloring -- but had to accept some downsides. Most of those were under the hood, where they just make it trickier for us but you never see them. That hand icon is a small, mildly annoying one that we couldn't avoid. We mutter the mantra softly ... "It's not a flaw; it's a feature."

I suspect that was a typing error, Garnet. (I do that all the time, so typos are familiar territory.) Take a look at these two quick images: As you can see, all I did to change the cube from a nice pink girl prim to a blue boy prim was to "accidentally" miss typing the final 4 in the code for the red channel, so it became 19 instead of 194. It's not your deep navy blue, but you get the idea. I can mess with typos and create all sorts of odd results. I can even do it with copy/paste. Nothing is immune from my typo skills.

There's a prominent note in the instruction notecard that is in your mailbox that says: IMPORTANT: Please note that custom colors are always saved in the control panel for your house, but they are NOT saved anywhere else. If you rez a new home on your parcel, any custom colors will be lost and you will need to create and apply them again. This is one very good reason to save the RGB values for favorite colors in a notecard or some other personal note. There's no practical way for the system to save the custom colors that you create. The dataserver can remember which preset colors you choose, because the house scripts have the detailed color vectors hard coded. Storing the custom vectors for up to nine user-created colors on each house in a region, though, would be more of a challenge. That's why we included the chat message that shows up every time you change the color of a wall, and it's why we advise you to write them in a sticky note or keep a notecard to remind you. That way, you can use the color information for tinting add-ons that you create or you can re-apply them to the walls in a different house that you may rez later. To apply that saved color information to a wall, use the <RGB> option instead of the Color Picker. Now, the system is supposed to remember the colors that you choose for the outside of the house, unless the house changes ownership. When you rez a different house model on the parcel, it is supposed to have the same exterior colors and should remember the preset colors on interior walls (just not your custom colors). If that's not working, it needs to be fixed.

As Fritigern says, the Wilderness regions all still exist and are fun to explore.Here's a shot of Capybara: You can find links to all ten destinations in the Destination Guide under Wilderness:

How about the entire continent of Bellisseria? The system that drives all of the house selection and decoration process is handled by an Experience.

No, not this time anyway. The string that was in the access file was not an avatar name of any kind. It was just a harmless but mildly annoying bogus entry created by a server hiccup of some kind. Life wouldn't be the same without a few mysteries.

@93YearOld That is odd indeed, but it's nothing to worry about. As you said, correctly, the access control system is scripted to clear all of the resident names from the access lists when it detects that a parcel has changed ownership. I do not know how to account for the ghost in your own access list. The system always checks any name that you try to add to the list and will reject a name that is not recognized as a valid login name, so that odd name wasn't entered by a previous owner or some random passer-by. In any case, since it's not a resident name, it's not going to be letting a real person into your home. If you send me a private note or an IM with a SLURL to your parcel, I can get into the system to remove that bogus name manually.

I am not quite sure how to take that ....