When teleporting using Hypergrid, show more informative error messages in case of error
Better error messages in RestClient
Reduced log levels for REST 404 errors to DEBUG
Move new Estate commands to OpenSim.cs

Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
BulletSim: Minor Fix to vehicle hovering, add more ways to disable it.

Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
Add Varregion support to Terragen Handler

Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
remove some whitespace that snuck in with last patch
Fix sp.AbsolutePosition when agent is sitting on a child prim, which in turns fixes llDetectedPos(), llGetLinkPrimitiveParams() and similar functions.

Add regression test for this case.
In relation to http://opensimulator.org/mantis/view.php?id=7043
fixed object-collision issue after uncheck phantom-flag

Signed-off-by: Michael Cerquoni <nebadon2025@gmail.com>
Don't re-retrieve sit part in SP.HandleAgentSit() when we already have it.
Revert "Don't re-retrieve sit part in SP.HandleAgentSit() when we already have it."

This reverts commit 2c00b73cd27a7183a5c105b4e2865f11e4a00d98.

Wrong code change
Don't re-retrieve sit part in SP.HandleAgentSit() when we already have it (this time with the right code change)
Pass the correct position to QueryAccess() instead of UUID.Zero (it was wrong in one place)
When preparing a Hypergrid teleport, tell the receiving grid which user is 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.
Fixed: during a teleport we always sent the error "The teleport destination 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.
Refactored: use Scene.GetAgentHomeURI() to get the Home URI of a user
When sending QueryAccess to a region, also send the user's Home URI
Avoid calling HELO service on malformed URLs. This is in response to an exception reported by danbanner.
Better (amend to previous commit)
Allow invalidating the users cache