Acheron Gloom

The server rollouts are weekly... because things do need to be tweaked. Unless you would like to keep everything the same for years to come and let Second Life become stagnant.

I wouldn't consider myself a blind fan of LL, nor am I naive with regards to their faults, I just simply realize their efforts and notice that their work can make a positive difference, too. Oskar's comment was simply saying that by letting your emotions get in the way of things you're not really helping yourself or LL to find the problem. A better method would be to simply send a ticket, post on the forum if you find it necessary even though it probably won't be the first thing seen, and/or send an online Linden the information. Unless you like to think that as a business LL is purposely trying to make their players leave, which I can assure you isn't how a business works, we can assume that they do want to improve SL. As players we should also try to aid LL in improving Second Life and make our own endeavors in doing so. The opposite of trying to aid in improvement, as an example, would be to bash LL at every turn without a rational even given for your complaint. Complaints themselves are fine, its just a matter of going about them in the right way. Also: http://status.secondlifegrid.net/ [postED 7:13AM PDT May 11, 2011] We are currently experiencing issues with some of our central services, which may cause issues with L$ purchases, inventory, teleporting, login failures, and region availability. Please refrain from L$ transactions or rezzing no-copy items until this issue is resolved. Our network team is working on this issue, and expects to have it resolved soon. Please watch this blog for further information. See: 7:13 AM PDT And if you need more clarification, that is seven minutes BEFORE you posted to this thread for the first time. As for an in-world system, I could support that.

You would need llRequestPermissions for the control event and for trigger animations, and then you would need to do llTakeControls for CONTROL_ML_LBUTTON. Then you need the control event to check when you start clicking, and then run the animation. You also need to do a statement checking for when they stop clicking which would proceed to stop the animation. Example: default{ attach(key id) { if(id){ llRequestPermissions(id, PERMISSION_TAKE_CONTROLS | PERMISSION_TRIGGER_ANIMATION); llTakeControls(CONTROL_ML_LBUTTON, TRUE, FALSE); } } control(key id, integer held, integer press){ if(press){ if(held) llStartAnimation("LOL I AM AN ANIMATION LOL"); else llStopAnimation("LOL I AM AN ANIMATION LOL"); } }}

Yes, because Oskar totally said to stop being sniveling big girlies. Wait, he didn't.

Usually armored vehicles have a physical vehicular hull with a collision counting event (collision_start) to count down the HP. Then you have a non-vehicular prim that follows around the hull. The prim that follows the hull uses the llVolumeDetect misfeature to provide invincibility to the user, and once the hull dies it gives off a message telling the volume detect prim to unsit the user and kill them.

I think if, for some reason, you also want to limit their tag while they're using it you can also start doing llSameGroup with the owner. Pretty sure you can change object's groups once attached, though, so you'd have to check that once more.

I was afraid this would be one of those threads filled with complaining, broken english, and flawed logic. Thank you for not being one of those threads. <3