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

fixes malkavians not getting an objective when another vamp breaks the masquerade #3512

Merged
merged 1 commit into from
Sep 26, 2024

Conversation

Absolucy
Copy link
Member

@Absolucy Absolucy commented Sep 22, 2024

About The Pull Request

how has nobody noticed this never working

Changelog

🆑
fix: Fixed malkavian bloodsuckers not getting an objective when another bloodsucker breaks the masquerade.
/:cl:

@Absolucy Absolucy merged commit 4ff5525 into Monkestation:master Sep 26, 2024
25 checks passed
@Absolucy Absolucy deleted the fix-malk-dox branch September 26, 2024 22:06
github-actions bot added a commit that referenced this pull request Sep 26, 2024
Swiftfeather added a commit to Bubberstation/Bubberstation that referenced this pull request Oct 4, 2024
… and more fixes (#2160)

<!-- Write **BELOW** The Headers and **ABOVE** The comments else it may
not be viewable. -->
<!-- You can view Contributing.MD for a detailed description of the pull
request process. -->

## About The Pull Request
Fixes malk's not getting their objective when a bloodsucker breaks the
masq, replaces nullchecks with qdeleted checks in a few places, gohome
checks that those who see the vampire are conscious, and makes
bloodsucker healing code not do multipel update_health check
Partial port of
Monkestation/Monkestation2.0#3534 and full port
of Monkestation/Monkestation2.0#3512
<!-- Describe The Pull Request. Please be sure every change is
documented or this can delay review and even discourage maintainers from
merging your PR! -->

<!-- Please make sure to actually test your PRs. If you have not tested
your PR mention it. -->

## Why It's Good For The Game
Fixes are good, especially for fixing features that should work
<!-- Argue for the merits of your changes and how they benefit the game,
especially if they are controversial and/or far reaching. If you can't
actually explain WHY what you are doing will improve the game, then it
probably isn't good for the game in the first place. -->

## Proof Of Testing
Went ingame and made sure it worked by proccalling break masquarade
<!-- Compile and run your code locally. Make sure it works. This is the
place to show off your changes! We are not responsible for testing your
features. -->

## Changelog

<!-- If your PR modifies aspects of the game that can be concretely
observed by players or admins you should add a changelog. If your change
does NOT meet this description, remove this section. Be sure to properly
mark your PRs to prevent unnecessary GBP loss. You can read up on GBP
and its effects on PRs in the tgstation guides for contributors. Please
note that maintainers freely reserve the right to remove and add tags
should they deem it appropriate. You can attempt to finagle the system
all you want, but it's best to shoot for clear communication right off
the bat. -->

:cl:
fix: Malkavians will now actually get a notification and a objective
once a bloodsucker breaks the masquarade
/:cl:

<!-- Both :cl:'s are required for the changelog to work! You can put
your name to the right of the first :cl: if you want to overwrite your
GitHub username as author ingame. -->
<!-- You can use multiple of the same prefix (they're only used for the
icon ingame) and delete the unneeded ones. Despite some of the tags,
changelogs should generally represent how a player might be affected by
the changes rather than a summary of the PR's contents. -->

<!-- By opening a pull request. You have read and understood the
repository rules located on the main README.md on this project. -->

Co-authored-by: Swift <[email protected]>
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.

1 participant