SubLim3Nexus

Wiki & FAQ

Everything you need to operate, customize, and recover Nexus.

This single-page reference covers first setup through advanced diagnostics. Use the bookmarks or search for a question and jump directly to the answer.

Overview

What is SubLim3 Nexus?

SubLim3 Nexus is a local-first tabletop RPG companion platform. Nexus Core hosts the table interface, campaign data, audio, RFID actions, player views, and connected devices. It can run on its own Local Mode network or join a home or venue router.

The basic rule: every phone, tablet, computer, and Player device must be able to reach the same Nexus Core.

Main areas

  • Owner Console: campaigns, characters, access, and administration.
  • GM Console: scenes, notes, encounters, initiative, damage, healing, and turn flow.
  • Media Player and Library: music, ambience, sound effects, streams, uploads, USB media, and packs.
  • RFID Cards: bind physical cards to audio or control actions.
  • Settings: networking, speakers, apps, backups, updates, power, and hidden advanced tools.

Getting started

First-time setup

  1. Install the Owner/GM and Player apps while internet access is available.
  2. Power on Nexus Core and wait for it to finish booting.
  3. For Local Mode, join SubLim3-Nexus and open http://10.10.10.1:3000.
  4. Pair the Owner device with the Owner PIN. Reserve the Recovery PIN for regaining Owner access.
  5. Create a campaign, choose a game system, and add or import characters.
  6. Open the GM Console and show players the campaign Player QR.
  7. Create a campaign backup before major changes or the first live session.

Access

Owners, GMs, and players

Owner / GM

The owner pairs with an Owner PIN and can manage the system. If that pairing expires, reconnect with the Recovery PIN. Keep both PINs private.

Players

Players join the same network, scan the Player QR, and select or create a character when allowed. They do not need an Owner, GM, or Recovery PIN.

Before Local Mode: install mobile apps while the phone still has internet. A phone connected only to the Nexus local network may not be able to reach an app store.

Hidden toolbox

What each hidden tool does

Update Diagnostic

Checks the Nexus update path and returns details useful when Update cannot download or install a release. Run this before exporting logs for an update problem.

Bluetooth Reset

Resets the Bluetooth subsystem when scans, pairing, or reconnection stop working. Put the speaker back in pairing mode afterward.

Wi-Fi Repair

Repairs Nexus Wi-Fi configuration. Use it for a broken network state?not as the normal way to switch between Local and Home Mode.

Export Logs

Downloads a text log for troubleshooting. Exported logs redact PINs, passwords, and keys, but review the file before sharing it publicly.

RFID Diagnostic

Checks RFID service and reader status when cards are not detected or actions do not fire.

Run Ping

Tests reachability from Nexus Core to a router, LAN address, or internet host. A successful phone connection does not prove that Core itself has upstream access.

Playback Defaults

Sets maximum volume, startup volume, volume-step size, and an optional timer that stops long-running playback.

RFID Card Behavior

Choose swipe or presence mode, decide what a second scan does, set repeat-scan delay, and allow function cards to bypass that delay.

Advanced Backup Tools

Download/import campaign files, prepare and scan USB folders, create full Nexus backups, and restore full-system files or USB backups.

Connectivity

Local Mode and Home Mode

Local Mode

Nexus creates the SubLim3-Nexus Wi-Fi network. Join it and open http://10.10.10.1:3000. This is the dependable recovery path when a router is unavailable.

Home Mode

Nexus joins an existing router. Connect every table device to that same network and reopen http://sublim3-nexus.local:3000 or the Core address shown by the app.

If Home Wi-Fi fails

  1. Wait for Nexus to restore Local Mode.
  2. Rejoin SubLim3-Nexus.
  3. Open http://10.10.10.1:3000/settings/.
  4. Confirm the network name and password, scan again, and use Run Ping after reconnecting.

Table atmosphere

Audio, speakers, and RFID cards

Use Media Library to upload or organize ambience and effects. Use Media Player for active playback, then bind library items or control actions to cards in RFID Cards.

Bluetooth speaker checklist

  1. Put the speaker in pairing mode.
  2. Open Settings and scan.
  3. Select the speaker, then Pair or Connect.
  4. If a previously trusted speaker fails, Forget it and pair again.
  5. Use Bluetooth Reset only if normal scan/pair steps fail.

RFID behavior choices

Swipe starts playback when a card is scanned. Place plays while the card remains present. The second-scan action can toggle, restart, or do nothing. A repeat delay helps prevent accidental rapid triggers.

RFID macros

RFID macro examples

RFID table macro cards can set a scene, replace the current encounter, or add monsters to an active battle. Use these examples when assigning a card from the RFID Cards page.

Static monster group

[
  { "name": "Goblin", "initiative": 14, "health": 8 },
  { "name": "Goblin", "initiative": 12, "health": 8 },
  { "name": "Goblin Boss", "initiative": 16, "health": 18 }
]

Random Spider Ambush

{
  "name": "Spider Ambush",
  "count": 3,
  "template": {
    "name": "Spider",
    "initiative": { "min": 1, "max": 20 },
    "health": { "min": 10, "max": 15 }
  }
}

Choose Load monster group to replace the encounter, or Add monsters to battle to append combatants. The same macro card can also include a scene title and description.

Campaigns

