Search the Community

Hello, and Happy Wednesday! Today, we’re excited to announce that we’ve updated our Name Change service in a major way. We’ve told you that we were going to keep working on adding new features to the Premium and Premium Plus offerings, and we’re delivering on that once again today. From here on, Premium and Premium Plus subscribers will benefit from a reduced price for the Name Change service. But that’s not all! Not only are we discounting the service across the board, but we’ve decided to democratize the service to everyone. That’s right, as of today, everyone can change their avatar name regardless of their subscription level. Not just the Premium subscribers that have always been able to do so, but all of our Basic accounts as well! This is something we’ve been trying to offer for a long time, and something that we get requests for on a consistent basis, so we couldn’t be more pleased to finally be able to announce it. As an exciting new option for Basic accounts, here’s what it looks like today. Not only do you have the option to change your avatar’s first name to anything you can imagine, but we also offer a rotating list of last names to give your avatar (even if you don’t already have one) that are updated on a regular basis. We will continue to make updates to the available last name pool, so if these options aren’t for you, stay tuned for future updates. You can also suggest your favorite name on our suggestion form, new names are chosen from there! For more information about the costs and how-tos involved in name changes, read the Changing your username FAQ. Click to change your name now!

We have been very pleased to see the response to the return of last names back in April of 2020. Much as we did with the original legacy surnames, we plan to continually update and change the last names that are available for selection. Now that Uplift is complete, we anticipate that the rotation of available options will happen more often. Today some of the older last name options were removed and the following new ones were added: Orlando Incognito Nebula Knickers Aviator Bunny Blackwood Darkheart Amore Suki Venus Evergarden Caboose Dakota Absinthe We will continue to make additional updates to the available last name pool, so if these options aren’t for you, stay tuned for future updates. For more information about the costs and how-tos involved in name changes, read the Changing your username FAQ.

Why do premium members have to pay for name changes when we pay you all $99 a year? I feel as though basic members should be the ones paying $39.99 for the name changes and premium members get that option free for the first time due to the fact we already pay for OUR premium membership.

When I say authenticate in this, I mean to take some information to confirm that A equals B(EG: Is Chaser.Zaks equal to Chaser.Zaks). It is important to note that this isn't fully finalized and Linden Lab may change specific stuff, this is written based off what I know. This isn't a Linden Lab notice, it is a resident to resident notice. Some things MAY BE INCORRECT. This is intended for primarily scripters to raise awareness they need to update their scripts to properly authenticate people via UUID. Please do not spread F.U.D.(Fear, Uncertaincy, Doubt) by skimming through this and spreading incorrect/inaccurate words in group chats. If you already authenticate users by the UUID, then you don't have anything to worry about. The change: If you haven't seen it already, take a quick skim through During a User Group meeting, it has been slightly confirmed(As in, it is the current plan, this may not be 100% the choice yet) to allow users to change their last name, and even first name. For scripters(Both LSL and external), this is a very big and concerning change. We can normally authenticate residents by their username(EG: Chaser.Zaks, Saltyalt.Resident, Ebbe.Linden, etc), but because of this change, this is no longer a viable solution. I have always been authenticating residents via their UUID. The UUID will never change. It is important to authenticate residents using their UUID. What this means for existing content: If you are a scripter, if you haven't already been doing so, authenticate users by their UUID. If you are not a scripter, check that you can authenticate residents via their UUID. If you cannot do this, you will need to contact the creator. If you are a web developer, APIs are planned to allow us web developers to authenticate and update information as needed. Why this change is may be of impact: If you authorize people to be in your parcel by their username, and they change their name, they may no longer be authorized to enter your parcel and get ejected. Why this isn't a security risk / Why you shouldn't worry someone will take over your sim: Once a username has been used(EG: Chaser.Zaks), it can no longer be used again, for example: Say I have a security system which lets me use stuff like /1 eject <name>, or /1 ban <name>, and said security system only checks to see if the user who used it has the name "Chaser.Zaks" I change my name from Chaser.Zaks to Chaser.Soupcanister Someone sees this and thinks "I can use this to my advantage", So they try to change their name to "Chaser.Zaks" They are told they cannot use this name as it has been previously used. Estimated time frame of this change: Not any time soon, but within this year likely. Think somewhere like October or December 2018. This is a big change and a lot of stuff needs to be changed internally to make sure it doesn't break stuff. I assume some things internally may be using name based identification. Updating scripts: Sometimes people may use llDetectedName or the Name parameter from listen. You should instead use llDetectedKey or the UUID parameters when possible. You do not need to change this for stuff that just says "Hello, <insert name here>". For reference, this: string thePowerUser = "Chaser Zaks"; default{ state_entry(){ llListen(1, "", "", ""); } listen(integer channel, string name, key uuid, string message){ if(name == thePowerUser){ /*Do important things here*/ } } touch_start(integer detected){ if(llDetectedName(0) == thePowerUser){ /*Do important things here*/ } } } Should become: key thePowerUser = "796b1537-70d8-497d-934e-0abcc2a60050"; default{ state_entry(){ llListen(1, "", "", ""); } listen(integer channel, string name, key uuid, string message){ if(uuid == thePowerUser){ /*Do important things here*/ } } touch_start(integer detected){ if(llDetectedKey(0) == thePowerUser){ /*Do important things here*/ } } } If you need assistance with this: Please send me a message In-world with the affected script/object with full permissions. I will upgrade the script for you free of charge. I am unable to fix products that are no modify. Please do not kill the messenger.