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

Mailing malicious stuff back on supply shuttles now delays send time, gives unique centcomm announcements and appearance at roundend #37411

Open
wants to merge 14 commits into
base: Bleeding-Edge
Choose a base branch
from

Conversation

SECBATON-GRIFFON
Copy link
Contributor

@SECBATON-GRIFFON SECBATON-GRIFFON commented Feb 6, 2025

[content]

What this does

so far, this covers mailing TTVs back, with unique scenarios for the bomb being disarmed, going off in the shuttle, or at centcomm, depending on how it's arranged and how the timer or prox sensor is set:

  • if less than 1 minute remains while actively ticking down, the announcement indicates it exploded on the shuttle. this causes some explosion damage looks to the shuttle itself when next seen, and multiplies the time taken to send the supply shuttle to the station by 1.5
  • between 1-2 minutes with above, it will indicate it exploded at centcomm. this causes an area of the centcomm shuttle dock to look explosion destroyed with dead bodies, depending on the dev of the bomb, and doubles the time taken to send the supply shuttle to the station
  • if over 2 minutes with above, defused, nothing happens.
  • bombs with no dev fail to go off.

announcement will out the name of whoever was detected on the bomb's fingerprints unless the shuttle console is emagged.

Why it's good

some flavor to the supply system for anyone with a traitor's mind.

How it was tested

spawn syndie TTV from nukeops uplink boombox, put on shuttle, set timer to 1 and 2 minutes, make active, send shuttle back.

Changelog

🆑

  • rscadd: Mailing large active explosives back to central comamnd is not recommended. In fact, if bomb squads don't do their job, it could lead to large losses of life. So don't do it. You will NOT.

@D3athrow-Issues D3athrow-Issues added the Content Adds something. Neat! label Feb 6, 2025
@SECBATON-GRIFFON SECBATON-GRIFFON marked this pull request as ready for review February 6, 2025 02:14
@CrazyAmphibian
Copy link
Contributor

sovl

@Eneocho
Copy link
Collaborator

Eneocho commented Feb 7, 2025

announcement will out the name of whoever was detected on the bomb's fingerprints

what if they were wearing gloves or similar?

@Eneocho
Copy link
Collaborator

Eneocho commented Feb 7, 2025

It could also have some gameplay ramifications, like slower cargo requests (4m instead of 2?) if it explodes on centcomm, cause now they have to route the requests through another station first.

@CrazyAmphibian
Copy link
Contributor

It could also have some gameplay ramifications, like slower cargo requests (4m instead of 2?) if it explodes on centcomm, cause now they have to route the requests through another station first.

chance for centcomm to send the bomb back and blow up cargo

@SECBATON-GRIFFON SECBATON-GRIFFON changed the title Mailing malicious stuff back on supply shuttles now gives unique centcomm announcements and appearance at roundend Mailing malicious stuff back on supply shuttles now delays send time, gives unique centcomm announcements and appearance at roundend Feb 12, 2025
@SECBATON-GRIFFON
Copy link
Contributor Author

It could also have some gameplay ramifications, like slower cargo requests (4m instead of 2?) if it explodes on centcomm, cause now they have to route the requests through another station first.

added this now due to positive reception

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Content Adds something. Neat!
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants