You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Per this line in monst.c, both padawan and player monster Jedi act as quest guardians for a player Jedi - my assumption is this is intentional on the part of the original Jedi patch's author.
The unforeseen consequence of this is that, when patched into variants that generate hostile random player monsters anywhere outside the Quest or Astral - e.g. SlashTHEM and Hack'EM, where this was discovered by mobileuser to what I'd imagine as great chagrin - killing a hostile Jedi that was not made hostile through any action of your own induces the massive alignment penalty associated with killing a quest guardian. Take that and add how much more alignment matters in the EvilHack-derived Hack'EM, and I'm sure you can picture the disgust on past!Mobile's face.
I'll crosspost this to the Hack'EM git as well, but I don't have a PR to go with this, sadly - I'll leave that to cbus, who brought it to my attention.
The text was updated successfully, but these errors were encountered:
Per this line in monst.c, both padawan and player monster Jedi act as quest guardians for a player Jedi - my assumption is this is intentional on the part of the original Jedi patch's author.
The unforeseen consequence of this is that, when patched into variants that generate hostile random player monsters anywhere outside the Quest or Astral - e.g. SlashTHEM and Hack'EM, where this was discovered by mobileuser to what I'd imagine as great chagrin - killing a hostile Jedi that was not made hostile through any action of your own induces the massive alignment penalty associated with killing a quest guardian. Take that and add how much more alignment matters in the EvilHack-derived Hack'EM, and I'm sure you can picture the disgust on past!Mobile's face.
I'll crosspost this to the Hack'EM git as well, but I don't have a PR to go with this, sadly - I'll leave that to cbus, who brought it to my attention.
The text was updated successfully, but these errors were encountered: