ellestones

the script function llKey2Name will still be available. What we are urged to do is to not use the avatar name as an identifier as the person may change their name breaking our script. A example of what not to do anymore: list names = [ "Some Avatar", "SomeOther Avatar", "AndSomeOther Avatar" ]; touch(int num) { if llKey2Name(llDetectedKey(0)) is in list names then they can operate the device } if "Some Avatar" changes their name then they will no longer be able to operate the device to prevent this breakage in new scripts going forward then: list uuids = [ x-x-x-x, // Some Avatar y-y-y-y, // SomeOther Avatar z-z-z-z ///AndSomeOther Avatar ]; touch(int num) { if llDetectedKey(0) is in list uuids then they can operate the device }

debug Which by using llOwnerSay(llDumpList2String(Which, ",")): if it doesn't print anything to your chat then Which is an empty list

its a bit unclear what you mean by it doesn't work. Would be good if you could explain that a bit more i notice that in the 2nd you use Mode, in the 1st you don't. Other than that both codes are functionally the same

if non-profits could get free land I would be into that like I would have a Prosperity Gospel Church. And everybody could come and I will preach the gospel of how all the goddesses wants you to give me lindens money so you can go to heaven. And you can pray also to the goddesses that I can get lots of lindens money so that I can get a aeroplane so I can spread the gospel further lots of people be into this as I will make them Prosperity Gospeleers. Like missionaries. My missionaries be able get a free land as well for their own missions. And bc they all good gospeleers then they will give me some of the lindens money they get through prayers and mission giving. So they can go to heaven on a VIP (virginally innocent prosperity) pass in the hereafter hope so maybe somehow

adding a little clarification about lists under Mono CIL a list parameter in a function call passes a copy of the class object pointing to the list data. The list data itself is not copied in the function call pcode example of how this works: list a = ["1", "2", "3"]; translation: data = ["1", "2", "3"]; class list a { p: pointer; read() { return data(p); } write(...) { ... }; }

i tend to flat random IMs from random people them: hi. me: hi then leave it to them to continue other flat responses them: pretty avatar. me: thanks them: I love you. me: me too them: are you a girl? me: Yes. them: are you a boy?: me:Yes. them: are you a frog/pony/kitten/giraffe/hippopotamus? me: Yes and sometimes a bit more than flatting if I got nothing else to do them: Do you do it? me: sure. them: I teleport you baby. [after some time] them: did you get the TP? me: No. them: Now? me: No. Must be broken them: What you do on SL babe you sexy thing? me: big long list of lots of nsfw stuffs. them: Really? me: no them: want to have fun with me beautiful?. me: Yes please. them: Do you have a favourite place or should I choose?. me: I will choose ok. I know lots of places we can have fun. them: Sure babe. [me sends TP] them after rez: This is a hair shop. me: I know! isn't it fun! I love shopping

I Wus On The Beta Grid So Nyah Nyah generation I Has A Starax Wand generation I Got Booted From The Main Grid Where I Wasn't Allowed And Exiled To The Siberia Gulag Otherwise Known as the Teen Grid generation I Am Do You A Favour By Inform With A Big Flashing Sign Next To Your Mainland Parcel That You Can Rent A Parcel On My Estate Where You Won't Have To Live Next To A Big Flashing Sign generation Mesh Is Going To Be The End Of Second Life generation Second Life Is Not A Game generation Yuss It Is generation Dismissing Profoky FIC List As Beneath My Dignity And Yet Always Feel A Little Heart Break When I Never Made The List This Year Either generation Not Ever Getting On List Ever Ever generation Being A Linden And Not Getting On A Residents Linden List Even Either generation

/me wonders if that Tommy is the son of GetOffMyLawn Linden

@Tari - well yes about how people are going to feel about all this and express their views. As people did when last names were abandoned as I already said I think it would be a mistake to not include a name change credit in the Premium package. But if LL do then is every possibility that the Premium package could be increased in price I am also not convinced that restricting payfor name changes to premium-only is a good thing. I am not understanding the thinking behind this. There might be but I can't see it

Hamlet Au posted on his blog about this. Hamlet can be a bit hard on Linden Lab sometimes, but he does try to give credit to the facts most times. The funniest part was he mentioned that Strawberry Singh has more followers on her SL content youtube than Digg has Twitter followers

you're treating the things we do currently get in the Premium account offer as if they are inconsequential, when they aren't to those who buy them

i agree that people shouldn't pay twice for the same thing say a person buys a Premium account. For this they get 300L stipend. 1024m tiers, a Experience Key and access to Premium land/spaces/content if the ability to change is not included in this package then they are not paying twice i do agree though that it doesn't make any sense to me not include in the signup package a name change credit

is interesting when we get into whats fair is it fair that later adopters only get 300L stipend now and early adopters still get 500L is it fair that early adopter new accounts still get 50L stipend and later adopter get 0L is it fair that very early adopters were able to buy lifetime accounts and later perople were not is it fair that sim owners on low-class sim servers who chose to stay on them and to not upgrade to the newer powerful servers were grandfathered at the old tiers rate when the whole grid was finally upgraded is it fair that the First Land programme was discontinued and subsequent new premium members had to go to the open market for their first land is it fair to these subsequent new members when LL started providing Linden Homes gratis after these people had incurred the extra cost to secure a home there's a temptation to look at all these things and say none of them are fair to us today. Its an abyss of discontent when we do this. When the way it works and has always worked in any real world is: This is what is offered today and this is the price today. If the price is right then buy it. If not then buy something else

@Wulfie - can add Club Penguin to the list. To get your own name you had to get a payfor account. Yesterdays children are todays adults who don't see this as a big deal. Paying for a inworld name is pretty common. Inworld names are like a asset property to many online people. In the same way as other inworld/game assets that enhance our sense of well-being

agree with the sentiment I would suggest that the single most important thing LL could do in all of this, is enable a person such as yourself to be able to rephrase their own existing name. By allowing you to split your name into First and Lastname. Coffee your first, Dejour your Last for exaample. LL have said that they will take suggestions for Last Names from the community. So you should be able to suggest Dejour for that list. You might have to wait a while for it to appear on the current list but I think LL should accept that your suggestion will appear at some time on the list Tte issue with this is that LL have said we won't be able to take a name already in use. Its a fail point if we cant rephrase our own name. As I don't think you would want to be left with an only option like: CoffeeDujour Dujour

i agree with your main point which kinda got swallowed up in the subsequent chatter that when actual Last Names do come back then LL in the official viewer codebase continue to not display Resident, as thats the current and expected behaviour that a TPV put code back into their viewer to enable display of the Resident lastname placeholder after LL removed it from the official codebase falls into the vanity feature set. Vanity features are options that are not necessary in a functional sense. They address the psychologicals of how a person feels. And if people feel that displaying Resident on their own screen through the use of a third-party add-on helps them to deal with their feelings then I am not going to advocate that they can't

^ this a capability to revert would be a good thing

@Xuander - Wwhat you are now asking for entails you learning about: lists, attach/detach, owner, ownerkey, listen, channels and region say the LSL wiki has lots of code examples for each of the functions and events that you need to know to create the app you want. My advice is for you to copy the wiki examples into inworld scripts, compile/run them, and study them to understand how and why they function as they do, and how what you observe relates to the LSL wiki explanatory texts. Then based on this understanding try to incorporate what you have learned into your app script the purpose of this forum is to help you debug scripts that you write. To give you pointers on the pathways open to you on your journey to becoming a scripter. It is not the purpose of this forum to write your app for you. The direction open to you in this now instance is the LSL wiki. Read it up, code it up. Observe what happens. Incorporate what you learn from this into your own app script. When we can see by the code you do post that you are making a reasonable effort to be a scripter in your own right then ppl on here will continue to give you pointers and guidance if the LSL wiki is beyond your understanding at this time, there are LSL tutorials and classes held inworld at a number of venues for ppl such as yourself. Use the inworld search to find them

@Xuander - go with what Callum recommends. Its a far better basis to go forward on.

try pressing Ctrl+Enter keys (Shout) instead of Enter key (Say)

maybe llPursue(...) ? if you are using that

when you pasted it, it would have been useful if you had of indented the lines of code with tabs and spaces. Formatted it. Nevermind, is ok but next time ok First 2 hacks. I am doing this off the top of my head here. So the outcome might be variable. Anyways, here goes: Hack #1: at top of the script replace say_message(...) with this float MyFade; string MyMessage; say_message(string message) { llSetTimerEvent(0.0); llSetText(message, <1.0,1.0,1.0>, 1.0); llSetColor(<0.0, 1.0, 0.0>, ALL_SIDES); llSleep(0.5); llSetColor(1.0,1.0,1.0, ALL_SIDES); MyFade = 1.0; MyMessage = message; llSetTimerEvent(2.0); // tick every 2 seconds. } Hack #2: in state on, insert the following timer event code timer() { MyFade -= 0.2; // reduce by 1/5th each time llSetText(MyMessage, <1.0, 1.0, 1.0>, MyFade); if (MyFade == 0.0) llSetTimerEvent(0.0); } Hack #3 has to handle what happens in state scan when say_message(...) is called. State scan already uses a timer event, so we have to hack around that somehow. And is further complicated as say_message(...) is also called in state scan immediately before returning to state on tricky and I will have to think a bit more about how best to do that Hacks #1 and #2 do though do give you something to work on in the meantime ok

i do, but is going to be messy, as a timer is needed to do this, and the script uses states, and say_message(...) is called in 2 of the states, state on and state scan which complicates matters. so before we start hacking a fix for this, can you post your current script formatted please so I can see anything else you might have done since. On the edit toolbar is the Code toolbutton, the button symbol is <>. Press it and paste your script into the popup dialog. do this and I will have current info, enough to post the bare necessary hacks to let you carry on without having to do a major rewrite

yes we have to remember though that OP is by their own posted example relatively new to scripting these kinda things. At this stage in their scripting experience by "universal" I take this to mean they are wanting a general purpose something they can drop into vehicles of their own making. more basically something that will spin the wheels based on their current understanding of how wheels in general work. what OP will come to understand by observation is that once they get their first vehicle working there is more to this than might be expected at first glance like velocity in itself is not the only factor. As animats suggested diameter has a bearing. Like when a vehicle has different size wheels, a drag racer for example. Little wheels on the front, big wheels on the rear. The little wheels spin faster than the big wheels. as you mention terrain, elevation, etc also has a bearing on how wheels works. other things are a vehicle which has wheels of the same diameter yet the wheels can spin at different rates. A motor bike doing a wheelie. Burning rubber. Vehicles doing donuts, drifting, etc OP will come to learn all this in time as they gain more experience in building vehicles. My understanding is that OP at this moment just want something that goes to get started with. Which I would encourage them to do, get something going. And as their understanding grows then they will like everyone else apply this growth to further their work.

another thing we can do to help with animation issues is check for agent who might be currently animated and stop their animation before requesting permissions from the next agent. Example: string anim_playing = "something"; touch_start(integer num) { if ((llGetPermissions() & PERMISSION_TRIGGER_ANIMATION) && (llGetAgentSize(llGetPermissionsKey()) != ZERO_VECTOR)) { llStopAnimation(anim_playing); } llRequestPermissions(llDetectedKey(0), PERMISSION_TRIGGER_ANIMATION); }