Skip to content

Players and characters

The roster is the record of who plays Nerthus. It has two halves: the people and the characters they play. This page shows you both blocks, explains what the tool reads in each, and walks you through registering a new player and adding a character to one.

The person and the character

Two blocks describe every player. The person:

### Eraster
- @typ: Gracz
- @margonemid: 9826541
- @status: Aktywny

The character they play:

### Eraster
- @typ: Postać
- @należy_do: Eraster
- @status: Aktywny
- @plik: /Postaci/Gracze/Eraster.md

A Gracz is the real person behind the game account. A Postać is an in-fiction character that person owns and plays. One player usually owns several characters, and exactly one of them is active at a time. The player Eraster owns four: Eraster, Losso Minewit, Felkissian, and Klusp.

Both blocks are headed ### Eraster, and they are still two different entities. The heading is a display label for people to read. @typ is what tells the two apart.

PU belongs to the character and not to the person: all four PU fields sit on the Postać block, and a player who owns several characters keeps a separate PU account on each - see Grant PU.

The roster lives in the index, nerthus.entities.md, in two sections. ## Gracze holds the players. ## Postacie Graczy holds their characters.

The Gracz block

A player's block, with everything it can carry:

## Gracze

### Eraster
- @typ: Gracz
- @margonemid: 9826541
- @status: Aktywny
- @prfwebhook: https://discord.com/api/webhooks/1211971813370892408/-7i1JynZrz…
- @tematy_zastrzeżone: Banany
  • @typ: Gracz marks the block as a person.
  • @margonemid is the player's Margonem profile id, and their real identity.
  • @status is Aktywny while the player is with the campaign, Nieaktywny when they have stepped away.
  • @prfwebhook is the player's personal Discord channel - where the tool sends their notifications. It has its own section below.
  • @tematy_zastrzeżone lists subjects the player does not want in their sessions. It has its own section below.

@margonemid is the anchor of the whole block. Nicks change over the years; the Margonem profile id never does. Every sign-in and every permission points at that number rather than at the heading above it - see Start here.

A nick change moves only the heading

When a player changes their Margonem nick, change the block heading to match and leave @margonemid exactly as it is. The heading is a label. The id is the identity.

A Gracz block carries no @plik. Sessions are copied into character files, never into a player's, so a player has no file of their own to point at.

@tematy_zastrzeżone - subjects to keep out

- @tematy_zastrzeżone: Banany

@tematy_zastrzeżone is the player's trigger list: subjects they do not want appearing in sessions they take part in. Here the player Eraster has one, Banany.

A Narrator reads the list before running a session for that player, and plans around what is on it. The list sits on the Gracz block, so it covers every character that player owns - you do not repeat it per character.

It is one line. If a player names several subjects, write them all on that single line, separated by commas. The tool keeps the value exactly as you write it and shows it to the Narrator, so write it for a person to read.

@prfwebhook - where the tool reaches the player

- @prfwebhook: https://discord.com/api/webhooks/1211971813370892408/-7i1JynZrz…

@prfwebhook is the player's personal Discord webhook: the private channel the tool posts their notifications to. Two kinds of message go there, and both are for the person, so one webhook covers every character they own:

  • the monthly PU their characters are awarded - see Grant PU,
  • the session Intel aimed at them or at one of their characters - see Record a session.

Copy the webhook URL out of the Discord channel's settings and write it on one line. A player who has none gets BRAK in its place:

- @prfwebhook: BRAK

Nothing else depends on it. A player with no webhook - or BRAK - still earns PU and still takes full part in sessions; the tool just has nowhere to send their copy, records the skip, and carries on. Delivery is best-effort: a webhook that is down loses that one message, never the award or the intel behind it.

The Postać block

A character's block, with the PU tags included:

## Postacie Graczy

### Eraster
- @typ: Postać
- @należy_do: Eraster
- @status: Aktywny
- @plik: /Postaci/Gracze/Eraster.md
- @pu_startowe: 20
- @pu_suma: 127.90
- @pu_zdobyte: 107.90
- @pu_nadmiar: 0.00
  • @typ: Postać marks the block as a character.
  • @należy_do names the Gracz who owns this character. This is the line that links the character to the person, and every character has exactly one.
  • @status is Aktywny on the one active character and Nieaktywny on the others.
  • @plik points at the character's own file under Postaci/Gracze/. Sessions this character took part in are copied into that file, so the path has to be right.
  • The four @pu_* tags are this character's PU account, and they split two ways. You write @pu_startowe yourself, once, when you create the character - it is the only one you ever touch. The tool maintains @pu_suma, @pu_zdobyte, and @pu_nadmiar from then on. Grant PU explains what each one means.

One character is active

Each player has exactly one active character. When a player switches, make both edits together: set the new character to @status: Aktywny and the previous one to @status: Nieaktywny.

The active character matters beyond the roster. A player's own notes are filed against it - see Set up the repository.

The roster sections are yours

## Gracze and ## Postacie Graczy are written once, when the repository is first set up. After that the tool never regenerates them. Edit them by hand as much as you like: add a player, correct a nick, fix an owner, retire a character. Re-running the import carries both sections over untouched.

This is why the two procedures below are just "write the block". There is no command to run afterwards and no generated copy to keep in sync.

Register a new player

  1. Get the player's Margonem profile id. Open their Margonem profile and read the number out of the address, https://www.margonem.pl/profile/view,9826541 - the id here is 9826541. Ask them for the profile link if you do not have it.
  2. Open the index, nerthus.entities.md, and find the ## Gracze section.

  3. Add the block, in the same shape as every block around it - a ### heading with the player's current nick, then one @tag line per fact:

    ### Eraster
- @typ: Gracz
- @margonemid: 9826541
- @status: Aktywny

    @typ, @margonemid, and @status are the minimum. Add @tematy_zastrzeżone if the player has named any subjects to keep out.

  4. Give them a character. A player with no Postać has nothing to play - the next section.

No id, no sign-in

A Gracz without @margonemid is a roster entry and nothing more. That player cannot sign in, because there is no id to match them to. Add the tag when you create the block rather than later.

Add a character to a player

  1. Open the ## Postacie Graczy section of the index.

  2. Add the block. @należy_do carries the owning player's nick, and @plik points at the file you are about to create:

    ### Felkissian
- @typ: Postać
- @należy_do: Eraster
- @status: Nieaktywny
- @plik: /Postaci/Gracze/Felkissian.md
- @pu_startowe: 41

  3. Set the status deliberately. Eraster is already this player's active character, so Felkissian joins as Nieaktywny. If the new character is the one being played from now on, mark it Aktywny and demote the previous one in the same edit.

  4. Create the character's file at the @plik path you wrote. It is a hand-authored Polish file, and the tool never rewrites your prose in it - it only copies sessions in.
  5. Write the starting PU. A veteran's second character does not start from zero. Its @pu_startowe is seeded from what that player's other characters have already earned - see Grant PU for the figure and how to preview it.

A character can also answer to short forms and old nicks through @alias, which Entities covers.

Retire a player or a character

Retiring is the same gesture as for anything else in the world: set @status: Usunięty on the block. Nothing is deleted, and Entities has the details.

Gracze.md

Gracze.md was the original hand-written player database, and the roster was built from it once, when the repository was first set up. It is a frozen archive now. Never edit it - the ## Gracze and ## Postacie Graczy sections of the index are the roster of record, and Set up the repository explains what happened to the file.

  • Grant PU - the PU fields on a character, and the monthly award
  • Entities - the block shape, @alias, and retiring a record
  • Start here - signing in with a Margonem id, and what each role may do
  • Set up the repository - the one-time import that built the roster