An AvaDroid is a sophisticated AI augmented, virtual synthetic entity in the Linden Labs derived Metaverse (Second Life and Open Simulator). It has the following features:

• AI Conversation engine for Roll Play (RP) or companionship. Large Language Models can be selected to suit the RP scenario and supports a tuned system prompt, the AvaDroid's Character Information, Real Time Situational data, Mood, Current activity, Conversation History and dynamic injected data. Various operation modes can be engaged.

• WebGUI. A Web based Graphical User Interface is provided to Control, Configure, Script and Schedule the AvaDroid.

• Inworld Command System. Commands to the AvaDroid can be sent via IM or Local chat. Only registered administrators can command the AvaDroid, using an “!” appended to their name. Commands can be embedded, Example: “Cath! I think it is time to go home” said in Local chat, will trigger Cath, an AvaDroid, to respond and then Teleport Home. There are a plethora of commands including but not limited to Sit, Stand, Touch, Follow, Come. More information in the specific document, Commands.

• Automatic Trigger Response. The AvaDroid automatically responds to Region Restarts (Logs out for 30 minutes and then logs in) so as not to end up at an InfoHub due to the Simulator being offline. They also respond to Dialogs and Permission requests. They respond to TP Offers from Admins.

• Scripting Engine. The AvaDroid can read a script file, a list of commands. They run a special script, “home” when they log in or TP home. A script can be created, it is just a text file, using an editor or through the AvaDroid GUI. Scripts are run with the “load <script file>” command.

• Scheduling system. AvaDroids have schedule system that allows a command to be run on a day at a time. Multiple days can be selected via the GUI. Typically the command will be the load command, example, at 1-AM every day “load reset”. The reset script clears memory and reloads the config file. Another example is scheduling a logoff and or logon at specific times. Any command can be run but some commands don't make sense in a script and will silently fail. An example would be the “come” command, the AvaDroid has no idea who they are to come to.

• The AvaDroid system is controllable by a human like any viewer. It is a web based/in world, non graphical viewer similar to Radegast just the UI (User Interface) is very different and is AI augmented. All viewers run scripts, be it animations, gestures or LSL scripting. An AO for example is a script that automatically runs animations.

• AvaDroids as companions, accompany their owner/administrator and are under full control. They are an extension of their owner.

• AvaDroids as NPCs working as part of a RP (Role Play) scenario typically will be in one region/parcel with the knowledge of the region/parcel owner/renter who will be the administrator/owner. Whilst they may be left unattended to work as greeters or part of the RP story, they are still under control.