Skip to main content

Open Larpinq for the first time

A first look at Larpinq — where the app lives, what the navigation gives you, and how to tell it is wired up to OpenRegister so character data, skills, items, and events can load.

Goal

By the end you will have opened the Larpinq app, recognised the dashboard and the left-hand navigation, and confirmed that the OpenRegister-backed lists (Characters, Skills, Items, Events, …) load.

Prerequisites

  • A Nextcloud account on an instance where the Larpinq app is installed and enabled.
  • The OpenRegister app installed and enabled — Larpinq stores characters, skills, items, conditions, effects and events in OpenRegister, so it is a hard dependency.
  • The Larpinq register and its 10 schemas imported. An admin runs this once from Settings → Administration → Larpinq, picking the data source per entity (see Manage Larpinq settings).

Steps

  1. Open the Nextcloud app menu in the top bar and pick Larpinq. You land on the dashboard.

    Larpinq dashboard

  2. Read the dashboard KPI cards — Characters, Events, Items, Players. On a fresh install they read 0; they fill in as the game master and players populate the setting. Below the cards are Recent characters, Recent events, and a Skill usage donut chart.

    Dashboard KPI cards

  3. Open the left-hand navigation. The entries map one-to-one onto the things Larpinq tracks: Characters, Players, Items, Conditions, Events. Below the divider sit the rule-engine entries — Abilities, Skills, Effects — and finally Game settings.

    Larpinq navigation

  4. Click Characters. The list view opens with a Cards / Table toggle, an Add Item button, and a search sidebar. An empty install shows No items found — expected until someone creates the first character.

    Characters list, empty state

Verification

You are set up correctly when: the Larpinq dashboard renders without an error banner, the left navigation lists the entries above, and clicking through to Characters (or any other list) shows either rows or a clean No items found state — not a load error.

Common issues

SymptomFix
"OpenRegister is not installed or enabled" bannerInstall and enable the OpenRegister app, then reload Larpinq.
Lists load but Add Item opens a modal with no form fieldsThe Larpinq register import is incomplete — an admin re-runs the register configuration from Settings → Administration → Larpinq.
Larpinq is missing from the app menuThe app is not enabled for your account — ask an administrator to enable it (and check it is not restricted to a group you are not in).
Screenshots may be missingApp not yet installed in the test environment; rerun npm run test:e2e:docs once it is.

Reference