Grant PU¶
PU (Punkty Umiejętności) are skill points. A character earns them by taking part in
sessions. You grant them by writing a - PU: block under the session header, and a
monthly award does the accounting. This page shows how to write the block, how the
tool tracks a character's points, what the monthly award does, and how to recover
when a name does not match.
Write the - PU: block¶
Under the session header, list each participant who earned points and how many:
- One line per participant, in the form
Name: amount. - Grants are small decimals. Write them with a comma (
0,2) or a dot (0.2). The tool reads both. - How much a session is worth is the Narrator's call. There is no table to consult.
The session needs a valid unique header before any of this counts - see Record a session.
PU belongs to the character, not the player¶
Every name under - PU: is matched to a character (Postać). All four PU fields
live on that character's block. A player who owns three characters has three
separate PU accounts, and points one character earns never raise a sibling's total.
Almost everything about PU is per character: all four fields live on the character's own
block, the monthly award and its cap are worked out per character, and one character's
NADMIAR reserve is never spent on a sibling.
Two things - and only two - look across all of a player's characters at once:
- Election eligibility. The voting roll sums PU over every character that player owns.
- A new character's starting PU. Its
STARTOWEis seeded from what that player's other characters have already earned.
Both are covered further down this page.
The four PU fields¶
The tool keeps four figures on each character. On the character's Postać block they
are written as the @pu_* tags - those are what you see on disk, and the uppercase
names are what this page calls them in prose:
| Field | On the block | Meaning |
|---|---|---|
STARTOWE |
@pu_startowe |
the points the character started with |
SUMA |
@pu_suma |
the running total right now |
ZDOBYTE |
@pu_zdobyte |
points earned through play (SUMA - STARTOWE) |
NADMIAR |
@pu_nadmiar |
an overflow reserve, saved when a month goes over the cap |
A character who has played nothing reads STARTOWE: 20, SUMA: 20 - twenty to start,
zero earned.
Starting PU for a new character¶
A veteran's second character should not start from zero. When a player creates a new
character, its STARTOWE is seeded from the points that player's other
characters have already earned - half of them, plus a bonus, with a floor of 20.
That floor is why so many characters read STARTOWE: 20. It is the baseline for a
player with no earned PU yet. The divisor, the bonus, and the floor are Council
settings.
You do not have to work the figure out by hand. The tool will report the STARTOWE a
new character of a given player would be seeded with, before you write the block - ask
for the preview, then write the number it gives you.
The monthly award¶
Session grants do not change SUMA on their own. They wait. Once a month, the award
gathers up that month's grants and applies them:
- Each character named that month receives a small base plus their grants, up to a monthly cap.
- Anything over the cap banks into that character's
NADMIARreserve. NADMIARis drawn on in leaner months, so a busy month is never wasted.
The base and the cap are Council settings.
Take July 2026, with the session above as the month's only new one. Lord Tussal
has overflow banked from earlier months, so his 0.2 grant plus the base plus that
reserve lets him draw the full monthly cap, and the leftover carries forward.
Eraster has nothing banked, so his 0.2 plus the base adds 1.2 to his SUMA.
Every session is counted exactly once. Running a month again after new sessions arrive counts only the new ones - the sessions already awarded are skipped.
The monthly award normally runs as part of the scheduled settlement, which you do not have to trigger by hand - see The monthly settlement.
The player hears about it¶
When the award runs, each player gets one Discord message on their personal channel, summing up what their characters drew that month:
Postać "Lord Tussal" (Gracz "Tussal") otrzymuje 5,00 PU.
Aktualna suma PU tej Postaci: 89,10, PU nadmiarowe: 0,60
One message covers all of that player's characters. The PU nadmiarowe line shows only
when the character had overflow in play - banked before the month or left over after it.
The message travels through the @prfwebhook on the
player's Gracz block: a player who has none is still awarded but hears nothing, and a
webhook that is down loses only that one message, never the PU behind it. Setting the
webhook is in Players and characters.
Fix an unmatched name¶
All or nothing
If any name in a month's - PU: grants cannot be matched to a character, the
whole month's award stops and nothing is written. No character is awarded,
not even the ones whose names matched.
This is deliberate. A half-applied month could never be cleanly re-run. The tool reports every unmatched name together with the sessions that used it, so one fix clears them all at once.
Say July's report lists Tussal as unmatched, coming from this session:
You have two fixes. Either one clears every session that used the name.
-
Correct the source. Edit the
- PU:line to the character's canonical name:Use this when the name was simply a slip.
-
Add an
@alias. Use this whenTussalis a short form people will keep writing. Teach the tool the name instead of correcting it forever. Open theLord Tussalcharacter block and add one line to it:Every session that says
Tussalnow resolves, including ones written later. Entities shows where blocks live and how to edit one.
Then run the award again. Because nothing was written the first time, the re-run is clean. The fixed month applies as if the failure never happened.
Election eligibility¶
Council elections are open only to active players. A player is UPRAWNIONY -
eligible to vote - when their PU activity over the last six months clears a
threshold.
Activity is measured across all of that player's characters together, because the vote belongs to the person:
- every PU grant their characters earned inside the window, plus
- one point for each distinct month in which they were active.
That extra point per month is why steady presence beats one busy month. A player at three sessions across three months scores above a player who played three times in one weekend and then vanished.
Eligibility counts a session by the month it was played, not the month it was awarded. Awarding PU late never costs a player their vote. The roll is worked out fresh from the play history each time it is asked for, so it is always current. The window length and the threshold are Council settings.
Related¶
- Record a session - the session header and the other metadata blocks
- Entities - entity blocks, tags, and
@alias - Players and characters - the
GraczandPostaćblocks - The monthly settlement - the workflow that applies pending PU each month