v0.3.0 #19
ncphillips
announced in
Announcements
v0.3.0
#19
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Full Changelog: v0.2.1...v0.3.0
The strip stops guessing which attacks matter and stops disappearing when nothing is selected.
Added
make — every usage mode of every weapon, every innate attack, every unarmed option — which is far
more than belongs in a strip you read at a glance. Dumping the lot in made the one region allowed
to scroll the region that always did. The weapon tables now start empty and you say what belongs
there: drag melee and ranged rows off the character sheet onto the strip, or take the lot with
Add every attack and prune from there.
within its group, or clear off the HUD to remove it;
Alt+↑/↓andDeletedo the same fromthe keyboard.
GM who picked a dragon's four useful attacks out of its forty gets them back the next time
anybody at the table selects the dragon.
dropped on it — the sheet stamps its actor id onto every row, so a foreign attack is refused
rather than mis-resolved.
the HUD and deleting the attack.
vanished between turns and out of combat. (Macros not visible without token selected #16)
Fixed
in the source — comments included — as a class candidate, and utilities were being emitted
unscoped, so two prose comments mentioning "collapse" were enough to ship a global
.collapse { visibility: collapse }that matched Foundry's own sidebar toggle. Every utility nowcarries a
hud:prefix, which makes the leak structurally impossible: a class can only reachFoundry if the source literally says
hud:. The same scan had also leaked.table,.hidden,.blockand a dozen more, which happened to lose to Foundry's own rules only by luck.Changed
Screenshots
No Actor Selected
No Weapons / Add
Weapon Drag Handles
This discussion was created from the release v0.3.0.
All reactions