Differences

This shows you the differences between two versions of the page.

--- avadroid [2025/12/27 05:32] – robyn
+++ avadroid [2026/01/02 06:44] (current) – robyn
@@ Line 16: / Line 16: @@
   * **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.
+==== Is an AvaDroid a scripted agent? ====
+  * The AvaDroid system is controllable by a human like any viewer. It is a web based/in world, non graphical viewer similar to [[https://github.com/cinderblocks/radegast|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.