The part about existing scripts can't be right...
This part can't be right:
"Will Display Names affect scripts I have created or bought? No. Your username in Second Life will automatically change to your current Second Life name, lowercase, with a period between your first and last name (for example, "John Smith"'s username becomes "john.smith"). "
If every existing call that returned "firstname lastname" now returns "firstname.lastname", then thousands of scripts will break. For instance, any script that reads a list of authorized users from a notecard, and compares the result of llDetectedName() to see if it's on the list.
I assume that the actual story is that all of the existing LSL functions that deal with names will still deal with the "firstname lastname" form (even if, internally to the server, they're actually stored as "firstname.lastname").
This section should be revised accordingly.
- update*: Kelly Linden has clarified the plan in a few posts on the opensource and/or scripters lists: as well as the "whatever you want" display name and the "first.last" user name, there is also a "First Last" form, which is apparently called the full name. And existing LSL functions that deal with names will all deal with full names. So nothing should break.
Dale Innis 01:16, 18 August 2010 (UTC)
I agree...I really hope what the FAQ actually says isn't what actually happens in regard to what existing avatar name calls will do.
- I'M GLAD YOU BROUGHT THIS UP. I've edited the section and linked to Kelly's post. THANK YOU. - on 2010-08-18 @ 5:59 AM Pacific
While we're on the subject :) , the phrase "Any of their scripts" can't be right either. It suggests that somehow the behavior differs based on who owns the script, and that's surely not the intent. Dale Innis 19:20, 18 August 2010 (UTC)