client_side

I dont know why I decided to post this before I got my rest, maybe its because I do everything I usually put off during the day at night, or maybe im just f*cking insane.


I vote the latter, but anyways, here is the proposal!

Now, I propose a new command, so far we have many commands that can be put to any number of applications ,but these are all done server-side! I propose that LL add a new command, that, if enabled, performs the action only on the owners PC, and no-one elses.

The application of this can be used widely, it can be used in not only sound files, but also with objects, textures, and may also cut down on some server side lag.

Im still debating weather it should be an Event, an integer, or a normal LSL command. Pehaps client_side(key id)?


Now, im going to sleep before I go comatose on my keyboard and ruin it with drool. Besides, my bed doesnt click while I sleep.

Maybe it's me - it's Sunday morning - but I have read and reread our post at least three times, and I still don't know a) what are "big-blue-text-thingies" and b) why you need a LSL event to handle them?

If by "big-blue-text-thingies" you mean the cyan dialog boxes that pop-up with llDialog(), I also fail to understand what exactly do you want to accomplish by a client side event on that.

llDialog() just pops up on the user - but yes, it runs from the server, you're right on that! - but you certainly can attach buttons to a private channel, so that the commands you give are invisible in public - and this will certainly reduce server lag!

Ok, I woke up, let me re-write my post .