joshuaandClaude Opus 5.5
57fba68a48
Seven steps in one commit, 1.15.0 to 1.21.0. They change the same files and were not saved apart, so they go in together. - The battle at a glance (1.15). A strip across the top of an encounter lists everyone in turn order and stays in view; a click goes to that card. On a wide screen the stat block of whoever is on turn stays beside the cards, and Pin keeps anyone else's there. Saving throws, every skill and passive Perception, Investigation and Insight are on encounter cards and in the character panel, which "Sheet" on a card and a button on the party overview open. For the DM, N is Next Turn and S opens the sheet of whoever is on turn. The party overview shows passive scores and spell save DC. - Subclasses (1.16). Three per class, picked in the level-up checklist at level 2 (cleric, druid, wizard) or 3, shown beside the class everywhere, and changed by the DM from the sheet: the old one's lines come out of Special Abilities and the new one's go in. Characters already at that level keep the path they were on. - Character state (1.17). Inspiration, exhaustion and conditions on the sheet and in the panel, and counters for what a class does a set number of times (Rage, Ki, Channel Divinity...), which the player spends and a rest gives back. A long rest takes a level of exhaustion off. A character's conditions are their own now: they stay from one encounter to the next. - Faster battles (1.18). Up to 20 of a monster added at once, numbered. One button rolls initiative for the monsters and NPCs. A condition can be given a number of rounds and then comes off by itself. Hovering over a condition shows its rule, and damaging someone who is Concentrating shows the save to call for. - Rolls from the sheet (1.19). A number with a dotted underline rolls when clicked, with its bonus: skills, saves, ability checks, attacks, damage, spell dice, and a monster's attack, damage and abilities. The dice roller has advantage and disadvantage. "Call for a roll" rolls one check or save for the whole party. Rolls stay in the browser. - XP and difficulty (1.20). An encounter shows the DM how hard it is, Trivial to Deadly, from the monsters' challenge ratings against the characters in it, and what it is worth in XP; one button shares that out, once. The sheet and the party overview show XP and when a level is due. Levelling up stays the DM's decision. - Subclasses are optional per campaign (1.21). With "Characters choose a subclass" unticked in the campaign's Settings nobody is asked, each class follows its first subclass, and none is named. - Conditions, exhaustion, counters and subclass features are reminders for the table: none of them changes a number on the sheet. - The docs cover all of it, with generated tables of what each subclass adds. - New migrations: a character's subclass; inspiration, exhaustion, conditions and spent counters on a character; the rounds left on a combatant's conditions; the XP awarded for an encounter; the campaign's subclass setting. - All packages at version 1.21.0. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
21 lines
978 B
SQL
21 lines
978 B
SQL
-- AlterTable: how a character is doing beyond HP, and the class counters
|
|
-- (Rage, Ki...) spent since the rest that gives them back, as { key: used }.
|
|
ALTER TABLE "characters" ADD COLUMN "resourcesUsed" JSONB NOT NULL DEFAULT '{}',
|
|
ADD COLUMN "inspiration" BOOLEAN NOT NULL DEFAULT false,
|
|
ADD COLUMN "exhaustion" INTEGER NOT NULL DEFAULT 0,
|
|
ADD COLUMN "conditions" TEXT[] DEFAULT ARRAY[]::TEXT[];
|
|
|
|
-- A character's conditions used to be kept per encounter. They are the
|
|
-- character's own now, so those given in an encounter still in progress move
|
|
-- onto the character.
|
|
UPDATE "characters" c SET "conditions" = held.conditions
|
|
FROM (
|
|
SELECT p."characterId", array_agg(DISTINCT condition) AS conditions
|
|
FROM "encounter_participants" p
|
|
JOIN "encounters" e ON e."id" = p."encounterId"
|
|
CROSS JOIN LATERAL unnest(p."conditions") AS condition
|
|
WHERE p."characterId" IS NOT NULL AND e."status" = 'ACTIVE'
|
|
GROUP BY p."characterId"
|
|
) held
|
|
WHERE c."id" = held."characterId";
|