Skip to content

Web Interface

Acelith edited this page Nov 1, 2026 · 2 revisions

Web interface

Open your server's address (for example https://sync.example.org/) in a browser and sign in with your Chronexus account. Notes are written in the desktop app; the web interface manages what lives on the server.

Campaigns have separate sections for server usage, members, invitations (owners) and deletion or leaving. Each section has a bookmarkable address. On wide screens, global navigation stays in a sidebar; on phones it appears above the content. Wide tables scroll horizontally and can be focused with the keyboard.

The source includes a separate Tables workspace: authorized GMs create tables, invite players or spectators and manage seats. Campaign membership and table seats remain separate. GMs see only journal items explicitly granted by their authors, including items beyond the first 100; the workspace loads the paginated list. The source now includes M44 map/grid/token editing, movement, rulers, area templates and the labelled ft/m converter. M45 adds initiative, turn/round controls, conditions, owner-only confirmed HP changes and a filtered combat log. Desktop table integration remains pending.

The live channel shows public activity and presence. After a connection interruption, it checks whether a pending message was already saved before retrying the same operation. Conflicts keep the draft for an explicit retry, and confirmations preserve newer text typed while waiting. These table features are source changes; published server release 0.1.1 predates them.

What you can do

Who Can
Everyone See their campaigns and role, what they keep on the server (items per kind, highest revision, last accepted save, images) and the server's limits; sign out devices
Owner Switch members between player and reader, remove members, create and revoke invitations, delete the campaign on the server (typing its exact name)
Player, reader Leave a campaign
Operator See service status (version, schema, database size, counts) and account metadata (sessions, campaign count, stored bytes)

Every destructive action first explains what happens to local copies, offline devices and existing backups, and asks for confirmation.

The page shows what the server holds. It cannot know changes a device has not sent yet: check the status in the desktop app for that.

Operators

Whoever controls the server's .env decides the operators:

CHRONEXUS_OPERATORS=your-user-name,another-user

The operator role gives no access to campaign content in the interface or the API: no campaign names, members or items. (Whoever controls the host can still read the database file; that is outside the application.)

Security

  • Static pages served by the server with a strict Content Security Policy: only its own scripts and styles, no framing, no third-party content.
  • Same JSON API and permission checks as the desktop. The session token stays in the browser tab and ends when you sign out or close the tab. No cookies, so no cross-site request forgery; requests from another origin are refused.
  • Names and other text from campaigns are always shown as plain text.

The interface supports English and the nine other desktop languages, including right-to-left Arabic. Campaign text remains unchanged.

Combat in the current source

Select combatants, prepare combat, enter/roll initiative and use the order controls for ties, then begin the first turn. Only the GM advances/delays turns or manages the roster. Players move their own token on its turn. Select a token on the map or in its list to load/edit its values. Only the owner changes HP/AC or rolls for it; the GM changes its own monsters. HP stays private unless its owner chooses to show it. A public status such as “bloodied” is manual, never inferred.

HP changes require confirmation. Rolls do not apply damage or change a character sheet. Condition durations reaching zero remain visible with a review reminder; remove them explicitly when appropriate. Spectators have no mutation controls. Hidden tokens/turns, GM notes, secret rolls and private HP logs never arrive in other players' views. Maps, combat and journals remain separate spaces.

Fog, monsters and image library (M46–M47)

The current server/web source adds manual fog, per-player restricted vision with walls/doors/lights, editable SRD/custom monsters and saved encounter placement. The GM sidebar also has an image library: import PNG/JPEG/WebP from the computer, search Wikimedia Commons explicitly, retain attribution, and place images on the grid or use them for monster portraits. Downloads of fogged backgrounds are redacted by the server; players do not receive the full map behind an overlay.

Fog currently uses a coarse 32 × 32 visibility mask. Source delivery does not claim desktop integration, production hosting or three-platform acceptance. See Table tools for operation instructions and limits.

Table workspace layout

A table opens as one workspace: tools on the left, the map in the middle and a tabbed sidebar on the right (Chat, Tokens, Combat, Measure; the GM also has Scenes, Fog, Library and Players). Zoom with the mouse wheel or the + and − buttons, pan with the middle or right button, Space+drag or the pan tool, and use Fit map to view or full screen. On narrow windows the sidebar moves below the map.

Chat, dice and pings

The server rolls every die. Type /r 1d20+5 Attack, /r 2d20kh1 (advantage), /r 2d20kl1 (disadvantage) or use the quick-roll buttons. /gr 1d6 and the Only the GM sees my rolls option send a secret roll; /w gm text whispers to the GM. Secret lines are visible only to their author and the GM. A roll changes no token, sheet or journal. Pick the ping tool, Alt+click, or press P on the map to show everyone a point on the active scene for a few seconds; pings are not saved.

Clone this wiki locally