roadmap
Revision from 2023-12-27 17:58:49
The majority of ARES is implemented. Items are removed as they are finished, mostly from the top. Nothing on this list is set in stone or final. Names in square brackets are what system components are involved.
These are to-do items that need to be done but, for various reasons, are annoying and keep getting put off. Exactly when they'll actually get done is anyone's guess.
Vox bugs: dot commands blocked, add filter ignores arguments, duplicated chat
finish core personas
consent request bundling; updatable alerts [security, variatype]
defensive low-power-masking
forget deleted scripts [kernel]
standard external menu HUD (AMenu)
ARES-to-ARES menu access [variatype + menu]
db backup, db load support for character streams (web sources) [db]
policies pt 2: curfew [security]; apparel policy [security]; distress beacon [power], IM policies [security], owner radio policies and exceptions
Nice display of package lists, fully usable menus for package management [libmenu]
animation hoverheight
autolock [policy]
Sexuality is the ARES equivalent of Companion's TESI add-on. It provides arousal, cryolubricant management, tactile sensors, and more. Sexuality is part of the same purchase package as TESI Complete.
Outstanding Sexuality implementation tasks:
Example furniture and devices
Voices
Orgasm nozzles
Fluid production
Reproductive Matrix
Friction
Installer
Wizard
Models
RLV outfit switching
Menu controls
Anim detect (head)
Prevent touch duration accumulation
Anim playback (pelvis)
WARRIOR is an enhanced combat add-on for ARES that adds features originally slated for ATOS/CX. We hope to deliver it around the same time as Beta 1 and Sexuality.
Outstanding WARRIOR implementation tasks:
Targeted damage
Power malfunctions
Update VectorLogix, Arachne X8, ARC, and ExARC to detect and fix ARES power malfunctions
Once ARES hits Beta, we will retire the Supervisor controller, and ARES will start to become available on standard hardware.
begin updating old devices for ARES compatibility
Beginning of converting Companion controllers to new ARES versions, deliver ARES to people who bought those systems; end of availability for exclusive ARES supporter controller
DIAG (short for diagnostics) is a software add-on experience for ARES that simulates malware and logic malfunctions. Its main purpose is to encourage roleplay around repair and maintenance, including a special tech support crew staffed by NS volunteers who help rescue stranded units in the field.
We expect to focus on DIAG after the Beta 1 rollout is finished.
Outstanding DIAG implementation tasks:
Implement main program
Update VectorLogix, Arachne X8, ARC, and ExARC to detect and fix DIAG problems
Update training course website
Organize tech crew
Spring Utilities replacement with new rental, proximity, and cron (scheduler) facilities
Hierarchy/XNMS compatibility [domain]—no server code changes anticipated
not implementing database overlays: this is a cut feature, as the db utility is already brimming
update remaining devices (those that previously depended upon the Companion "internal" message)
Cleanup:
shakedown of interference and security rules
shakedown of documentation completeness
shakedown of guest access
shakedown of announcer rules; second set of announcers
The CSU is a particularly design-intensive product that requires a complete overhaul. Many of its settings are no longer meaningful, as ARES soft-codes all of the power subsystems, so these can be changed without the CSU.
We would ideally like to replace the CSU with a "cyberware inventory" experience called the <b>Hardware Components System</b>, where you must go to your local ripperdoc (Arachne X8) to change load-outs.
This is a generic server/client architecture for implementing multiple HUDs with a single attachment, a little like X Windows. For sanity and sanitation reasons we intend to implement HUDware first, then implement the HCS interface using HUDware.
implement stream-oriented API, adapt command-line pipes
In 2019 we demonstrated a somewhat-janky-and-laggy-but-viable pair of gadgets for remotely controlling other avatars' movements and camera using direct control input. Dive will package this as a telepresence add-on for use between NS units in the same region.
myNanite Uplink has been a long-standing dream project at NS, intended to provide a web-based interface for accessing and managing units remotely via a subscription service. Implementing it will require a new payments system, and (hopefully) allow integration via our upcoming Patreon.
Things That Are In Limbo
These are to-do items that need to be done but, for various reasons, are annoying and keep getting put off. Exactly when they'll actually get done is anyone's guess.
Sexuality
Sexuality is the ARES equivalent of Companion's TESI add-on. It provides arousal, cryolubricant management, tactile sensors, and more. Sexuality is part of the same purchase package as TESI Complete.
Outstanding Sexuality implementation tasks:
WARRIOR
WARRIOR is an enhanced combat add-on for ARES that adds features originally slated for ATOS/CX. We hope to deliver it around the same time as Beta 1 and Sexuality.
Outstanding WARRIOR implementation tasks:
Beta 1 Targets
Once ARES hits Beta, we will retire the Supervisor controller, and ARES will start to become available on standard hardware.
DIAG
DIAG (short for diagnostics) is a software add-on experience for ARES that simulates malware and logic malfunctions. Its main purpose is to encourage roleplay around repair and maintenance, including a special tech support crew staffed by NS volunteers who help rescue stranded units in the field.
We expect to focus on DIAG after the Beta 1 rollout is finished.
Outstanding DIAG implementation tasks:
Beta 2 Targets
Cleanup:
HCS: The new CSU
The CSU is a particularly design-intensive product that requires a complete overhaul. Many of its settings are no longer meaningful, as ARES soft-codes all of the power subsystems, so these can be changed without the CSU.
We would ideally like to replace the CSU with a "cyberware inventory" experience called the <b>Hardware Components System</b>, where you must go to your local ripperdoc (Arachne X8) to change load-outs.
HUDware
This is a generic server/client architecture for implementing multiple HUDs with a single attachment, a little like X Windows. For sanity and sanitation reasons we intend to implement HUDware first, then implement the HCS interface using HUDware.
Beta 3 and Beyond
Dive
In 2019 we demonstrated a somewhat-janky-and-laggy-but-viable pair of gadgets for remotely controlling other avatars' movements and camera using direct control input. Dive will package this as a telepresence add-on for use between NS units in the same region.
Uplink
myNanite Uplink has been a long-standing dream project at NS, intended to provide a web-based interface for accessing and managing units remotely via a subscription service. Implementing it will require a new payments system, and (hopefully) allow integration via our upcoming Patreon.
This is the page roadmap as it appeared at 2023-12-27 17:58:49.
You can view other old versions at the
history page.
Alternatively, you may want to settle for the current version.
Alternatively, you may want to settle for the current version.