Rolig Loon

I am very pleased with my Realistek Appaloosa stallion. He's the horse I have been riding on some of my travelogue wanderings in Bellisseria this summer. It took me a little while to figure out which features work on the worn version rather than the rezzed version (or vice versa), but I've used both successfully. When I'm not riding, he grazes peacefully on my region. He's a fine traveling companion. He even has a nice whinny. Someday I really have to name him.

It's mildly complicated but, as with each of the other topics you have asked about, I'm sure that you can work through the logic. Here's the basic challenge: You want to create a list of people who are allowed to do stuff with your script (open doors, teleport, get gifts,... whatever your script does... ). So, you need to create a global list variable to put the names (or UUIDs) in. Then you need a way to add names. For that, you need to have a way for the user to open a Text Box (with llTextBox), so use one of your dialog buttons to open it. Then tell your listen event what to do with whatever the user types in the text box >>> add it to your global list. That's all there is to it, except .... What if the user wants to remove a name from the list? What if the user tries to add the same name twice? What if the user types a name that does not exist or is not a username? Again, I'm sure that you can work through the logic of questions like this, but here are some things to think about: 1. You can easily set a flag during the action that opens a text box, and then use that flag to tell the listen event whether it's hearing a name that is supposed to be added or one that is supposed to be removed. If it's a name to remove, you'll need to find it in the list and then use llDeleteSubList. 2. You can use llListFindList to see whether any particular entry is already in a list you have created. 3. You can use llRequestUserKey to see whether the UUID associated with a name is a real avatar UUID or is NULL_KEY. And so on. The basic business of creating the list isn't the hard part. It's the tests that you have to include to detect when the user has tried to do something impossible or unexpected. Then once you have the list, all you need to do is look to see if llDetectedName(0) is on it. If so, the user is allowed to proceed.

As much as I truly love what's going on in Bellisseria, I haven't been moved to upgrade to Premium yet. That's a puzzling reaction, as I think about it, but I think I understand better now that the camping trailers have appeared. I love being outdoors. Decorating indoors has never held much appeal for me, because indoors is just a place for sleeping and eating. When I take RL vacations in RL, I head for the countryside (Scotland, Croatia, the Canadian maritimes, Iceland ... ). When I'm at home, I look forward to taking a long walk in the woods or around a nearby lake. I'm finding great joy in wandering around Bellisseria and seeing the landscape, just as I do in RL. The camping regions are stunning, the best I have seen yet! If I were exploring a RL place like this, even at my advanced age, I would grab a tent and a sleeping bag and hike off into the hills. The trailers are wonderful. I just don't want to live in one. I get more than enough enjoyment by visiting. 😊

How about this ...... If you open your mini-map as you wander around watery regions, you will occasionally see dark areas in the water. Small dark things are likely just a rock or a sunken rowboat. If you see a BIG dark area, though, it's a structure of some kind. Mermaids love to hide things in underwater structures. It turns out that there really aren't a lot of them in Bellisseria. You just have to spend some time exploring. Even if you don't find the hunt prize, you will find other cool stuff. That's at least partly why Patch is doing the hunt anyway. That's also why I have been sharing travelogues of some of my explorations in the Linden Homes Photo Thread (aside from the fact that I am having fun).

I'm late to the party. As you can see from the posts above mine, you will get a range of opinions on almost any question that you ask. In the end, you'll just have to decide for yourself. Check out possible spots on the mainland to see what the neighborhoods are like. Check rental prices and covenants on private estates too. As a Basic member, I can rent anywhere, so I never felt a great need to upgrade to Premium just to have a spot for a shop. Over the years, I rented shop space on several regions on the mainland and in private estates and was happy in all of them. Now that I am selling only through Marketplace and own my own estate, it's no longer an issue for me. If you're considering an upgrade yourself, I think you'll find that other Premium benefits (like the sandbox, the weekly stipend, the access to Live Chat, and the Premium gifts) are likely to be more important than the ability to buy land on the mainland --- unless you plan to live there or in a Linden Home.

So, get a wearable Bento horse like mine.

It's a bit obscure (but probably not to people who live in graphics world). The limits page that I referenced above says Aspect ratios of profile, place, etc. pictures — all of these were measured at UI size (Edit menu > Preferences > General tab > UI Size) = 1.000: which implies to me that the "native" aspect ratio is the ratio that customarily appears on your own monitor and it also what your viewer presents as long as you haven't messed with UI size. In other words, the "native" aspect ratio is the aspect ratio that anyone ought to see on their own monitor unless they have monkeyed with it by stretching the image.

Justice Ginsburg

I've never heard of a limit on how close you can cam to an avatar. In my 12 years here, I have always been able to cam inside avs, just as Qie has. It's not something I do every day, but it's useful when you're trying to help someone find a lost piece of jewelry.

And you said that you weren't a scripter! This is how we all begin. A small challenge pokes us into trying something, and it works. I should warn you ... once the bug bites, there's no turning back. Scripting is like doing crossword puzzles or whatever your favorite puzzle is. It's addictive, and very rewarding. Keep at it. As you get stuck on whatever you are working on, feel free to bring it here to share. This forum is a place for scripters to share insights and to commiserate about things that aren't quite working right yet.

A system like that comes with a well-written set of instructions for doing all sorts of magic. If you follow instructions, it's not hard at all. If you are setting up a handful of vendors in a single shop, a system like that may be more fancy (and more expensive) than you need. If that's the case, if I were you, I would look instead for a smaller system that cannot make refunds.

Yes, I agree. If you were a scripter, you could do just that. This particular script is a very simple, bare bones script that could be modified in lots of ways, including managing several doors. So, you have a choice. You could either figure out how to change it yourself -- not a terribly difficult job -- or you could hire a scripter to do it for you. Or, you could just go ahead and use two separate copies of this script, one in each door. Frankly, the small inefficiency of using two scripts is almost negligible, and that's by far the easiest option you have. If you were scripting an entire house full of doors, I'd think abut the modification.

You are very wise to be cautious about using any script that displays that warning. It is produced automatically on any script that needs your permission to take money from you. In this case, I suspect that you are setting up a vendor that is intended to be able to refund money to the purchaser if there has been some mistake. The vendor will not be able to make the refund without your permission. So, as part of the setup process, it is asking you for permission. If you are using one of the common vendor systems, like CasparVend, it's a normal part of the process. That should have been explained in the instructions that came with the system. However .... If you are not using one of the major vendor scripts, I would be cautious, especially if you will not need to give any buyer a refund. Not all scripters are careful about making their scripts secure and error free. An error in a script that wants to take your L$ can be expensive. Therefore, I would recommend either using one of the big commercial systems that have a good reputation for reliability, or using a vendor that does not need to offer refunds and will therefore never need to have your permission.

A second independent door? Just name the second door something else. Notice the comment line in the script that says // All prims in the door must be named "DOOR", and none can be the root prim of the linkset Well, in your second door, name all prims something like "door" instead of "DOOR", and be sure to change the two places in the script that look for the name of the door that you touched.

Yes, you could easily modify it or any sliding door script to talk to a companion.

and still unindicted ....

There are no puppies in the Flattened Fauna book. Honest. Just good ol' raccoons, possums, snakes, and -- well, yeah -- bunnies. What kind of grandparent do you take me for?

Oh, that is lovely. Yes, the 6-year-old will be particularly fascinated. I'll pass it along. 😜

Not that I am aware. I think it's in the server code now. I alternate between the LL EEP viewer and Firestorm myself, and haven't had any trouble since I reset it. None of my tenants have said anything either. I suspect that many of them are on Firestorm. I wonder why it's a problem on your region? Have you tried restarting the region?

I thought as much. I think my son walked off with mine. It was quite dogeared, but I'm sure he is getting good use out of it. He has two curious daughters, after all.

I suspect that you are already aware of the classic text in this field, which has been around since 1987.

Ooo! I must have misspelled it. Yup, you're right. Of course, that whole site hasn't been updated for much of the past decade, so there's no telling how many are still with us, but at least we know now that there really were lots of Zehetbauers once. Thanks, Rhonda.

I had that problem on my own region a month or so ago and solved it by running the Linden Lab EEP viewer and setting the Windlight with it. I haven't had a problem since.

And you are not likely to, unless someone sets it as a Display name. If you look at https://slnamewatch.com/ to see the history of legacy names, you will not find a single Zehetbauer among them. You are unique!