| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
| |
the ball rolling on replacable modules. No user functionality yet
|
| |
|
|
|
|
| |
Change all uses of the HttpServer properties to use the new singleton
|
| |
|
|
|
|
|
|
|
|
| |
needed to be able to 'NAT-wrap' the login sequence.
* If you have something using XmlRpc that isn't in core, change your method signature from:
(XmlRpcRequest request)
to:
(XmlRpcRequest request, IPEndPoint remoteClient)
|
| |
|
|
|
|
|
|
|
|
|
|
| |
LLClientStackModule to new
region modules. This was needed because the stand alone and grid modules weren't deleting
old scenes, which caused an issue when deleting and recreating a region with same name
on same x,y coordinates. Tested it on standalone and issue is fixed. Requires prebuild
to be run again.
Fixes Mantis #3699
|
| |
|
|
|
|
|
|
|
|
| |
Scene.NewUserConnection()
- adding reason reporting
this enforces estate bans very early on and prevents us from
circulating client objects that we'd then have to retract once we
realize that the client is not allowed into the region
|
| |
|
