The majority of
ARES is implemented. This is what remains to be done. Each bullet point represents an estimated 1 work day. 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.
damage folder loading [effector]; document which power rules have hardcoded dependencies [system.info]
@security command; apparel and curfew policies; consent UI; guest expiry [security]
@beacon May 27 2023
menu pagination; menu refresh fixes [menu]
power profiles [power], volume & scheme controls [id]; all remaining menus should at least activate stubs [fs + menu + power]
minimal external menu HUD (AMlite)
ARES-to-ARES menu invites & sharing [interface + variatype]
shakedown of all security rules
revisit streams [io, filter, input]
finish vox control program; get input filter system working fully; vox permission [vox]
_input fully implements power notify restriction [input]; shakedown of all announce messages [various]
leashing & follow [nav]; @tp [nav]; lock & autolock [security + menu + baseband]; bolts [device, effector]; command for drainprotect [power]; command for bolts [security]; prevent movement while charging [status + effector]
animation hoverheight [effector], battery auto-positioning [ctrl, device]; !broken [effector, ctrl]; zap [power]
@beacon June 10 2023
finish parametric interference [effector + input]
pkg; package server; args for @do [input]
proc watchdog [fs]; leftover filters; generic web fetch backend [fs]
ports [ctrl + device]; gracefully retry probe for battery [device]
finish unnamed ARES-exclusive main controller
remaining time for bug fixes, documentation, overflow, and polish
@beacon June 24 2023 (release Alpha 1)
db backup, toggle [db]
auto-unstick [proc]; forget deleted script [kernel]; timer events [kernel]; daemon info [proc]
standard external menu HUD (AMenu)
replacement for remote console HUD (ARemote)
distress beacon [power], IM policies [security], owner radio policies and exceptions [security]
5 workdays of extra time for bug fixes and polish
@beacon July 8 2023 (release Alpha 2)
finish nav
new nav server
RLV relay [restraint]
begin updating old devices for ARES compatibility
July 14–19: extra time for bug fixes, polish, and working on releases for Mainframe
start of Mainframe shopping event July 20, 2023
sexuality (TESI for ARES); estimated 5 working days
@beacon July 22, 2023 (release Alpha 3 and sexuality (TESI for ARES))
Spring Utilities replacement with new rental, proximity, and cron facilities
database overlays [db]; Hierarchy/XNMS compatibility [domain, db]—no server code changes anticipated
ARES WARRIOR add-on with malfunctions (estimated 4 working days)
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
@beacon August 5, 2023 (release Beta 1 and WARRIOR)
Plans after the first ARES Beta are less definite in terms of the amount of time required and the order of expected developments.
undefined amounts of time for copious bug fixes and polish; update remaining devices (those that previously depended upon the Companion "internal" message); update remaining controllers
dive (3 workdays)—ability to move units with direct key input with camera etc.
@beacon August 19, 2023 (release Beta 2 and dive)
undefined amounts of time for copious bug fixes and polish
HUDware (??? workdays)
new CSU system (??? workdays)—the CSU is a particularly design-intensive product that requires a complete overhaul as many of its settings are no longer meaningful; we would like to replace it with a "cyberware inventory" experience, where you must go to your local ripperdoc (Arachne X8) to change load-outs
@beacon September 2, 2023 (release Beta 3?, HUDware?, CSU2?)
uplink (??? workdays)—ability to control units from web; will require new payments system and Patreon integration
This is the page roadmap as it appeared at 2023-05-26 04:11:29.
You can view other old versions at the
history page.
Alternatively, you may want to settle for
the current version.