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

Arrivals blacklist for bluespace lockers and QSIs #34072

Open
wants to merge 3 commits into
base: master
Choose a base branch
from

Conversation

crazybrain23
Copy link
Contributor

@crazybrain23 crazybrain23 commented Dec 26, 2024

About the PR

Added the arrivals blacklist to bluespace lockers and quantum spin inverters.

Why / Balance

Both bluespace lockers and quantum spin inverters could and have been used to get back to the arrivals terminal. This is a problem because players have recently been building "colonies" out on the arrivals planet map.
This change prevents the method commonly used to get to the terminal (bluespace lockers) and another method I knew of (quantum spin inverters).

Technical details

In the bluespace locker event, just after the lockers are configured, I made it ensure the locker has the arrivals blacklist component. As for the quantum spin inverter, I just added the component in the yaml.

Media

image
image
(QSI worked in exactly the same way so screenshots are pointless)

Requirements

## Breaking changes

Changelog

🆑 crazybrain

  • tweak: Bluespace lockers and quantum spin inverters can no longer go on the arrivals shuttle.

@github-actions github-actions bot added S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. size/XS Denotes a PR that changes 0-9 lines. labels Dec 26, 2024
@crazybrain23 crazybrain23 changed the title Add bluespace lockers and QSIs to arrivals blacklist Arrivals blacklist for bluespace lockers and QSIs Dec 26, 2024
@crazybrain23 crazybrain23 added P3: Standard Priority: Default priority for repository items. D3: Low Difficulty: Some codebase knowledge required. A: General Interactions Area: General in-game interactions that don't relate to another area. T: New Feature Type: New feature or content, or extending existing content S: Needs Review Status: Requires additional reviews before being fully accepted T: Of Admin Interest Type: Affects administration work a lot, and might require admins to weigh in on and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Dec 26, 2024
@@ -45,6 +46,8 @@ protected override void Started(EntityUid uid, BluespaceLockerRuleComponent comp
_bluespaceLocker.GetTarget(potentialLink, comp, true);
_bluespaceLocker.BluespaceEffect(potentialLink, comp, comp, true);

EnsureComp<ArrivalsBlacklistComponent>(potentialLink); // To stop people getting to arrivals terminal
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wouldn't this only blacklist one of the two lockers since the other one is assigned in GetTarget?
This should probably be moved to the OnStartup function for the BluespaceLockerComponent so that all bluespace lockers are arrival shuttle immune.

@slarticodefast
Copy link
Member

Also storing the QSI inside a storage container will make it teleport to the center of the shuttle instead of staying at the position of the container. But that can be fixed in a separate PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: General Interactions Area: General in-game interactions that don't relate to another area. D3: Low Difficulty: Some codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Needs Review Status: Requires additional reviews before being fully accepted size/XS Denotes a PR that changes 0-9 lines. T: New Feature Type: New feature or content, or extending existing content T: Of Admin Interest Type: Affects administration work a lot, and might require admins to weigh in on
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants