pyrex/fledgling
1
0
Fork 0
Code Issues 17 Pull Requests Actions Packages Projects Releases Wiki Activity

Endgame logic: Consolidate carry-over conditions in one place and handle them well #25

New Issue
Open
opened 2025-02-18 06:32:37 +00:00 by pyrex · 0 comments
pyrex commented 2025-02-18 06:32:37 +00:00
Owner
Copy Link

Things that carry over:

  • The master's wish. (this works)
  • The number of talent upgrades per successor. (this should increase by N every game)
  • The character, in case of punishment status. (this works)
  • Any thrall who got their item. (They carry over, but the item goes away. Their health status carries over too. Dead thralls are removed.)

Allow new game + as a thrall, if that thrall was vampirized.

This should somehow be conveyed in the game epilogue.

Things that carry over: - The master's wish. (this works) - The number of talent upgrades per successor. (this should increase by N every game) - The character, in case of punishment status. (this works) - Any thrall who got their item. (They carry over, but the item goes away. Their _health status_ carries over too. Dead thralls are removed.) Allow new game + as a thrall, if that thrall was vampirized. This should somehow be conveyed in the game epilogue.
pyrex added the
core
refactor
 labels 2025-02-18 06:48:06 +00:00
pyrex added the
Importance
Important
 label 2025-02-22 19:50:13 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
art
This is primarily a change to the pixel assets
core
This is needed for the game to function on a basic level.
good first issue
Kistaro! Work on these.
Importance
Important
This should be done before end of February
Importance
Postponed
This issue doesn't need to be done right now.
polish
This makes the game feel nice to play, but it's not essential
refactor
The code is bad: fix it!
speculative
"I don't know if this is a good idea yet."
No Label
core
Importance
Important
refactor
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bhijn kistaro pyrex
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: pyrex/fledgling#25
No description provided.
Delete Branch "%!s()"

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?