| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
asset server is not the same as the simulator's asset server. Unfortunately this still continues to be wasteful -- new assets are created every time an attachment is detached, but the process of storing the new asset goes through the InventoryAccess module, which does all sorts of checks regarding the users' inventory.
|
|
|
|
| |
like copy-paste items in inventory.
|
|
|
|
| |
EstateManagementModule relating to RAW file uploading.
|
|
|
|
|
|
| |
rather than infinite timeout.
This both signals a problem with the URL and eventually frees the thread, rather than hanging indefinitely with no information.
|
|
|
|
|
|
|
|
| |
handle notices to offline users directly as known undeliverable messages rather than discarding or attempting delivery.
Offline notices can still be controlled with the [Messaging] ForwardOfflineGroupMessages setting.
Looks to address more of http://opensimulator.org/mantis/view.php?id=7037
Only for Flotsam now for testing, but if approach works should be possible with core offline notices as well.
|
|
|
|
| |
of xmlrpc and core offline IM modules
|
|\ |
|
| |
| |
| |
| |
| |
| |
| | |
There is a problem here with infinite recursion, but this patch loses the 'hunting' behaviour where the code will attempt multiple lookups if the avatar is teleporting rapidly around different simulators.
This patch only does a single lookup before giving up.
This reverts commit cecb446e0e91ede0b05ea9cf40c1313782241f3d.
|
| | |
|
| |
| |
| |
| | |
version of default user switch for load oar :q :q
|
| | |
|
| | |
|
| | |
|
|/
|
|
|
|
|
|
| |
central services of a Robust server EXCEPT assets. In other words, grids where the simulators' assets are kept in one DB and the users' inventory assets
are kept on another. When users rez items from inventory or take objects from world, an HG-like asset copy takes place between the 2 servers, the world asset server and the user's asset server. This makes the simulators independent of the central asset server.
Note that this an advanced configuration and requires some security strengthening coming up.
|
|
|
|
|
|
|
|
| |
NPCs would be seen by other viewers.
It appears that at least Singularity 1.8.5 (but probably others) rely on attachment FromItemIDs being different to display more than one.
This commit resolves this by generating random IDs instead of always using UUID.Zero for NPCs.
Resolves http://opensimulator.org/mantis/view.php?id=7110
|
|
|
|
| |
5d01a1f
|
|
|
|
| |
rather than in the log.
|
|
|
|
|
|
| |
region co-ordinate.
For debug purposes.
|
| |
|
| |
|
|
|
|
| |
This fixes the issue of "Show in Search" seeming resetting at random.
|
|
|
|
| |
because now JsonRpcRequest() returns an error result instead of throwing an exception
|
|
|
|
| |
both the Simulators and Robust
|
| |
|
|
|
|
| |
of 0 from previous commit cb1f28
|
| |
|
|
|
|
| |
simulator cache)
|
|
|
|
| |
This commit also contains other changes, but they're all just for clarity. The only actual behavior change is to avoid Posting local assets.
|
|
|
|
| |
because it's Obsolete.
|
| |
|
|
|
|
| |
pre-truncate the description of dynamic textures.
|
|
|
|
|
|
|
|
| |
status of friends, so they continued to appear Offline.
This happened because these notifications (the UDP packets) can only be sent to Root Agents. But the notifications were done in OnClientLogin(), at which point the client is still a Child Agent. Since a FireAndForget is used, it became a race condition as to whether the packets would be sent before or after the client became a Root Agent.
To fix this, we now only send the notifications once the client becomes a Root Agent for the first time.
|
|
|
|
| |
value
|
|
|
|
| |
much as they wanted even if the parcel's permissions had since been changed to disallow rezzing
|
|
|
|
| |
object in the parcel even if the flag "Create Objects by Group" was disabled
|
|
|
|
|
|
| |
parcel has a Group set; it doesn't have to be *deeded* to the group
Also some cleanup of the use of Group ID's (with no change to functionality).
|
| |
|
|
|
|
| |
Gatekeeper URI (which is used with Regions); not the Home URI (which is used with Users)
|
|
|
|
| |
land. The objects that are sold together with the parcel of land need to fulfill the following preconditions: owned by the current parcel owner, not set to a group, transferrable. This feature does not work for group owned parcels or land bought by a group.
|
|
|
|
| |
referrer)
|
|
|
|
| |
says "Teleport failed", so adding "Teleport refused" is redundant.
|
| |
|
| |
|
| |
|
|
|
|
|
|
| |
could not be found" to the client. This happened on both success and failure.
On successful teleports this error wasn't actually shown to the user. But on failed teleports this error could hide the true cause of the failure. For example, attempting to use a Landmark that's more than 4095 regions away would result in two warnings appearing in the viewer: "Region too far" and "Destination could not be found". The second message hid the first one, so it wasn't obvious to the user what is actually the problem.
|
|
|
|
|
|
| |
entering the grid.
This can affect which region to use. E.g., returning users may be allowed to enter any region, whereas users from other grids will have to enter a gateway region. Previously per-user decisions were only made later, but by then it's too late to change which region the user enters.
|
|
|
|
| |
wrong in one place)
|
| |
|
|
|
|
| |
Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
|
|
|
|
| |
Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
|