This repository was archived by the owner on May 22, 2025. It is now read-only.
[Bounty] Kilostation #11413
Merged
[Bounty] Kilostation #11413
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Yogbot-13
added
Feature
github-actions
bot
added
the
Config
Contributor
|
tbh having hostile mobs in the station doesn’t seem like a terribly great idea |
Contributor
Author
Those are removed in the version I made |
Contributor
If they're in maints, I can see it as a way to discourage people from going into maints on random-ass loot quests. |
Contributor
|
omega was my favorite map... sadge... |
Hopekz
reviewed
May 4, 2021
Co-authored-by: Hopekz <hopekxx@gmail.com>
Yogbot-13
pushed a commit
that referenced
this pull request
May 10, 2021
Yogbot-13
pushed a commit
that referenced
this pull request
May 10, 2021
Yogbot-13
pushed a commit
that referenced
this pull request
May 10, 2021
Contributor
|
kinostation |
Yogbot-13
pushed a commit
that referenced
this pull request
May 11, 2021
Yogbot-13
pushed a commit
that referenced
this pull request
May 11, 2021
Yogbot-13
pushed a commit
that referenced
this pull request
May 11, 2021
Contributor
|
I don't like the lack of random engines. |
Contributor
Author
|
Did a lot of fixes during the testmerge, I can now say with confidence that most of the bugs are fixed and this is ready for a fullmerge after the bounty part is settled. |
patpol4
added
Awaiting - Action - HD
Yogbot-13
pushed a commit
that referenced
this pull request
May 25, 2021
JamieD1
approved these changes
Jun 13, 2021
Yogbot-13
added a commit
that referenced
this pull request
Jun 13, 2021
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
General Documentation
Bounty: https://forums.yogstation.net/threads/40-60-swaps-omega-with-kilo-is-our-low-pop-map-ss13-server.23323/#post-199059
Intent of your Pull Request
Adds Kilo as one of our maps.
General map:
Tg's Kilo for reference: https://affectedarc07.github.io/SS13WebMap/TG/KiloStation/
I didnt implement random engines, and only added like 3 random maint rooms because what kilo has right now is pretty good.
Gateway room has been replaced with clerk
Why is this change good for the game?
Intended as a replacement for omega later on, is a lowpopish map but doesn't compromise on features like certain departments or head roles
Wiki Documentation
Briefly describe your PR and the impacts of it, in layman's terms.
Adds Kilo as one of our stations
What should players be aware of when it comes to the changes your PR is implementing?
Adds Kilo as one of our stations
What general grouping does this PR fall under?
new station
Are there any aspects of the PR that you would like us not to mention on the Wiki?
not really
If there are any numerical values involved in your PR that will be relevant to a player, please note them here.
nope
Changelog
🆑
rscadd: adds KiloStation as one of our stations along with all it's shuttles
/:cl: