Ask Nixie 1.0.5 — base plugin
This package contains AskNixie-1.0.5.jar, the regular Minecraft edition. The main class is com.evergrims.nixie.NixiePlugin. It requires a separately operated, compatible Nixie bot/bridge service. No Broadcast edition, broadcaster payload, Discord bot, account cache or deployment secret is included.
Install or update
- Stop the Paper server and preserve
plugins/AskNixie, including its configuration and state. - Remove the previous Ask Nixie JAR and place
AskNixie-1.0.5.jarinplugins. Install only one edition. For legacy NixieMinecraft installations, move the existing data folder toplugins/AskNixiewith its state intact. - On a new installation, let the plugin create its configuration. Set
bridge-urlto the running Nixie service's HTTPS endpoint andserver-secretto the separate secret assigned by its operator. This is not a Discord bot token or model-provider API key. - Enable the plugin after configuration and fully restart. Existing installations should preserve their settings.
The default configuration keeps the plugin and Server Watch disabled until configured. The service operator must update their bot for the 1.0.3 ranked-watch features; that bot is outside this download.
Server Watch
Enable server-watch.enabled only for the intended connected server. The watcher monitors accepted plugin identities and sends queued diagnostic evidence through the existing bridge. The owner-managed project registry syncs about every 60 seconds; /nixie watch sync requests an early refresh and requires nixie.watch.sync.
The two updated gameplay plugins use these exact identities:
| Plugin | Version | Main class |
|---|---|---|
| GrimsSuperSpawners | 0.1.5 | com.evergrims.SuperSpawners.GrimsSuperSpawnersPlugin |
| GrimsRedstoneWifi | 0.2.1 | com.evergrims.grimsredstonewifi.GrimsRedstoneWifiPlugin |
The service owner adds missing identities with /project add, or updates existing ones with /project edit. Retain previous main classes when older installed builds should remain recognized. Confirm the registry with /project status.
Both plugins log [EGW-WATCH] records with rank, severity, operation code and version. Ranks are 1 NOTICE, 2 WARNING, 3 ERROR and 4 CRITICAL. Original exception causes remain available. Default bot alert switches enable ranks 3–4 and disable 1–2. The owner can inspect /serverwatch ranks and change each switch with /serverwatch rank rank:<1-4> enabled:<True|False>.
Verify delivery
Run /nixie watch test [1-4] as an operator or with nixie.watch.test; the default rank is 3. The test is limited to once per server per minute and reports confirmed Discord posting, a filtered rank, or unconfirmed delivery. Test messages do not ping or call the model.
Local parser checks do not prove live delivery. The bridge, destination, identity registry, enabled ranks, queue limits and network availability still apply. Check the original server log when investigating an incident.