Fly permission being overridden
tracked
Crexon Resident
The no fly setting on regions currently has an exploit where a land owner can set no fly on the land, but viewers can still enable flying for users. I believe this was a long standing issue where override fly permissions was removed from the LL viewer but never removed from the server code, so viewers just left it in.
I've been trying to find the exact patch notes for the viewer when it was remove but unable to find it right now. The issue still stands of the server not respecting land permissions set by land owners.
Log In
Silvilein Crystal
Leider habe ich das schon seit wochen :( Oder ich fliege aus SL im TP :(
Unfortunately, I've had this for weeks :( Or I'll be kicked out of SL in TP :(
Bleuhazenfurfle Resident
More likely the server just doesn't check for flying at all — it has no real need to do so, if the viewer is following the rules.
Being able to force flying is also rather useful, though, when you get stuck in terrain — I generally have force flying enabled, but I still try to obey the no flying signs.
This is also something that scripts can watch for, and send out nasty letters or whatever when needed.
What viewers probably
should
do, is turn off flying override when you're not supposed to be flying, thus forcing the user to explicitly turn it back on, and announcing them as knowingly flouting the rules (and throwing up a warning dialog when they do so). Another, is the viewer could make flying a little harder when you're overriding no-fly, like requiring you to double-tap the key to get into flying (again, so everyone knows you're flouting the rules intentionally, rather than simply having not noticed).Lucia Nightfire
Would be great if we had a llFly(key target, integer flying) LSL function.
If called from a land owner object, it could turn off flying status. If called from a self/public owned object, it would require perms/exp perms.
Maestro Linden
tracked