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

Adds Flank Route & Choke Point West of Eastern Lab Trijent Dam #5645

Merged
merged 2 commits into from
Feb 20, 2024
Merged

Adds Flank Route & Choke Point West of Eastern Lab Trijent Dam #5645

merged 2 commits into from
Feb 20, 2024

Conversation

hislittlecuzingames
Copy link
Contributor

@hislittlecuzingames hislittlecuzingames commented Feb 3, 2024

About the pull request

Adds another path for Xenos to attack marines when at eastern labs.

Explain why it's good for the game

Allows for more combat on Trijent.
I think Trijent is boring, and once marines get into Eastern Lab, the xenos usually just die and just a few marines are fighting because there's not enough space for xenos to fight.

Testing Photographs and Procedure

Small map edit.

The changes I made and a picture circling what was changed.

image

image

Areas are also setup.
image

Changelog

🆑
maptweak: tweaked Trijent Dam to add a new choke point.
/:cl:

@github-actions github-actions bot added the Mapping did you remember to save in tgm format? label Feb 3, 2024
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.

Opening the south pattern a bit more as you have is fine, but opposed to adding the additional flank due to risk of marines/xenos just going across the river directly from the LZ if chosen.

@Nanu308 Nanu308 marked this pull request as draft February 6, 2024 22:32
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 Feb 14, 2024
@hislittlecuzingames
Copy link
Contributor Author

@Nanu308 it's now restored; idk what that artifact is-must be some dirt or something that I didn't re-add.

@hislittlecuzingames hislittlecuzingames marked this pull request as ready for review February 17, 2024 17:32
@github-actions github-actions bot removed the Stale beg a maintainer to review your PR label Feb 18, 2024
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.

lgtm

@Nanu308 Nanu308 added the Mapping Approved adds 500 new dict keys label Feb 20, 2024
@Nanu308 Nanu308 added this pull request to the merge queue Feb 20, 2024
Merged via the queue into cmss13-devs:master with commit b05372b Feb 20, 2024
27 checks passed
cm13-github added a commit that referenced this pull request Feb 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Mapping Approved adds 500 new dict keys Mapping did you remember to save in tgm format?
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants