| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
for all bots if no bot number is given
|
| |
|
|
|
|
|
| |
than controlling from the main action loop
This is to avoid excessive and inconsistent delays between behaviours that currently need to embed sleeps in other actions (e.g. physics) and other behaviours.
Might need a more sophisticated approach in the long term.
|
| |
|
|
|
|
| |
or bot it disconnected.
In this case, it is used to turn off jump when physics testing behaviour is removed.
|
| |
|
|
|
|
| |
during operation.
Doesn't currently work very well as stopping physics, for instance, can leave bot travelling in old direction
|
| |
|
|
| |
behaviour <behaviour-name> <bot-number>" console commad
|
| | |
|
| |
|
|
| |
string.join(string, List<string>), or some auto casting is missing
|
| | |
|
| | |
|
| |
|
|
|
|
| |
actually filter out users shown continuously online for more than 5 days
Remove confusion in command output.
|
| |\ |
|
| | | |
|
| |/
|
|
|
|
|
|
| |
online from a standalone/robust instance.
This is not guaranteed to be accurate since users may be left "online" in certain situations.
For example, if a simulator crashes and they never login/logout again.
To counter this somewhat, only users continuously online for less than 5 days are shown.
|
| |
|
|
|
|
|
|
| |
hear chat from their source region for some time after teleport completion.
This occurs on v2 teleport since the source region now waits 15 secs before closing the old child agent, which could still receive chat.
This commit introduces a ScenePresenceState.PreClose which is set before the wait, so that ChatModule can check for ScenePresenceState.Running.
This was theoretically also an issue on v1 teleport but since the pause before close was only 2 secs there, it was not noticed.
|
| |
|
|
| |
This causes extreme console spam if a simulator running latest master and one running 0.7.5 have adjacent regions occupied by avatars.
|
| |
|
|
|
|
|
|
|
|
| |
allow different default regions for HG and direct grid logins.
This requires a new GridService.GetDefaultHypergridRegions() so ROBUST services require updating but not simulators.
This method still returns regions flagged with just DefaultRegion after any DefaultHGRegions, so if no DefaultHGRegions are specified
then existing configured defaults will still work.
Immediate use is for conference where we need to be able to specify different defaults
However, this is also generally useful to send experienced HG users to one default location and local users whose specified region fails (e.g. no "home" or "last") to another.
|
| |
|
|
| |
legacy profiles
|
| |
|
|
| |
just environment variables
|
| |
|
|
|
|
| |
If the port is specified it is added but a ":0" is not added if the port is zero.
This enables the hypergrid address short form "hypergridGateway:regionName"
which is handled by the parser but failed because of this zero port addition.
|
| |
|
|
| |
Attempt to fix Mantis 6740 (http://opensimulator.org/mantis/view.php?id=6740).
|
| |
|
|
|
|
|
|
| |
fails."
This is very similar to my earlier revert in bcb8605f8428a9009a2badf9c9eed06d9f59962c and fails for the same reasons.
Reverting this change because it causes a problem if access is denied to the user.
This reverts commit c7a8afbb8da40e09252d58d95c89b8a99a684157.
|
| |
|
|
|
|
|
|
| |
Fallback doesn't work at this level as the change of destination isn't communicated to the source region/viewer
Reverting because this introduces a bug when access does fail.
More detail in revert of main commit.
This reverts commit ec32c1d4b69e4219fe44a38bcbc411e7996641f1.
|
| |
|
|
|
| |
This exception was very likely harmless since it occurred after the restart had taken place, but still misleading.
Thanks to SCGreyWolf for the code change suggestion in http://opensimulator.org/mantis/view.php?id=6747, though I did this in a slightly different way.
|
| |\ |
|
| | | |
|
| | |
| |
| |
| | |
commit.
|
| | |\ |
|
| | | |
| | |
| | |
| | | |
printed the error message and not the call stack.
|
| | | | |
|
| | | | |
|
| | |/
|/|
| |
| | |
other capitalizations of pCampBot
|
| | |
| |
| |
| | |
fails
|
| | |
| |
| |
| |
| |
| | |
name
Shorter and can do this because bot names are uniform
|
| | | |
|
| | |
| |
| |
| | |
one id
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
CreateAndAddChildScenePresence() since the former was only ever called from the latter
This allows us to remove dead code relating to adding root agents directly to the scenegraph, which never happens.
|
| | | |
|
| | | |
|
| | |
| |
| |
| |
| |
| | |
was wrongly counted as a connect
Also, only sleep when we actually perform a connection
|
| | |
| |
| |
| | |
LoginDelay parameter of pCampbot.ini
|
| | |
| |
| |
| | |
bots whilst pCampbot is running
|
| | |
| |
| |
| | |
which have sit positions but are attachments
|
| | |
| |
| |
| |
| |
| | |
activity timeout, a root connection triggers a CloseAgent to a neighbour region which has already closed the agent due to inactivity.
Also separates out log messages to distinguish between close not finding an agent and wrong auth token, and downgrades former to debug and latter to warn
|
| | |
| |
| |
| | |
console "connect" command
|
| |/
|
|
| |
sit/stand avatars already sitting/standing
|
| |
|
|
| |
that we can distinguish between simultaneous logins
|
| |
|
|
|
|
|
|
|
|
|
| |
local logins."
This approach does not work - it is taking place too far down the login process where really the region checking
could only be done when the hg map tiles are linked on the main map (messy and probably impossible) or possibly
when the final destination is fetched at the very first stage of teleport (which couldn't be done without a protocol
change to pass the agentID as well as the requested regionID)
This reverts commit 3d9b73c47a15cf00150ac80570fea88de8cecbdf.
|
| |
|
|
|
| |
These would be specified in the [GridService] section of Robust.HG.ini, which already lists these in the example text.
Untested patch so that Neb can easily pull in for testing, though shouldn't disrupt existing hg logins since fallback processing is a bit of code stuck on the end of the login sequence.
|
| |
|
|
|
|
|
| |
going to that region first.
If this is attempted, they get a "Try moving closer. Can't sit on object because it is not in the same region as you." message instead, which is the same as current ll grid.
Sitting on ground is okay, since viewer navigates avatar to required region first before sitting.
|