Campaigns, characters, and game systems

Each campaign groups its system, characters, and live session state. Use Basic Custom RPG for a quick first table and Player Cube compatibility. Optional packs add deeper fields, resources, conditions, and actions for the Player App.

  • Create or switch campaigns from the Owner Console.
  • Use GM Console to publish scenes and run encounters.
  • Keep character names and ownership clear before showing the Player QR.
  • Back up before changing game systems, importing large content sets, or handing a Core to another owner.

Data protection

Backups and restore

Campaign backup

Creates a portable .nexus-campaign.json copy containing campaign metadata, characters, live session state, and required game-system metadata. Import creates a new campaign copy rather than overwriting the original.

Full Nexus backup

The hidden tools can back up campaigns, characters, sessions, systems, RFID bindings, audio-library metadata, player settings, and controller provisioning. Media file bytes are not currently bundled, and browser pairings are not restored.

Safe restore sequence

  1. Create a fresh backup of the current state.
  2. Confirm you selected a campaign file versus a full Nexus file.
  3. Keep the page open through the confirmation and restore.
  4. After a full restore, verify campaigns, RFID bindings, player settings, controllers, and media paths.
Restore replaces data: a full Nexus restore replaces current tabletop data and settings. Do not test it during a live session.

Customization

Expansion packs

Game Packs add rules, character templates, resources, conditions, and player actions. Audio Packs add reusable ambience and effects. Start with Basic Custom RPG, then add only the packs needed by the campaign.

Current game-pack families include D20 Fantasy, Narrative Adventure, Percentile Horror, Post-Apocalyptic Survival, Sci-Fi Dice Pool, Superhero Adventures, and Dungeons & Dragons 5e-style support. Review third-party publisher terms before commercial distribution.

Explore available expansion types

Maintenance

Updates, reboot, and shutdown

  • Update: downloads and installs the latest Nexus release, then restarts Core. Keep the page open and back up first.
  • Reboot: briefly interrupts the table and restarts Nexus Core.
  • Shut Down: safely stops the Pi. Physical access is required to turn it back on.
Do not pull power: use Shut Down and wait for the Pi to turn off before disconnecting power.

Troubleshooting

Fast recovery checklist

  1. Confirm Nexus Core is powered on and fully booted.
  2. Confirm every device is on the same network.
  3. In Local Mode, try http://10.10.10.1:3000.
  4. Refresh the app or browser and reconnect Owner access if it expired.
  5. Back up before repair or restore work.
  6. Unlock hidden tools and run the diagnostic that matches the failing subsystem.
  7. Export logs after reproducing the problem, then send them with a description of what happened.

Ideas under consideration

Future Development

These are ideas we would like to explore, but none are promised, scheduled, or guaranteed to ship. Priorities may change based on technical feasibility, privacy, cost, and community feedback.

Exploratory

Cloud-based account setup

Optional accounts could simplify onboarding, device ownership, profile recovery, and access across multiple Nexus Cores while preserving local-first play.

Exploratory

Campaign game schedule

Let the GM create upcoming game dates, session times, locations, and notes for each campaign.

Exploratory

Player attendance requests

Let the GM ask campaign players whether they can attend. Players could answer Yes or No and optionally include a reply message.

Suggested idea

Attendance dashboard

Summarize responses for the GM, highlight players who have not replied, and show whether enough of the group is available.

Suggested idea

Reminders and calendar export

Offer opt-in session reminders and calendar links while handling time zones clearly and avoiding unwanted notifications.

Exploratory

SRD rule books

Add searchable System Reference Document rule books as expansion content, giving GMs and players quick access to properly licensed rules for compatible game packs.

Suggested idea

Optional campaign portability

Use encrypted cloud backup or transfer tools to recover a campaign, move between trusted Nexus Cores, or prepare for a game away from the usual table.

Privacy first: accounts, messages, schedules, and attendance responses would require clear consent, secure storage, and controls for deleting personal data.

FAQ

Frequently asked questions

Does Nexus need internet during a game?

No for normal Local Mode play. Internet is useful for installing apps, downloading updates, external streams, and expansion content.

What address should I open?

In Local Mode use http://10.10.10.1:3000. In Home Mode use http://sublim3-nexus.local:3000 or the Core address shown by the app.

Why can?t I see the advanced tools?

You must be paired as Owner. In Settings, click or tap the Nexus Core heading five times within 2.5 seconds.

Do players need a PIN?

No. Players join through the Player QR. Owner and Recovery PINs are administrative credentials and should remain private.

Does a full backup include my audio files?

It includes audio-library metadata, but not the media file bytes yet. Keep a separate copy of important media.

Will importing a campaign overwrite the original?

No. A campaign backup imports as a new campaign copy. A full Nexus restore is different and replaces current tabletop data and settings.

What happens if no Bluetooth speaker is connected?

Nexus falls back to the Pi audio output when no trusted Bluetooth speaker is connected.

Which game system should I use with Player Cubes?

Use Basic Custom RPG. Advanced and optional expansion-pack systems are intended primarily for the Player App.

Community

Support and contributions

If this page does not answer the question, send a support request with the Nexus version, network mode, what you expected, what happened, and any exported diagnostic logs. Builders can also report issues and contribute improvements through GitHub.

Ask for support
Back to top