12-30-2004 20:08
I don't post much. Naturally, when I do, I actually have something on my mind. :rolleyes:

Most of these features came about due to issues I've had with the system. Others are just suggestions I've gotten from others.

1) More 3D Dev. Tools in Second Life
Now, I know things like Boolean Operations aren't going to happen with the current system via rights to abuse it, but how about a knife tool that would allow us to chop a prim right down the middle (or wherever), thus generating two prims representing the cut first one? For example, say we start with a sphere and make an arbitrary cut down the center - this would result in two hemispheres to toy with in the shape of the original sphere. Could be useful - though only for select prim classes. Considering LSLing (a crappy form of) this myself. Otherwise, a few more tools here and there to appease us renegade 3D folks would be nice. :D

2) Local (Client) Sound Support
Simple problem - if you have, say, a game - that relies on sounds, currently you have to have the camera fairly close to the avatar or risk severe dropoff/not hearing the sound at all. How about support for Client sounds, with a permission, that play with no dropoff in the client? I know one of my games needs this. :)

3) Physics Permission on Land
Set a specific world height for these permissions to be enforced in the public sims, and allow it to be set. If a physical object crosses that boundary, either repel it or throttle physics. Logic to this one being so an enterprising prick can't simply spam someone with physical objects above the No Script world boundaries or fire from just off plot.

Speaking of which...
4) Allow island owners to set their own No Script/No Physical Worldheight
Now, I realize this would be bad in the continuous and/or public sims of Second Life, but with regards to island sims... why not? Since they experience less "cross-sim travel" traffic, are usually isolated, and are owned by individuals paying what I consider a hefty chunk of change, this would help aleviate problems like pernicious scripts being spawned/run just above the safezone. Not to mention a boon to the personal sim game devs worried about hacks. :eek:

5) llCalcString
String math. Anyone that's ever toyed with LSL at length knows we want it. Many of us (myself included) have written workarounds with this already, and anyone wanting to store extremely large float or integer values needs something like this, either with a workaround script or a built-in function. I've already done the former. I'd love the latter.

**For those less savvy in LSL, float variables start to lose accuracy in the very high digits - a bad thing - and integers can only store values up to roughly 10 or 11 digits. Anything higher evaluates to -1. Many of us have gotten around this problem by using other variables and some rather laggy code.

6) Allow Group Scripts
Simple one. Only allow scripts to be run that are set to a specific group, either by creator, owner, or both. Another one long-since needed to clamp down on the *ahem* difficult nature of exploits with scripted events.

7) Allow Personal Sim Ban-by-IP
This last is a controversial one, I'm sure. It also has a short story to go with it.

A friend of mine, who happens to own his own sim (sim name and owner omitted) happens to have a problem. See, a select individual, who will remain nameless, happens to be pestering my friend by spamming objects/scripts/etc and forcing the friend to play a twisted game of hide-and-laggy-prim-seek. The person gets promptly banned by my friend, so he just goes and snags a new account and repeats the process. My friend, frustrated, has submitted an abuse report or six, to no avail (as I've been told), probably due to the holidays.

That said, without compromising avatar IP binds to residents (bad, bad, BAD :eek: ), how about a simple checkbox by resident name on the banlist to also ban by IP and backend the rest? This only applies to personal sim owners in the example, since they're again paying megabucks and should have such a privilege to cut down on the number of abuse reports of this nature. But there IS a risk of abuse of this new privilege, hence why I pegged it controversial.

---

That's that. Feel free to leave feedback, but I make no promises to scan the forums again in a timely manner. :p