| Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
|
|
disable, but well many things can go wrong.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a bit;
|
|
instance with ini file option BanLineSafeHeight
|
|
|
|
|
|
|
|
|
|
|
|
|
|
changes. There flag it is need with InvalidateDeepEffectivePerms(). Add config options PropagateGroupShareOutwards and PropagateAnyOneOutwards
|
|
they should be use to bypass normal delayed updates, for debug
|
|
|
|
|
|
Instead, handle the port being 0 as "any port" and assign a random
port for regions in that case.
|
|
This field started out as a simple flag in the protocol to indicate a
user being a SL charter member. It has since then taken on additional
functionality that means that the name is no longer appropriate.
|
|
|
|
|
|
|
|
|
|
physics single caps message per selection request
|
|
info), where info in info message field. only minimal testing done
|
|
|
|
|
|
|
|
|
|
|
|
and its use even worse
|
|
|
|
|
|
|
|
interregions invite/eject messages, etc
|
|
transferred. This is a work in progress. All permission assertions are commented for now. Will get back to this later when permissions are fixed by Melanie.
|
|
(regression) Putting back the heavy messaging.
|
|
regression. Took the opportunity to refactor that code, so that both Groups V2 and XmlRpcGroups can use the same function.
|