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

Update to whiskey outpost map. #6255

Closed
wants to merge 8 commits into from
Closed

Conversation

Huffie56
Copy link
Contributor

@Huffie56 Huffie56 commented May 7, 2024

About the pull request

The PR aim is increase space available inside main bunker to equip.
also i fixed some M56 missing cades sandbag in front of them.
i also change central part of pillbox to change a bit the dynamic around it to create connection between them while giving a new vulnerability to it.

Explain why it's good for the game

Testing Photographs and Procedure

Screenshots & Videos

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

Changelog

🆑
mapadd: Added an LZ to Whiskey Outpost map only for admin event usage.
maptweak: added a proper room for the lavatory and the showers.
maptweak: moved the reporter room west of the canteen.
maptweak: added some missing sandbag or cades on the static M56D.
maptweak: increased the size of the dormitories and the prep rooms north of the canteen also added clothing and weapon vendors.
maptweak: change the area of the central pillboxes moved the medical outpost between the pilllboxes.
/:cl:

@github-actions github-actions bot added the Mapping did you remember to save in tgm format? label May 7, 2024
@Huffie56 Huffie56 marked this pull request as ready for review May 7, 2024 07:20
@Huffie56 Huffie56 requested a review from Nanu308 as a code owner May 7, 2024 07:20
@Huffie56 Huffie56 marked this pull request as draft May 10, 2024 10:08
@Huffie56 Huffie56 marked this pull request as ready for review May 13, 2024 15:05
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 May 21, 2024
@Drulikar Drulikar removed the Stale beg a maintainer to review your PR label May 24, 2024
Copy link
Contributor

github-actions bot commented Jun 1, 2024

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 Jun 1, 2024
@Drulikar
Copy link
Contributor

Drulikar commented Jun 7, 2024

Stale exempt until reviewed again.

@Drulikar Drulikar added Stale Exempt PR can't go stale and removed Stale beg a maintainer to review your PR labels Jun 7, 2024
@cm13-github cm13-github added the Merge Conflict PR can't be merged because it touched too much code label Jul 10, 2024
@cm13-github
Copy link
Contributor

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

@harryob
Copy link
Member

harryob commented Oct 6, 2024

been in merge conflict for two months, feel free to poke someone to reopen this if you're still interested

@harryob harryob closed this Oct 6, 2024
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? Merge Conflict PR can't be merged because it touched too much code Stale Exempt PR can't go stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants