Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ever have a stacked character die on a shop level? #44

Closed
wants to merge 1 commit into from

Conversation

ryfactor
Copy link
Member

This change enables a message to appear indicating whether or not you are putting your character at risk of never spawning a ghost.
A cryptic sort of message appears, supplementary to the level entry message, hinting that bones are not to be found or left behind on that level. It triggers only once and disappears after.

Messages range from:
UT1: "You fear you may never be seen or heard from again."
Catacombs: "You worry you might never be found down here, either dead or alive..."
GC; Shop or Chest level: "It feels less oppressive here. Your spirits rise."

Attnam, New Attnam and Oree's Lair have no message.

This change enables a message to appear indicating whether or not you are putting your character at risk of never spawning a ghost.
A cryptic sort of message appears, alongside the level entry message, hinting that bones are not to be found or left behind on that level. It triggers only once and disappears after.

Messages range from:
UT1: "You fear you may never be seen or heard from again."
Catacombs: "You worry you might never be found down here, either dead or alive..."
GC; Shop or Chest level: "It feels less oppressive here. Your spirits rise."

Attnam, New Attnam and Oree's Lair have no message.
@ryfactor ryfactor closed this Jun 28, 2015
@ryfactor ryfactor deleted the NoBones branch August 12, 2015 04:00
ryfactor pushed a commit to ryfactor/ivan that referenced this pull request Oct 29, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant