Description

When this option is enabled, Corrade will send error messages to Wizardry and Steamworks. Doing so, helps fix very serious bugs preemtively since all error messages are centralized and then fixed in upcoming releases. When enabling this option, some information that can be considred private may be transmitted as part of the process even though Wizardry and Steamworks does not care about that private information except for fixing Corrade issues. The error messages reflect bugs that could potentially cause Corrade to crash - smaller, non-fatal bugs will still have to be submitted directly to Wizardry and Steamworks.

Data Transmitted

Corrade will send the following useful information encrypted point-to-point between this Corrade scripted agent and Wizardry and Steamworks:

  • the Corrade version
  • whether the error pertains to Corrade or OpenMetaverse
  • the error message itself and a stack trace
  • a timestamp when the error occurred
  • the in-world Corrade bot name

This information is used to trace the problem back to the snippet of code where the error occurred and hopefully it is something that can be fixed.

The following information is disclosed implicitly as part of the process since any connection over the internet requires it:

  • the IP address of the machine that Corrade runs on

However, none of this data is useful and thus it is not stored.

Data Retention and Processing

Wizardry and Steamworks does not retain nor redistribute this information in any way to anyone. Once the bugs have been addressed, the error messages would have exceeded their usefulness and the error messages and all other related information will be deleted.

The grid login first name.
The grid login last name.
The grid login password.
The grid login URI.
The maximal range for sensing in-world objects and avatars.
Select a group to modify.
The name of a group that is used for authentication and must be an existing group on the grid to connect to.
The group password is used by scripts to authenticate, has no SecondLife equivalent and is just a made up shared secret.

These are the start locations that Corrade will attempt to start at when connecting to the grid. Region name can also be set to "last" or "home" in order to make Corrade login to the last location it connected to, respectively the home location. The order of the rows can be adjusted such that Corrade will attempt to connect to each location starting from the top and up to the last location at the bottom. In case all locations to connect to have been exhausted and Corrade cannot connect to the grid, then Corrade will terminate.

Region X Y Z
HTTP
The prefix to use for the HTTP server.
MQTT
The IP address for the MQTT server to listen on. The port for the MQTT server to listen on. Whether to use deflate compression for all communication.
TCP
The IP address for the TCP server to listen on. The port for the TCP server to listen on. Whether to use deflate compression for all communication.
WebSockets
The URL for the WebSockets server to listen on. Whether to use deflate compression for all communication.

Even though Corrade commands are much more powerful than RLV, Corrade has built-in support for RLV that can be enabled here.

As per the RLV specification, certain RLV behaviours can be blacklisted and by ticking the behaviour names, the behaviours will be added to the RLV blacklist.

Distributed Caching
The IP address to connect to The port to connect to