Add Mercenary Jumpsuit to Passenger Loadout Options (w. Time Requirement) #52

Merged
Makar0w merged 2 commits from patch-1 into master 2026-04-24 18:29:12 +00:00
Makar0w commented 2026-04-23 00:44:32 +00:00 (Migrated from github.com)

About the PR

Why / Balance

Technical details

Media

Requirements

Breaking changes

Changelog

<!-- SPDX-FileCopyrightText: 2021 Pieter-Jan Briers <pieterjan.briers+git@gmail.com> SPDX-FileCopyrightText: 2021 Swept <sweptwastaken@protonmail.com> SPDX-FileCopyrightText: 2021 mirrorcult <lunarautomaton6@gmail.com> SPDX-FileCopyrightText: 2022 AJCM-git <60196617+AJCM-git@users.noreply.github.com> SPDX-FileCopyrightText: 2022 Kara <lunarautomaton6@gmail.com> SPDX-FileCopyrightText: 2023 DrSmugleaf <DrSmugleaf@users.noreply.github.com> SPDX-FileCopyrightText: 2023 Kevin Zheng <kevinz5000@gmail.com> SPDX-FileCopyrightText: 2024 Vasilis <vasilis@pikachu.systems> SPDX-FileCopyrightText: 2024 lzk <124214523+lzk228@users.noreply.github.com> SPDX-FileCopyrightText: 2025 Aiden <28298836+Aidenkrz@users.noreply.github.com> SPDX-License-Identifier: AGPL-3.0-or-later --> <!-- Guidelines: https://docs.spacestation14.io/en/getting-started/pr-guideline --> <!-- NOTE: All code submitted to this repository is ALWAYS licensed under the AGPL-3.0-or-later license. The REUSE Specification headers or separate .license files indicate a secondary license (e.g., MPL or MIT) solely to facilitate integration for projects that do not use the AGPL license. This secondary license does not replace the fact that AGPL-3.0-or-later remains the primary and binding license. Uncomment and modify the following line if you wish to change the license from the default of AGPL.--> <!--- LICENSE: AGPL --> ## About the PR <!-- What did you change? --> ## Why / Balance <!-- Discuss how this would affect game balance or explain why it was changed. Link any relevant discussions or issues. --> ## Technical details <!-- Summary of code changes for easier review. --> ## Media <!-- Attach media if the PR makes ingame changes (clothing, items, features, etc). Small fixes/refactors are exempt. Media may be used in SS14 progress reports with credit. --> ## Requirements <!-- Confirm the following by placing an X in the brackets [X]: --> - [x] I have read and am following the [Pull Request and Changelog Guidelines](https://docs.spacestation14.com/en/general-development/codebase-info/pull-request-guidelines.html). - [x] I have added media to this PR or it does not require an ingame showcase. <!-- You should understand that not following the above may get your PR closed at maintainer’s discretion --> ## Breaking changes <!-- List any breaking changes, including namespaces, public class/method/field changes, prototype renames; and provide instructions for fixing them. This will be posted in #codebase-changes. --> **Changelog** <!-- Add a Changelog entry to make players aware of new features or changes that could affect gameplay. Make sure to read the guidelines and take this Changelog template out of the comment block in order for it to show up. Changelog must have a :cl: symbol, so the bot recognizes the changes and adds them to the game's changelog. --> <!-- :cl: - add: Added fun! - remove: Removed fun! - tweak: Changed fun! - fix: Fixed fun! -->
LukeZurg22 commented 2026-04-23 01:07:17 +00:00 (Migrated from github.com)

This is not Monolith nor Hullrot. Name Pull Requests and Commits appropriately. I hold you to this standard as I hold myself, and others. The change itself is pretty benign.

Unimportant, But Notable

  • I also recognize this PR as an indulgent one mostly meant for yourself.
  • I also see that your branch is titled "patch". It's a funny name that doesn't accurately reflect what you're doing on it. Not any issue, but I noticed.
This is not Monolith nor Hullrot. Name Pull Requests and Commits appropriately. I hold you to this standard as I hold myself, and others. The change itself is pretty benign. # Unimportant, But Notable - I also recognize this PR as an indulgent one mostly meant for yourself. - I also see that your branch is titled "patch". It's a funny name that doesn't accurately reflect what you're doing on it. Not any issue, but I _noticed_.
LukeZurg22 commented 2026-04-23 01:09:35 +00:00 (Migrated from github.com)

General consensus says that this is an acceptable change but only if you seal it behind having hours in the Security department. Seems fair, I'd say!

General consensus says that this is an acceptable change but only if you seal it behind having hours in the Security department. Seems fair, I'd say!
Makar0w commented 2026-04-23 17:37:10 +00:00 (Migrated from github.com)

Done twin

Done twin
Sign in to join this conversation.
No description provided.