Corrade is a multi-purpose, multi-platform scripted agent (bot) that runs under Windows or Unix natively, as a service or daemon whilst staying connected to a Linden-based grid (either Second Life or OpenSim) and controlled entirely by scripts. We like to think of Corrade as a bridge, that gives access to viewer-commands to LSL scripts. Corrade does not stop at providing viewer-commands to LSL scripts but reaches into the Internet of Things (IoT), Big Data and Artificial Intelligence (AI) by implementing the latest technologies and communication protocols. Corrade's target audience consists of programmers that will use Corrade as a building block and then create an end-product.

Scripting templates in various programming languages are provided in the Corrade store (for free) that are meant to provide a starting point for programmers by illustrating some of the aspects of programming with Corrade. The templates can be changed or created differently (or better) by a programmer that interfaces with Corrade. If a specific targeted application is desired that requires a scripted agent, then chances are that a programmer would be able create one using Corrade. At the current time, Corrade is a mature project, with almost two decades of experience and history in SecondLife and OpenSim, with a large number of issues solved, bugs fixed and nearly all of the SecondLife API being implemented and offered through the API. Corrade releases are now infrequent due to the coverage being almost complete, with a few missing parts that require upstream changes that we do not wish to challenge. After so much time, we are proud to say that Corrade sets the standard in what regards interfacing with virtual worlds being one of the first precursors to many developments and being used by many creators to automate various tasks.

The Corrade binary can be executed from the extracted folder directly on all supported platforms however the canonical way to run Corrade now is using some containerization technology such as Docker that can be ran both on Windows and Linux.

If running manually on Linux, the libgdi library will need to be installed in order to process images. Furthermore Corrade might need an older version of libssl installed depending on the version that might not be backported anymore by some Linux distributions. These requirements are not necessary if Corrade runs under Docker and the extra security due to the containerization is always welcome.

Whether running under Docker or manually after having solved the dependencies, upon executing the Corrade binary, whether that means starting the program on Windows or running the Corrade executable on Linux, Corrade will mention that no configuration has been found and that a webserver named Nucleus has been launched in order to perform an initial configuration.

Nucleus listens on all addresses so if Corrade is installed on the local machine then the Nucleus interface will be available at following URL:

• http://127.0.0.1:54377/

on the machine running Corrade. If Corrade is running on a different machine, then the Nucleus web interface can be accessed through the network by pointing the browser to http://TARGET_MACHINE:54377/ where TARGET_MACHINE is the hostname or IP address of the machine on which Corrade has been launched.

