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

Break Up Secure Storage LV-624 #4767

Closed
wants to merge 3 commits into from

Conversation

Steelpoint
Copy link
Contributor

@Steelpoint Steelpoint commented Oct 22, 2023

Breaks open the secure storage on LV-624.

Explain why it's good for the game

Survivor holds on 624 are usually a case of either the survivors running and gunning or hiding in secure storage for 18 minutes until the xenos reach T3, then its a case of if the Xenos can breach secure storage before the Marines arrive. Secure storage is simply not a fun exercise for both sides, if survivors are going to survive there should be more effort than hiding in a pre-made bunker.

I should note that this does not make Secure Storage a impossible hold, only that its now not 100% inaccessible to xenos until they reach T3.

Testing Photographs and Procedure

Screenshots & Videos

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

Changelog

🆑
maptweak: Secure Storage on LV-624 has been broken open, making it far less defendable but easier to access.
/:cl:

@github-actions github-actions bot added the Mapping did you remember to save in tgm format? label Oct 22, 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 Oct 30, 2023
@Diegoflores31
Copy link
Contributor

Diegoflores31 commented Nov 1, 2023

sincerely i dont think this is the way to encourage anything but making it a more solid meta or returning back to 24/7 LZ1 holds.

PD: also show images of before/after on your PR

@github-actions github-actions bot removed the Stale beg a maintainer to review your PR label Nov 2, 2023
@Steelpoint
Copy link
Contributor Author

sincerely i dont think this is the way to encourage anything but making it a more solid meta or returning back to 24/7 LZ1 holds.

PD: also show images of before/after on your PR

The current situaton means once a survivor gets inside it becomes literally impossible for any xeno to be able to threaten them until the 20 minute mark when T3s can spawn, which puts huge pressure on the xenos since they risk being hit by the arriving Marines at any moment.

At least in this circumstance the xenos can still threaten the survivors.

If needs be I can break up more of the secure dome so there are multiple entrances so its not so simple.

@Steelpoint
Copy link
Contributor Author

MapDiffBot shows the changes as well

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 Nov 11, 2023
@Nanu308
Copy link
Member

Nanu308 commented Nov 14, 2023

Requested @Zonespace27 input, if he wants the gameplay implications it i can go over the mapping itself

@Nanu308 Nanu308 removed the Stale beg a maintainer to review your PR label Nov 14, 2023
Copy link
Contributor

@Zonespace27 Zonespace27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm

@Zonespace27 Zonespace27 added Balance You need to be a professional veteran game maintainer to comprehend what is being done here. Balance Approved This PR has had its balance and gameplay-affecting aspects approved. Cry to the Head-maint about it. labels Nov 14, 2023
@Nanu308 Nanu308 added the Mapping Approved adds 500 new dict keys label Nov 16, 2023
Copy link
Member

@Nanu308 Nanu308 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

map lgtm

@Nanu308 Nanu308 added this pull request to the merge queue Nov 16, 2023
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to a conflict with the base branch Nov 16, 2023
@cm13-github cm13-github added the Merge Conflict PR can't be merged because it touched too much code label Nov 16, 2023
@cm13-github
Copy link
Contributor

This pull request has conflicts, please resolve those before we can evaluate the pull request.

@Huffie56
Copy link
Contributor

if your deleting secure storage blast door you should delete all the connect buttons to open it from the outside.
research and nightmare insert, armory and nightmare insert, commanding office, cl office.
@Steelpoint

@Steelpoint
Copy link
Contributor Author

I hate merge conflicts, I'll re-do this PR when I have free time. Maybe one day I can get the hooks to work to stop this being a issue.

@Steelpoint Steelpoint closed this Nov 17, 2023
github-merge-queue bot pushed a commit that referenced this pull request Nov 22, 2023
Breaks open the secure storage on LV-624. 

Remake of #4767 

Mapping changes are identical, however this PR has also removed buttons
that reference the now removed secure dome shutters from the rest of the
map, and similar nightmare inserts.

# Explain why it's good for the game

Survivor holds on 624 are usually a case of either the survivors running
and gunning or hiding in secure storage for 18 minutes until the xenos
reach T3, then its a case of if the Xenos can breach secure storage
before the Marines arrive. Secure storage is simply not a fun exercise
for both sides, if survivors are going to survive there should be more
effort than hiding in a pre-made bunker.

I should note that this does not make Secure Storage a impossible hold,
only that its now not 100% inaccessible to xenos until they reach T3.

# Testing Photographs and Procedure
<details>
<summary>Screenshots & Videos</summary>

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

</details>


# Changelog
:cl:
maptweak: Secure Storage on LV-624 has been broken open, making it far
less defendable but easier to access.
/:cl:

Co-authored-by: Steelpoint <[email protected]>
@Steelpoint Steelpoint deleted the SurvMain branch July 17, 2024 17:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Balance Approved This PR has had its balance and gameplay-affecting aspects approved. Cry to the Head-maint about it. Balance You need to be a professional veteran game maintainer to comprehend what is being done here. Mapping Approved adds 500 new dict keys Mapping did you remember to save in tgm format? Merge Conflict PR can't be merged because it touched too much code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants