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

If Grimshaw knocks out his abductor, his dialogue is incorrect #543

Open
ZenithMDC opened this issue Nov 28, 2024 · 3 comments
Open

If Grimshaw knocks out his abductor, his dialogue is incorrect #543

ZenithMDC opened this issue Nov 28, 2024 · 3 comments
Labels
n64 bug bug that exists in the original game

Comments

@ZenithMDC
Copy link

grimshaw_helium.mp4

This is possibly an N64 bug, but I don't have the means to easily verify that. Tested 2a5c3a3 and 9c4aded (i686 and x86_64).

It doesn't appear that he has any other thanks-quip than to say it "was too close", and that he "almost had to take him out" himself. So then I guess he shouldn't say anything at all if he had to take matters into his own hands. Or, we could just consider it a feature and keep it like this since it's kind of funny and most likely a completely harmless oversight.

@RyanDwyer
Copy link

This happens on N64 too.

Each hostage is assigned a different "morale" value. The morale is used to select their thank you message. Grimshaw's morale is 2 which is the "that was too close" message. The holo room hostage's morale is 3 which is "quick, let's get to the hangar, and thanks."

However, morale serves a second purpose by the game engine. Every character's morale is incremented whenever they do a melee attack. This is because for certain characters, the game engine uses morale as a melee damage multiplier, so their melee attacks become stronger each time they do them.

In your video, Grimshaw did a melee attack on the guard which increased his morale to 3, so he said a different character's message.

The conflicting usage of morale was surely not intentional, but it's what N64 does and is harmless so I reckon it should be left as is.

@fgsfdsfgs fgsfdsfgs added the n64 bug bug that exists in the original game label Nov 29, 2024
@fgsfdsfgs
Copy link
Owner

I'll mark it as an N64 bug just to make note of its existence then.

@ZenithMDC
Copy link
Author

Thanks for the thorough explanation, @RyanDwyer. And, yeah, I completely agree that it should be left as-is. Personally, I'm not interested in making alterations to the game if the bug is completely innocuous. I suppose this issue can be closed now, unless you feel that something should be done, @fgsfdsfgs. Up to you.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
n64 bug bug that exists in the original game
Projects
None yet
Development

No branches or pull requests

3 participants