Submit a session report¶

Nerthus.Core (until cutover). This page describes the frozen system that runs today and is deleted at cutover. Replaced by: not yet written.

A session report files a game no Narrator recorded — one you ran yourself — straight from Discord. Your submission becomes a merge request the Rada reviews, and the tool renders the Markdown for you, so you never write raw @-tags. Self-service: the same two commands serve a player filing their own session and a Narrator filing one on the side.

A report is a draft. It lands in zgłoszenia/ and is not distributed, closed, or awarded PU by the act of reporting. The Rada reviews and merges the request; a Narrator then enacts the merged draft into the live lore. Nothing you submit takes effect until then.

Before you start¶

Report from a Discord server where the commands are enabled — access is set per server, so if you cannot see /zgłoś, ask a Radny to grant it. Your submission is tagged with your Discord identity so the Rada knows who filed it; if your Discord is not yet linked to your player identity, a Radny matches it while reviewing (Start here).

Somebody wired these commands up once, long before you got here. You need none of that to file a report - the two commands are the whole of your side.

Two ways to report¶

/zgłoś — the guided form (lenient)¶

Type /zgłoś in the server. Discord opens a modal with five fields:

This path is lenient: the daemon recovers common fumbles — an unpadded date, a PU entry without its colon, several PU pairs run together — and the warnings ride along into the merge request for the Rada to see. When in doubt, use /zgłoś.

"Zgłoś sesję" — from an existing message (strict)¶

Already wrote the report as a message? Right-click it → Apps → Zgłoś sesję. This reads the message raw and strict: a properly formatted report passes untouched; anything that would need recovery is rejected with the exact fixes, posted back only to you (ephemeral).

Wrap the report in a triple-backtick ``` block. Discord mangles Markdown in normal messages; the code fence delivers it byte-for-byte.

What happens next¶

1. The command replies immediately with a "working…" state, then edits it to a confirmation, or a Błąd: line with what went wrong. A reply ending in ⚡ was answered by the live tool; one without it went the slower route. Both mean the same thing for you.
2. On success a merge request opens, titled Zgłoszenie sesji: <nagłówek>, labeled zgłoszenie/discord/<tryb> for Rada triage.
3. The Rada reviews and merges it. After merge, a Narrator enacts the draft through the normal open/close workflow — that is when distribution, transfers, and PU actually happen. Until then, wait: zgłoszenie przyjęte, czeka na Radę.

Three commands that just answer¶

These read and never change anything, so they reply in seconds:

They are served only by the live tool. When it sleeps you get Demon niedostępny - spróbuj ponownie za chwilę, and /zgłoś still works — reporting has a slower fallback route, these do not.