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

Made Research nightmare insert blast doors no longer be invulnerable #3788

Merged
merged 2 commits into from
Jul 23, 2023

Conversation

JackieEstegado
Copy link
Contributor

@JackieEstegado JackieEstegado commented Jul 3, 2023

About the pull request

The "fully locked" nightmare insert had blast doors that were: Unacidable, unpryable and just generally indestructible.
Replaced it with a variant that is non of those, but merely van-proof.

Explain why it's good for the game

It lead to very strange gameplay where you could destroy the walls, but not the podlocks. Would be particularly problematic during an LZ2 siege.
I doubt that the intention with this insert was to make Research completely inaccessible, so I rather made the podlocks destructible rather than the walls invulnerable too.

Indestructible.mp4

Testing Photographs and Procedure

Screenshots & Videos

Put screenshots and videos here with an empty line between the screenshots and the <details> tags.

Changelog

🆑
maptweak: Made LV-624's "Fully-locked" Research nightmare insert no longer have indestructible blast doors.
/:cl:

@github-actions
Copy link
Contributor

github-actions bot commented Jul 3, 2023

You currently have a negative Fix/Feature pull request delta of -1. Maintainers may close this PR at will. Fixing issues or improving the codebase will improve this score.

@github-actions github-actions bot added the Mapping did you remember to save in tgm format? label Jul 3, 2023
@github-actions
Copy link
Contributor

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

@github-actions github-actions bot added the Stale beg a maintainer to review your PR label Jul 11, 2023
@github-actions github-actions bot closed this Jul 18, 2023
@morrowwolf morrowwolf reopened this Jul 23, 2023
@morrowwolf morrowwolf removed the Stale beg a maintainer to review your PR label Jul 23, 2023
@morrowwolf morrowwolf added this pull request to the merge queue Jul 23, 2023
Merged via the queue into cmss13-devs:master with commit 5ebbd08 Jul 23, 2023
53 checks passed
cm13-github added a commit that referenced this pull request Jul 23, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mapping did you remember to save in tgm format?
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants