Skip to main content
Apps/Larpinq

Larpinq

Build worlds, run campaigns, for live-action role-playing. On your own Nextcloud. Yes, really.

Larpinq (formerly LarpingApp) is an open-source campaign manager for live-action role-play groups. You design the rules of your world once: abilities, skills, items, conditions and what they do to a character. Players keep their own sheet, and the sheet recalculates itself when they learn a skill or pick up an item. You approve backgrounds, hand out experience after every event with a reason, and print clean character sheets and a cast list before the weekend. Made by people who run games. Released under EUPL-1.2 and maintained by Conduction since 2019.
What it does

Characters, rules, events and players. One place, no six-tab spreadsheet.

Your rules live in the app, not in your head. Players edit their own character in the same Nextcloud you run the campaign from. You stop recalculating sheets and start running games.

A player learns a skill. Their sheet updates itself.

Today you recalculate twenty sheets the night before the event. Instead, a player adds the skill and every stat it touches changes on the spot. Every ability shows exactly which skill, item or condition added what, so an argument at the table is settled by looking. Illegal builds and overspent points are refused when the player saves. You can override, once, on purpose.

Award XP once, with a reason. Six months later nobody argues.

After the event you hand out experience per character, with why and when. The character levels up by itself. Six months later a player asks why they have fewer points than their friend, and the answer is on their sheet, entry by entry. No spreadsheet cell somebody once overwrote.

A player writes their background at home. You approve it before Saturday.

The player writes the story and submits it. You get a notification, read it when you have a minute and approve. The character walks in on Saturday with the right points and an approved background. No printed drafts, no last-minute email with an attachment.

Print the sheets and the cast list on Friday night.

Each player brings a clean PDF character sheet to the field. You bring one cast list per event with names, stats, conditions and notes. Both come straight from the records, so what is on paper is what is in the app. Printing needs the Filinq app installed next to it.

Your own rules, your own worlds.

Model your own game system: abilities, skills, items, conditions, effects, and what each does to a stat. Run more than one world from the same install and keep characters and events apart per campaign. A finished campaign is archived, not deleted, so old rosters stay readable. A first-run wizard sets everything up and shows you around.

Free for the small organiser.

No yearly licence per player. Install it on a Nextcloud you already have, or ask a partner to host it. Open source, so the rules you build stay yours.

Four ways Larpinq earns its place

It works the way you play. And it works for you.

Four things you would normally pay extra for. In Larpinq they are built in.

TriggerStepStepApprovalEnd
Automate

A background is submitted. The approval is already on your list.

Today: a player mails you a story, you forget, they ask on Saturday. Instead, set it up once. The moment a background is submitted, a task lands on the game master's desk. The moment it is approved, the player is told. After every event, a list of characters that got no XP yet. Nothing forgotten, no chasing, no coding.

How automation works
Make it yours

Your system, your fields, your sheet.

A fantasy group wants mana on every sheet. A post-apocalyptic group wants radiation and a faction. A vampire chronicle wants generation and clan. Add the field, hide the block your system does not use, drag the widget you check first to the top. In the running app, in minutes, and your changes stay with every update.

How customising works
Talk to it

Ask who is coming. Get the list, not a spreadsheet.

Ask "who signed up for the June event?" and you get the names. Ask "which characters have the healing skill?" and the list is there. The assistant reads the same characters and events you are allowed to see, and asks before it changes anything. Approving and awarding XP stay with you.

Meet the assistant
Let clients help themselves

A new player signs up without a seat in your Nextcloud.

Not every player needs an account on your server. Through Portaliq they get their own portal page: they see the coming events and sign up, follow whether their background is approved yet, and check their own character and XP before the weekend. You keep the game master side to yourself, and the "am I approved yet?" messages stop.

See the player portal
How Larpinq plugs into the workspace

Calendar, contacts and photos. Already yours.

No separate player portal. The campaign uses the calendar, the address book and the photo album your group already has in Nextcloud.

Give an event a start and end date and it is in the Nextcloud Calendar. Pin the location on the map from the event page. Players sign up through a form and you see who is attending on the roster, before you print the cast list. Nobody keeps a second list in a chat group.

Read the docs
Partners

Partners shipping Larpinq

Implementation, hosting, and integration partners that deliver Larpinq to their customers. Pick the partner you already work with, or one whose stack matches yours.