Lua Viewer Alpha

Currently there are various advanced and developer tools that allow us to enable viewer side options like Wireframe and Hitboxes. Those two particular render options are incredibly easy to abuse in combat regions to give the player a great advantage over others. Seeing through walls and having a brightly colored hitbox to aim at for instance. If we could use client side lua to track the Render Information of avatars in the region and report it to the new Combat 2.0 Combat Log Channel, we could keep track of people abusing advanced and developer tools to get said advantages in gameplay scenarios.

If you push the forward key in an llVehicle, the signal gets sent to simulator, script does something, result of input comes back. What I'm trying to say is vehicles in SL have latency that other multiplayer games don't. If the client can be told basics about the llVehicle it could be making a good guess about what the vehicle should be doing before it gets a definitive answer from the simulator, thus making vehicles appear much snappier as the result of input would be instant client-side Or perhaps even make it possible for a client side script to be authorative on an objects position and run the physics simulation client side, just sending results to simulator for other residents to see? (I'm currently just throwing random ideas out there to see what sticks, sorry if my posts seem excessive)

I think a useful client side script feature would be the ability to cap draw distance. Reason for this is whilst the user usually sets their draw distance as far as performance permits, inside skyboxes, it is often not desirable to render neighboring skyboxes, or one skybox casts a shadow over another etc. If we had the ability to cap draw distance from client side script, a script could automatically cap draw distance when the user enters one of these skyboxes for better immersion

Since client side scripting is being explored and developed I thought I'd express my personal desire to not only expose 'get' and 'set' of client state via script, but also the ability to 'restrict' certain actions For example, for certain types of games, the ability to restrict seeing other players on the minimap would be a useful gameplay mechanic. But the problem is if we only have 'get' and 'set', whilst our lua script might hide the map, another script could then show it again or the player could just open it again themselves. The ability to set constraints would therefor be useful. The constraints could be tied to an attachment assuming we can run lua scripts on avatars in inworld objects such that the constraint releases when the attachment is removed. Other lua scripts would not be able to remove the constraint if that makes sense - so we can be sure the user is not cheating the game. examples of useful constraints might be disallow flight radar/minimap don't show avatars nearby max alt cam distance max draw distance (think skyboxes)