Innula Zenovka

I've been trying to think when I might want to use it. I mean, the most common reason for llGiveMoney failing is if the money isn't there, and the most common use for llGiveMoney is to pay a percentage of something that's just been paid to the object (a tip jar or a commission vendor) so that's not normally an issue. I am sure there are times it will be really useful, but I can't think of one off-hand.

Since a script can't do anything unless it's in an object that is rezzed in world, I'm wondering if this "Syntax" thing isn't an attachment the OP was persuaded to wear, which is somehow designed to crash the viewer on_rez by flooding it with llDialog menus or something. That would explain what I think is being described. If that's the case, trying to relog in a no script sandbox might let you in, and then you could remove all attachments and get rid of the thing that's causing the problems.

The only way I can think that your rug would suddenly stop being a rug and turn into "a funny shaped box" is that when you were trying to resize or retexture it, you managed to change the object from being a sculpted prim to being a box by changing the drop down for "object type" Did the object tab start by looking like this and end up looking more like this? Try switching it to Sculpt and see what happens, anyway.

The blog FabFree might be worth following. They cover freebies, group gifts and hunt prices for both men and women.

There's a number of reasons for this error message (see Maestro Linden's comment in the jira). The short answer is that it can be caused by trying to something that is, itself, trying to rez things (a temp rezzer or some forms of teleporter), in which case your friend might have better luck in a no-script sandbox. Or it could be a temporary problem with SL -- I now and again get that message on my home sim, but if I try half an hour or so later, the problem seems to resolve itself. Otherwise, as I understand it, your friend will probably need the assistance of a Linden to resolve the matter. ETA -- I doubt this is because of Linden trees, myself; when that's the problem you get -- or I did, the one time it happened to me -- a very specific message telling you that you can't rez Linden trees in that parcel (or words to that effect).

I don't know about "main" but certainly an important reason might be that the "industry and media expectations" were, on any sober analysis, unrealistic, I guess. What was the main reason for the dot-com bubble?

Yeah, if you're using old drivers, then it's not an issue. I rolled my driver back to 260.99 and could log in with with any viewer, without problems. But if I used any more recent driver, I had huge difficulties logging in until Runitai Linden got his Shining fixes working. It's a combination of the new code for mesh-capable viewers and Nvidia deprecating the the fixed function, at least according to https://jira.secondlife.com/browse/SH-2240 Certainly the only viewers I've been able to use without difficulty on more recent drivers have been either old ones (based on 2.7.n and earlier) or very recent ones that include Runitai's new code.

You can now use PRIM_LINK_TARGET to make a list of prims to affect in different ways, like this llSetLinkPrimitiveParamsFast(1,<some parameters>,PRIM_LINK_TARGET,2,<some other parameters>,PRIM_LINK_TARGET,3,<some more parameters>...]);

I use a server for that sort of thing when I have to, though I'd normally prefer to shop around for a sculptmap that can be freely redistributed (or nag my business partner into making one). @Qie -- a typical scenario would be if you're making -- for example --- a drinks dispenser that gives out glasses of whatever people choose. If you're selling the dispenser, the wine and beer glasses "inside" it have to be copy transfer for the next owner, or it will give him drinks but not anyone else, and if you've bought the sculpt maps of the glasses, you probably can't rely on the purchaser to set the perms on those. And, in any case, the licence under which you -- the maker of the drinks dispenser -- bought the sculptmaps probably doesn't allow you to supply to your customers with copy-transfer glasses inside it.

You might try following this blog: FabFree -- Fabulously Free in SL

You get the bonus 45 days after signing up for Premium Membership. I know there was a bug affecting Le Tigre RC channels and teleports to Premium Sandboxes, which I thought had been fixed but maybe not, so try tp-ing to a Premium Sandbox from somewhere else. I've noticed this SecondLife Resident thing, too, now and again, over the last few days. From memory, I've just clicked on the name and it's taken me to my profile (not that of SecondLife Resident) and that's made the problem go away, at least for a while (I'm wondering if it's something on my PC removing a cookie that it shouldn't). I know the website has been having issues lately, though -- for a couple of days, half my Land Use Fees calculator was in English and half in French, though that now seems fixed -- so it could be the site is acting up. Now you're a premium member, of course, you can ask Live Help for their assistance, in case there's something at LL's end that needs attention.

Yes, you can wear several things on the same layer (so, two alpha layers) but only with a viewer based on V2 or V3. So you can wear two alpha layers with the Official Viewer or Firestorm, Dolphin, Catznip, RLV etc. but not with Phoenix.

Hi, Lseven and welcome to the forums. The process for applying to have your ballroom listed in the destination guide is explained here: https://wiki.secondlife.com/wiki/Destination_guide

If you search for gears or cogs in the Marketplace, and then narrow your search down to building components, you may well find what you're looking for.

How do you mean, you need a start function? If you're using llPushObject() you need to grab the key of whoever or whatever you are pushing, so touch_start is only going to work if your victim touches something. You could use collision_start or a sensor, or, I guess, you could grab their key in a listen event.

Yeah, but when I want people to pay me, in RL and both, I try to make it as easy as possible for them to hand over the dosh. I really don't see why it shouldn't be an option, if you find yourself locked out of your account like that, to authorise LL to sell your L$ at the market rate (and to take a fee for so doing) to set off against your debt. It can't take much more time to do that than it does to explain to someone you can't do it, and you could charge them for the service.

I don't quite understand the problem. Here's the structure of the script, at least if I've properly understood what you're trying to do. Why not put together a basic version of the script as you want it, rather than with these meaningless placeholders, and post that if you're still having difficulty? That way the logic of what you want the script to do would be clearer, and I think you would find it easier to understand, too integer handle;list buttons;list MainMenu = ["Emote","Thank Emotes"];list thank = ["Thank1","Thank2","Thank3"];list emotes = ["Blow Kiss", "Wink","Example4","Example5","Example6","Example7","Example8", "Example9","Example10"];string my_name;key av;default{ state_entry() { my_name = llGetObjectName(); } touch_start(integer total_number) { av=llDetectedKey(0); llListenRemove(handle); handle = llListen(99,"",av,""); llSetTimerEvent(20.0); buttons = MainMenu; llDialog(av,"Please choose an option",buttons,99); } listen(integer channel, string name, key id, string message) { llSetTimerEvent(20.0); if(~llListFindList(MainMenu,[message])){ if("Thank Emotes"==message){ buttons=thank; } else if ("Emote"==message){ buttons = emotes; } llDialog(av,"Please choose one of the "+llToLower(message),buttons+["Back"],99); } else if ("Back"==message){ buttons = MainMenu; llDialog(av,"Please choose a colour",buttons,99); } else{//it must be from a sub-menu llListenRemove(handle);//stop listening if(~llListFindList(emotes,[message])){//whatever the message is, it's from the "emotes list" llSetObjectName(llGetDisplayName(id));//change the object's name to the user's display name string str; if("Blow Kiss"== message){ str = "blows a kiss"; } else if ("Wink"==message){ str = "examplegoeshere"; } else if ("Example4"==message){ str = "examplegoeshere"; } //and so on llSay(0,"/me "+str); llSetObjectName(my_name); //change back }//end of what to do if it's something from the emotes list else if (~llListFindList(thank,[message])){//it's one of the messages from the "thank" list //so do whatever you want .. no need to turn the listener off, //because you did that as soon as you discovered it was a message from a sub menu llRegionSayTo(av,0,"Sending this emote to local: "+message); } } } timer() { llListenRemove(handle); llSetTimerEvent(0.0); }}

Yeah, but that's if you're on damage-enabled land and you suffer >=100% damage. That teleports you home directly, without ejecting you first, and explicitly tells you that you've been tp-d home because you were "killed". On the OP's account, that's not what happened.

You can only have been ejected and teleported home by an object that belongs to the landowner (or the group that owns the land) so this can't have happened in an LL sandbox. It must have been a private one (and, while I'm not sure, I suspect it must have ejected you to an adjacent parcel owned by the same person or group that owned the sandbox and the ejector for llTeleportAgentHome to work). So I doubt it can have been a griefer that did this to you -- it must have been the landowner. llEjectFromLand and llTeleportAgentHome are two separate functions, both of which can fail under certain circumstances so you would sometimes want to use both. I wouldn't normally make an ejector that ejects and then teleports home (I'd teleport people home first, then eject them if that failed), but clearly someone has done.

I'm in two minds about this, Carole. Where actual photographic images of a child are involved, there's a clear victim. And this is one of the reasons, quite rightly, the law takes such a dim view of people downloading images of sexual assaults on children -- because it clearly encourages such assaults to take place, so people can produce the images and sell them. With non-photographic images, though (of the sort that might be produced in SL and prosecuted in the UK under Section 62 of the Coroners and Criminal Justice Act rather than The Protection of Children Act or the Criminal Justice Act 1988, that doesn't apply. There's one argument that such images tend to legitimate photographic images that involve the abuse of actual children, but to my mind, though, by far the strongest argument is that the production and use of eroticised images of children provokes such disgust in most right-thinking people the law should ban it, regardless of what harm it may or may not do. The harm, that is, is done to the public at large. It's a dangerous line of argument, I accept, which is one reason why the bar for prosecution is so much higher for non-photographic images than it is for actual photographs (which need simply to be "indecent") -- this absurd filter won't even let me quote the relevant Act of Parliament without bleeping stuff out, so people will have to look at the tests here. But I think it's the strongest, since it's based on the undeniable fact that most people are genuinely shocked and outraged by such extreme imagery rather than on some hypothetical harm that might be caused.

Randall Ahren wrote: Apple concludes: The copying is so pervasive, that the Samsung Galaxy products appear to be actual Apple products. Sadly, the same accusations could be made about SL's copying of the wall feature from Facebook I don't understand. By no stretch of the imagination could anyone mistake their Facebook page for their SL "wall" or vice versa. So, I guess the statement "the same accusations could be made" is true, but it's pretty groundless. It's no more justified, to my mind, than is saying OpenOffice or LibreOffice are "copied" from Microsoft Office -- the functionality is broadly the same, you're never going to confuse the one for the other. Just take a look at your Wall and at a Facebook page, and you'll see what I mean. Indeed, the differences between Facebook and SL are considerably more pronounced than those between the various Office-type products, in that the Wall feature is pretty minor adjunct to LL's main product rather than, as in Facebook's case, the product itself. To my mind, the idea behind the Wall is to enable people who are used to keeping in touch with their friends via a variety of online media to touch bases with their SL friends, when they have a bit of spare time they can't, or don't want to, log into SL, to do it within the SL website rather than to have to go to Facebook to do it.

All you need to do to make that script compile is take out the lines else if ("Blues"==message){ buttons=blues; } else if ("Greens"==message){ buttons=greens; } They'll make it throw an error because you don't, in your example, have a list anywhere defined called blues or greens.

I don't know anything about the law in America but I know a bit about English law relating to this sort of thing. As to the Coppertone advert, it's nothing like what our law deems a "prohibited image" of a child. The test for actual photographs is a lot less rigorous; there the question is, are the jury sure it's "indecent" in the everyday sense of the word. And since many jurors, not to mention judges, lawyers and police officers, will have the sort of baby pictures of their children to which you allude, they're hardly likely to consider them "indecent." Part of the standard directions judges over here give to juries is that they should not leave their common sense outside the courtroom door; on the contrary, the collective common sense and judgement of 12 ordinary men and women is a vital part of our legal system. And that's not the judge flattering the jury.

I think you are going to need to post the full script. We're glad to help, but without the full script, it's just a guessing game. If you post the whole thing, we should be able to spot the problem area pretty fast.

I think removing identifiable information is just going to cause more rants, because in that case, people are simply going to blame every bloody thing that goes wrong, from the fact they keep on crashing with the new Firestorm to the failure of the Marketplace to deliver something, on the fact they are on, or might be on, an RC channel, and LL is hiding from them whether they are, in fact, on a RC channel and, if so, on which one ("Why won't LL tell us, eh? You answer me that. It's because they've got something to hide, that's why!").