From 80b0208984ec1b2a4d1e2427440227b055eb147e Mon Sep 17 00:00:00 2001 From: Grant Shoshin Shangreaux Date: Sat, 21 Jan 2023 10:31:41 -0600 Subject: Docs: add notes from pairing brainstomre session to DEV.org --- DEV.org | 73 +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 73 insertions(+) diff --git a/DEV.org b/DEV.org index ad8eab4..987dcc8 100644 --- a/DEV.org +++ b/DEV.org @@ -14,3 +14,76 @@ * More fings for wargfood ** TODO Setup Auth / User Reg ** TODO Deploy + + +* Notes & Concepts +** Nomenclature + +| Project Managment Term | Dnd Term | +|-------------------------------+-------------------------------| +| Task | Monster | +| User / Team Member | Hero | +| Landing Page: Overview | Tavern | +| Authorization | Doorkeeper | +| Sprint | Quest | +| Project | Campaign | +| User account creation | Shrine | +| | Equipment/Loot | +| Assignment To A Task | Melee | +| Task Category / Tags | Monster characteristics | +| Miss Deadline / Take too long | Hero Death | +| Time Budget | Hit Points | +| Make a task | Report Rumor of Beast/Monster | +| Areas of Expertise | Character Class | +| | Level / Experience | + + +Campaigns can have a pace. The pace is used to deduct hitpoints when +nothing happens. Penalty for retreating: Roll a die,lose something +(hp), (equip). + + +** TODO Plan Out Task Categories and Character Classes More Thoroughly + +Here's the idea: Monsters have characteristics. Heroes' character classes +are determined by the kinds of monsters they defeat. + +Should we pick discrete classes of character? Discrete classes of monsters? + +E.g. Goblin wizard = ??? + Gelatinous Cube = ??? + +| Task Category | Monster Class (smaller) | Monster Class (Bigger) | +|-----------------+---------------------------------+------------------------| +| Feature | Boss (dragon warlock elemental) | e.g dragon | +| Task-SubFeature | orc, goblin, (minions) | orc chieftan | +| Task-StandAlone | not-minions (wolf) | minotaur | +| Bug 1 | (the undead) | | +| Bug 2 | (horrible undead) | | + + +| Different Task Categorization | +|------------------------------------------------------| +| coding & debugging (& reproducing bugs) & unit tests | +| user testing | +| devops | +| art | +| documentation | +| | + +*** Non-task merit earning action + +- reporting a rumor that is verified +- verifying a rumor (?) +- lose merit if you rumor is considered specious +- adding context to a rumor (maybe other people give a +1) +- aiding another hero somehow + + +*** Note : monster reporting and reclassification + +When a feature/task/bug is "rumored", the "verifier" should be able to +reclassify it. + +there could even be monster promotion mid battle. If it is revealed +that a monster is much much more deadly than initially thought. -- cgit v1.2.3