There is no Active Spells window.

[SaragosDR]

There does not appear to be a way to open an Active Spells window in Genie 5. Additionally, in Genie 4 the variables from that window are exposed via the Spell Timer plugin, which does not function in Genie 5. Is the plan to try to write a new plugin for this, or to roll that functionality into the base client?

[SaragosDR]

These are the variables the system exposes for each spell:

$SpellTimer.Substratum.active=1
$SpellTimer.Substratum.duration=7

[monil2233]

Great question — and the good news is the plumbing for this already exists.

Genie 5's plugin system can do both halves of what the Genie 4 Spell Timer gave you: render to a dedicated dock window and publish $variable globals back to .cmd scripts. The cleanest way to see how is the reference plugin we just published, EXPTrackerV5:

👉 https://github.com/GenieClient/Plugin_EXPTrackerV5

It's a port of VTCifer's Genie 4 EXPTracker, and it does the same two things a Spell Timer plugin needs:

1. Reads a live stream (<component id='exp …'> pushes) + parses the verb's full-dump text.
2. Writes a named window via the host API (SetWindow("Experience", …)) — the host surfaces it as a dock panel (Window → Experience).
3. Publishes script globals — $<Skill>.Ranks, $<Skill>.LearningRate, etc. — the same surface the Genie 4 plugin exposed. This is the exact mechanism your $SpellTimer.Substratum.active=1 / .duration=7 variables would use.

To try the plugin pattern today:

1. Build it: dotnet build -c Release → bin/Release/net8.0/Plugin_EXPTrackerV5.dll
2. Open your plugins folder with Plugins → Open Plugins Folder. That menu item always opens the correct folder for your install — so you don't have to hunt for it, and it works whether you're on a standard install or running Genie 5 portable (where the data folder sits next to the app instead of under your user profile). For reference, the standard locations are:
   • Windows: %APPDATA%\Genie5\Plugins\
   • macOS: ~/Library/Application Support/Genie5/Plugins/
   • Linux: ~/.local/share/Genie5/Plugins/
3. Drop Plugin_EXPTrackerV5.dll into that folder.
4. Load it — Plugins → Load → Plugin_EXPTrackerV5.dll (loads an individual .dll sitting in the Plugins folder that isn't loaded yet), or reconnect, or #plugin load Plugin_EXPTrackerV5. If you've just rebuilt over an existing copy, Plugins → Reload Plugins picks up the new DLL.
5. Open Window → Experience and type exp in-game to populate it.

You can manage it the same way any plugin is managed — Plugins → Enable / Disable to toggle it without unloading, or Plugins → Unload to release the DLL.

On the actual Active Spells / Spell Timer question: the plan is a plugin (not base-client), built the same way as EXPTrackerV5 — read the active-spells stream, render to an Active Spells dock window, and republish $SpellTimer.<Spell>.active / .duration for script compat. EXPTrackerV5 is meant to be the template for exactly this kind of port. If you (or anyone watching this issue) want to take a run at it, that repo is the place to start.

[monil2233]

Cross-link: the spell-timer scripting variables requested in #45 ($casttimeremaining, $spelltime, $spellpreptime, $spellstarttime) belong to this plugin path too. As noted above, the plumbing to expose $variables back to scripts already exists (EXPTrackerV5 precedent), so a Spell Timer plugin can deliver both the Active Spells window and those globals — testable independent of the base client.

[monil2233]

Good news — this works today via the Genie 5 spell-timer plugin:

👉 Plugin_SpellTimerV5 — https://github.com/GenieClient/Plugin_SpellTimerV5

It's the Genie 5-compatible port of the Genie 3/4 Spell Timer, built on the same plugin model as the reference EXPTracker plugin. It renders the Active Spells window and publishes the $SpellTimer.<spell>.active / .duration globals back to .cmd scripts (the variables noted above and cross-referenced in #45). So no base-client work is needed for this — install the plugin and the window + variables come with it.

Tagging as question: if you're already running it and the window/variables aren't populating, let us know the plugin version and we'll dig in.