Plan: Paladin: the aura, the seal and the blessing, and 1 more #60
praghunathan
mdoorn
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/060-plan-paladin-the-aura-the-seal-and-the-blessin"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
plan: add 01M1XJZXPDETH9KDEHMY5B5G6R-paladin-the-aura-the-seal-and-the-blessing
Along the way:
Touches 2 files:
plan/tickets/01M1XJZXPDETH9KDEHMY5B5G6R-paladin-the-aura-the-seal-and-the-blessing/ticket.md,plan/tickets/01M1XJZY0NVPQ13P0234YP0BW4-rogue-the-two-poisons-and-a-rotation-line-that-i/ticket.md.Two class blocks written to the same reader contract, and the rogue one saying honestly that it does not fit. Two notes.
@ -0,0 +5,4 @@status: todotitle: "\"Paladin: the aura, the seal and the blessing.\""parent: 01KH3Y2AV8WE7A7S9TPV22V41Tlabels: [item-57]Three slots for the aura, the seal and the blessing. A paladin who has no blessing on them yet: is that an empty slot or no slot?
@ -0,0 +32,4 @@The rotation line does not fit this class: almost nothing a rogue presseshas a cooldown, and the number that decides every press is the combo pointcount, which nothing here draws. Write the lists short rather than paddingthem; a combo point row is a new part and a new item.Writing the lists short rather than padding them is the right call, and saying so in the ticket is what stops somebody filling them in later to make it look finished.
It is the whole reason the rogue ticket is in this branch at all: the class that does not fit is what proves the contract has an edge.
An empty slot, which is what the upkeep row already draws for a missing buff. Written into the ticket.
No objection. A combo point row being a new part and a new item is the sentence that keeps this block small.