Upon accessing the Nucleus web interface, log-in using the default password nucleus (this can be changed later by copying NucleusConfiguration.xml.default' to NucleusConfiguration.xml and then changing the password) and a configuration form should now load up.

As a reference, the minimal fields required to get the bot connected to the SecondLife grid are the following:

• Login → Firstname, Lastname and Password - these are the credentials of an existing account in SecondLife that the bot will use to connect to the grid,
• Groups → Group name and Password - the group corresponding to the group name must exist in SecondLife and the password can be any made up string; the default [Wizardry and Steamworks]:Support group can be edited or removed

Once the configuration is complete, click the Commit configuration and wait for the bot to connect to the grid.

In case the bot is unable to connect, the error logs can be inspected using the Nucleus web-interface by browsing to the Logs section in order to determine the cause. One trick, is to shut down the bot and delete the CorradeConfiguration.xml file manually and then restart the bot in order to go through the initial configuration phase again and hopefully set up the bot correctly. In case all else fails, you can file a ticket and we'd be glad to assist provided that the request does not involve setting up auxiliaries such as Linux or Docker for which help is better sought on their corresponding forums or support pages.

• Corrade can run on the following platforms and architectures:
  • Linux (Linux users need to install the libgdiplus library and OpenSSL version 1.x otherwise the error "No usable version of libssl was found" will be reported when attempting to run Corrade)
    • Linux 64bit,
    • Linux ARM 32bit,
      • ARMv7 or more required (please check your hardware),
      • Raspberry Pi first generation (v1) are not compatible since they have ARMv6 which is not supported. The following will not work: Raspberry Pi v1, v2, Zero v1, most of which are now outdated,
  • Windows
    • minimum Windows 7, or any Windows after Windows 7
• 100-350 MB RAM with all options turned on.
• DSL onward (Linden Lab recommends cable, not wireless).
• Corrade uses the exact same firewall ports as any other view in Second Life. Additionally, any Corrade feature that requires an additional port will have to be forwarded to the machine that Corrade runs on.

The latest Corrade is available at:

• Corrade

where higher version numbers, from left to right, represent the more recent versions (ie: a release with version number 11.0.1.2 would be newer than a release with version number 11.0.1.0).

You can find basic tutorials on how to interact with Corrade on the tutorials page.

The application programming interface can be found on a separate page and describes all the commands that can be sent to Corrade along with examples.

• Corrade application programming interface (API)

• For tips and tricks on programming with Corrade, please see the scripting considerations page

• Various attack vectors on Corrade and how to mitigate them are presented on the Corrade security page.

• For performance improvements please see the Corrade performance page.

• Please see the frequently asked questions page.

You can find scripting templates (that also function as test harnesses) in Corrade's store on the Second Life marketplace:

• Corrade Template Store

they are demonstration scripts that could provide you with a starting base for programming with Corrade.

Docker is now the canonical way to run Corrade and it should be the preferred method regardless of the operating system. Docker is easy to use, will just ask for an image and then Docker itself will manage process starting and restarting which has been a challenge for users in the past, in particular on Windows.

• https://hub.docker.com/r/wizardrysteamworks/corrade

The Dockerfile can be found amongst the docker build pages along with a matching compose file.

• https://hub.docker.com/r/fixedbit/corrade by Coal Edge

If you need help with Corrade (installing, setting up, general questions), we can be contacted by using the contact page.

If you would like to request a feature or report a bug, please use:

• The Corrade bug reporting system.

To create a bug report, please make sure to provide a minimal, reproducible and complete example of the problem you are experiencing. This roughly includes creating a test scenario with the following points in mind:

• include minimal code snippets, screenshots or a video that illustrates the problem without providing a large code listing that may have other problems that do not necessarily pertain to the software you are opening a bug for
• all the required parts of your testing scenario are either provided or documented and thus complete, ie: "using the software this version, configured in this way, on this operating system, and running the following code, [… etc …] the software does this and it should be doing that instead"
• make sure that your testing scenario will produce the issue you are filing a bug report for illustrates the issue every time you run the scenario thereby being reproducible - if it is possible to check from different environments, ie: Windows, Linux, from different network locations, etc then please do include the extra testing

Additionally, please be aware that we barely can provide any support for products that are not made by Wizardry and Steamworks. We cannot take upon ourselves the responsibility of other products and it would be wrong to do so; this includes various operating systems, such as how to set up various Linux distributions, or in-world commercial items to which we may not even have access to or would require purchases on behalf of Wizardry and Steamworks.

Wizardry and Steamworks Project-Closed and Open-Derivatives License 1.0 (WAS PC & OD 1.0)

Wizardry and Steamworks allows the use, commercial use, private use, copy, redistribution and sublicensing the Software without prior consent from Wizardry and Steamworks provided that attribution is granted in a visible and reasonable manner to Wizardry and Steamworks, no reverse-engineering is permitted of any distributed binaries or binaries of work licensed to Wizardry and Steamworks connected to the Software, no warranties are provided with the Corrade software nor with any other works related to the Software and that no warranties shall be implied whether in an action of contract, tort or otherwise, arising from, out of or in connection with the Software or the use of other dealings in the Software.

Permission is hereby granted to extend the license (WAS PC & OD), including its restrictions, limitations as well as benefits, to any material licensed to Wizardry and Steamworks, when the intent is to re-use material published by Wizardry and Steamworks, for creations or derivate works, that interact with or include Corrade as a component of those creations or derivate works, regardless of any other license or terms (GNU GPL, MIT, BSD, etc.) that may apply to the material previously licensed to Wizardry and Steamworks.

• Logos and Vanity Items