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

Hammerhead Upgrade + Rigsuits + Baron Integrity Increase #6302

Merged

Conversation

jakeramsay007
Copy link
Contributor

@jakeramsay007 jakeramsay007 commented Jan 29, 2024

About The Pull Request

Redesigns the hammerhead somewhat to be more like a patrol and response carrier, with a more streamlined design for carrying personnel and detainees.

Brings the Rift to parity with other maps for security EVA by replacing the spare security officer lockers in EVA storage with an additional security voidsuit and two hazard rigs, plus a hazard rig in the HoS' office.

Increases the Baron's integrity by 200 (from 400 to 600) to offset the damage impacting a wall causes (which is the only way to stop in space currently), and increases the Duke's integrity by 400 to match the intended double armour value.

🆑
tweak: Redesigned the Hammerhead Patrol Barge
tweak: Increased armour values for the Baron and Duke space fighters
balance: Added an additional voidsuit and three hazard rigs to security to bring the rift to parity with other map values
add: Adds an old_wall flag to lights, allowing them to be placed on old-style walls without ending up inside of them
/:cl:

@github-actions github-actions bot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Jan 29, 2024
@jakeramsay007
Copy link
Contributor Author

jakeramsay007 commented Jan 29, 2024

image

silicons pushed a commit that referenced this pull request Jan 30, 2024
@TheLordME
Copy link
Collaborator

grafik
68747470733a2f2f616666656374656461726330372e626c6f622e636f72652e77696e646f77732e6e65742f6d6462322f696d616765732f3133323337343330382f32303939383639343530342f6d2f6d6170735f726966745f6c6576656c735f726966742d30352d73

silicons pushed a commit that referenced this pull request Jan 31, 2024
silicons pushed a commit that referenced this pull request Feb 1, 2024
silicons pushed a commit that referenced this pull request Feb 1, 2024
silicons pushed a commit that referenced this pull request Feb 1, 2024
silicons pushed a commit that referenced this pull request Feb 1, 2024
silicons pushed a commit that referenced this pull request Feb 2, 2024
silicons pushed a commit that referenced this pull request Feb 2, 2024
silicons pushed a commit that referenced this pull request Feb 2, 2024
silicons pushed a commit that referenced this pull request Feb 2, 2024
silicons pushed a commit that referenced this pull request Feb 2, 2024
silicons pushed a commit that referenced this pull request Feb 2, 2024
silicons pushed a commit that referenced this pull request Feb 4, 2024
silicons pushed a commit that referenced this pull request Feb 4, 2024
silicons pushed a commit that referenced this pull request Feb 4, 2024
silicons pushed a commit that referenced this pull request Feb 4, 2024
silicons pushed a commit that referenced this pull request Feb 4, 2024
silicons pushed a commit that referenced this pull request Feb 4, 2024
silicons pushed a commit that referenced this pull request Feb 6, 2024
silicons pushed a commit that referenced this pull request Feb 7, 2024
silicons pushed a commit that referenced this pull request Feb 7, 2024
silicons pushed a commit that referenced this pull request Feb 13, 2024
Copy link

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 ~ two week, 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 label Feb 15, 2024
silicons pushed a commit that referenced this pull request Feb 15, 2024
silicons pushed a commit that referenced this pull request Feb 24, 2024
silicons pushed a commit that referenced this pull request Feb 24, 2024
@silicons silicons merged commit f49b571 into Citadel-Station-13:master Feb 24, 2024
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants