elleevelyn

if we have the gestures to go with this then in lots of places we either get muted or kick banned by grumpy parcel owners. The big meanies !!!

^^ this pretty much yes is on us to consider and appreciate when our attire is appropriate for the occasion the onus to abide is on the wearer. As adult people in the RL we know whats appropriate and whats not. In SL is no different, we do know, and I don't ever accept that somehow we don't know i am neko, and I also have some involvement with a Adult-rated venue of some longstanding. I am fully aware of what is and isn't appropriate attire. I have a zillion outfits which are not appropriate for the venue. And so do our region patrons. Sometimes, not often at all, we might get a visitor who wants to be play the disingenuous. We don't entertain it. They're gone also I think that the rules are more about the wearer than about the parcel owner. As they should be. You are wearing the child avatar, not the parcel owner. If you as a child avatar want to make it about the landowner then the answer is no. You are the one causing the issue, you're gone. And if by gone this means Linden banhammers you out of SL altogether because you don't want to address your own behaviour then then oh well and I don't care

this song has kinda become an anthem for Isle of Man TT. The people who do the TT are pretty insane i read a comment on one of these vids: My 250cc listened to this and now thinks is a 1000cc. kehehe 😹

the Object script can follow the same style as the HUD script example that Tessa showed longhand example integer chan = 15113234731; // strided list where color vectors are adjacent to the user-defined name list colors = [ // name, color "gold", <226,201,111>, "rose gold", <240, 158, 111>, "silver", <168, 168,168>, "gunmetal", <67,67,67> ]; default { state_entry() { // listen only for owner llListen(chan, "", llGetOwner(), ""); } changed(integer change) { if (change & CHANGED_OWNER) llResetScript(); } listen (integer channel, string name, key id, string msg) { // look up colors list to get index of msg integer index = llListFindList(colors, [msg]); if (~index) // msg found { // color vector is at index + 1 vector color = llList2Vector(colors, index + 1) / 255; llSetColor(color, ALL_SIDES); } } }

grabbing physical objects and moving them was part of the New User Orientationl back in the day. I dunno if it still works but the tutorial path on Orientation Island Public has a grab tutorial station down by the creek below the temple. Grab the ball on the ground and place it on the table. Not part of the tutorial was throwing the ball off the island, but a few people would give that a go as well

with a significant value sudden devaluation then a way that this can be done is overnight. We log off with L$250 in our account. The next day we log in and our account balance is L$500. The suppliers according to their own timetable adjust their prices accordingly the other way this can be done is to adjust the money supply. To devalue, Supply Linden starts pumping LS into the Lindex. To revalue Supply Linden turns off/turns down the pump a few years ago now Linden appeared to do this. Supply Linden appeared to be pumping approx. L$10 million blocks onto the Lindex on a regular weekly basis - the effect was the exchange rate moved to about USD1 = L$350. Was a whole lot of chatter about this at the time all over. Then after some time the pumping rate slowed and the exchange rate moved back to USD1 = L$250 only Linden could tell us what this was about (and they have never said). But it did mirror the mechanics of how to devalue and revalue a currency in a domestic market using money supply

to grow a domestic economy relative to another target (foreign) economy then we devalue our currency relative to the target. We don't revalue it as OP proposes instead of revalue USD1 = L$100 from USD1 = L$250 then if do anything then devalue USD1 = L$775 the effect of this is the foreign buyers (SL Account holders of USD) are able to obtain more products and services within the domestic SL economy. The ability to obtain more means that the buyers are able to spread their L$ to more suppliers, and/or provide more L$ to fewer suppliers the issue OP highlights is that the suppliers affected by revaluation/devaluation are foreign suppliers - SL creatives who extract value - USD currency from the SL domestic economy. Following from this, when it becomes uneconomic for foreign suppliers to extract value from a domestic economy then they stop supplying products and services. However, stopping supply only happens when there is a oversupply of suppliers; and/or when there is an undersupply of local currency within the domestic economy revaluing to USD1 - L$100 creates an undersupply of local currency. This has a far more detrimental effect on the economy than does the movement of foreign suppliers in and out of the market the fortunes of individual foreign product and services suppliers is of far less importance to the robustness of a domestic economy than is the supply of local currency. Or in other words: Where there is a customer - a supplier can always be found. When there is a supplier - a customer cannot always be found so if anything was to change then devaluation, not revaluation

given that the stated aim is for the NPC to act as a tour guide (with the ability to give a tour guide patter and answer questions about the tour locations) then is not a overly-complex project, and some people (not just new accounts) be into doing this the NPC would not (should not) be able to go to regions it knows nothing about it gets complex should the NPC accept friend requests and should it be able to correspond in IM (thats more complicated as the chat between user and NPC can become untethered from location) as a tour guide working to a set of tethered/known parameters then a reasonably simple NPC project. As a untethered friend then not simple

i haven't done any testing, but I think with Newton then is about up to 24 iterations (precision) on a 32-bit float type, breaking early on match thinking about the quake method a bit more then we can get a union of some kind using fui() and uif() from the LSL Combined Library which I am not going to test as would be terribly slower (two calls to llPow) than llSqrt this said, even if we did this then as I haven't tested it (so not sure what the fui() bit arrangement is) then if the bit arrangement is something other than a C-like union then the magic number would be something other than quake which would be discoverable but yeah so agree with your TLDR. Use llSqrt

i think the best we can get without using any LSL library function is the Newton example. Probably using the precision parameter from the babylonian example for finer control on the result not sure tho that it would be any faster than just using llSqrt the quake method (Q_rsqrt) might be possibly faster if there is a substitute method for the magic number 0x5f3759df, but I dunno what that method might be, or even if there is a substitute at all

just on this. When we use Other People license (closed or open source) is still incumbent on us to do our own legal due diligence when we include a licensed work in our own work for example, just because I include a Public Domain notice in a script I might post to the Scripting Library it means that the Public Domain notice applies only to the script as a whole body of work. My Public Domain notice doesn't mean that I am necessarily the legal owner of all methods that may be included in the posted work. Methods can be encumbered by patents and/or user licenses that can come back and bite us when we not careful pretty much yes to both points generally in most countries we can't dictate on-sell prices unless the product is part of a franchise agreement and in most countries we can encumber a user license with pretty much anything we want (Linden Terms of Service for example), provided that we also provide a legal dispute remedy. Is not enough to just say to the customer that the legal remedy is DMCA. We typically have to do more than this not making a User License available before purchase, is usually legally actionable as a dispute. In this case we could petition Linden to make us whole. Get our money back and remove the product from our inventory. If Linden doesn't do this then we can use the Linden Dispute Arbitration process. https://wiki.secondlife.com/wiki/Linden_Lab_Official:Terms_of_Service_Arbitration_FAQ basically in the do-nothing case we sue Linden for enabling this to happen on their site however, from what Orwar says the seller has addressed this issue by providing a Demo Product accompanied by a User License. My assumption is that the demo is not the Full Product which the user can buy after reading the User License we received the User License before we purchased the Full Product. Typically in this case the act of purchase after receiving the User License would be seen as agreeing/signing in most jurisdictions

this is what I do i can tho easy use all 38 attachment points after linking all I can i consider myself still naked after attaching all body, hair, neko ears tail, wings + jewels. Jewels and body piercings I wear heaps off as standard me so not typical of most other people. I also have 6 huds that I wear standard me. I am a bling bunny so yes I have to ration my actual clothing due to the current 38 attachment limit sometimes I think I would like more but am pretty sure that I would use them all up as well and still want more Pretty Linden please. So I can be a double bling bunny 😻 is the same with layers. Back in a previous life when baked layers was being introduced, like how many layers would be reasonable? I said at that time I could use 22 layers just for face and body, nevermind additional for clothing layers. Since BOM layers came I can use about 40 just for face and body, nevermind clothing layers, without even trying

this ^^ breaking it down integer beginswith(string str, string substr) { return llSubStringIndex(str, substr) == 0; // return TRUE when str begins with substr, else return FALSE } // do it with the NOT operator integer beginswith(string str, string substr) { return !llSubStringIndex(str, substr); // returns TRUE when str begins with substr, else return FALSE } // inline it for efficiency if ((ItemType == INVENTORY_SOUND) & !llSubStringIndex(ItemName, "Radio: "){} // TRUE & TRUE == TRUE

i agree with this approach. The only time an existing code should be deleted (or reverted after a bad edit) is when there is an actual bug in the code (bug in this case meaning the example doesn't actually do what it purports to do) editing code can also break (introduce a bug or introduce a behaviour that was not intended by the orginal submitter) a instance of this came about some years ago due to a convo over the street. The convo lead to discussion about a modification to an existing LSL wiki general purpose method that would make the matter being discussed be slightly more performant somebody edited the existing LSL wiki code entry as a result of the discussion, which broke the generality of the LSL wiki method. An edit which had to be reverted. The editor didn't understand that negative zero and positive zero are two different things even tho in most common use instances they equate to the same value

llSay(PUBLIC_CHANNEL, ...) vs llSay(0, ...) stylistics can make people go nuts sometimes