nexSys4

A character-management and curing-automation system for the text MUD Achaea, running inside the Nexus web client.

nexSys4 ingests GMCP, text triggers, and prompt boundaries to maintain authoritative state for your character — afflictions, balances, defences, limbs, cache, and queues — and drives two coordinated outbound lanes: prompt-bound curing/defence output and a separate queue control plane. Behavior is deterministic, server-side curing is reconciled diff-only, and a built-in configuration UI exposes priorities and settings.

Installation

npm install nexsys4

The package ships prebuilt distributables only:

• dist/nexSys4.nxs — a Nexus package file. Import it into the Nexus client to run nexSys4 in-game.
• dist/nexsys4.min.js — the prebuilt runtime bundle. Importing it exposes globalThis.nexSys.bootstrapNexus; the runtime does not start until that function is called.

Usage

Import the bundle, enable the nexSys4 package groups, and explicitly bootstrap the runtime:

import("https://unpkg.com/nexsys4/dist/nexsys4.min.js").then(() => {
  nexusclient
    .packages()
    .get("nexSys4")
    .items.filter((item) => item.type === "group")
    .forEach((group) => {
      group.enabled = true;
    });

  nexSys.bootstrapNexus();
});

After bootstrapNexus() runs, the global nexSys module namespace is replaced by the live runtime object.

// Open the configuration UI (priorities, settings, precache, colors)
nexSys.ui.openConfig();

The nexSys global exposes a namespace-first runtime API:

| Namespace | Purpose | | ---------- | --------------------------------------------------- | | state | Read current system / character state | | affs | Affliction presence and timing | | defs | Defence presence and timing | | balances | Balance presence and timing | | limbs | Limb state | | queue | Queue control plane | | ss | Server-side curing: predictions, queue, curing sets | | rules | Rule lifecycle | | control | Runtime control (pause, etc.) | | prompt | Prompt-bound output | | events | Subscribe to runtime events (on / off) | | ui | Open / close the configuration UI |

Requirements

nexSys4 is designed to run inside the Nexus client for Achaea, alongside the standard Nexus runtime globals (eventStream, GMCP).

License

Proprietary — all rights reserved. See package.json for the current license declaration.