Skip to content

Conversation

@mikeysaurus
Copy link
Contributor

@mikeysaurus mikeysaurus commented Jan 2, 2026

About the PR

  • increases the default shuttle shuttle.cooldown ccvar from the default of 10 seconds to 60 seconds.
  • creates a new ccvar for the arrival shuttle's FTL cooldown, shuttle.arrivals_ftl_cooldown, defaulting at 10 seconds (to not break the arrivals system).
  • allows game admins to manually override the shuttle's FTL cooldown timer.

Game Admin Notes

For game admins/admemes, you can bypass the FTL cooldown by vvwriting the shuttle grid's server ShuttleComponent, and setting FTLCooldownOverride to a value. This value will reflect the FTL cooldown length for future FTLs (it does not update while the shuttle is already cooling down).

The full command syntax is vvwrite /entity/[uid]/Shuttle/FTLCooldownOverride [value], where a value of 5 would equal 5 seconds.

Why / Balance

The primary goal is to prevent FTL spam to avoid combat encounters, without negatively impacting regular shuttle FTLing. At the original value of 10s, this both felt bad for attackers attempting to board a shuttle, as well as (in my opinion) feels excessively NRP.

Technical details

In doing this, I also had to breakout the shuttle.cooldown update to also have a new ccvar, shuttle.arrivals_ftl_cooldown, so that the Arrivals shuttle does not get affected by this change. I believe this is the only edge case that needs to be accounted for.

Media

I don't think this needs a video, but I can make one if requested.

Requirements

Breaking changes

Two changes have been made to server CCVars.Shuttle.cs's - an update to shuttle.cooldown and the introduction of shuttle.arrivals_ftl_cooldown.

  • shuttle.cooldown default value has been updated from 10 seconds -> 60 seconds. This is the default cooldown on all non-arrivals shuttles.
  • shuttle.arrivals_ftl_cooldown default value has been set to 10 seconds (which was the previous default of shuttle.cooldown). This is the default cooldown for only the arrivals shuttle.

If your server has a custom shuttle.cooldown set, make sure that you pick a new shuttle.arrivals_ftl_cooldown variable that will work with the other arrivals variables. Notably, shuttle.arrivals_cooldown needs to be longer than shuttle.arrivals_ftl_cooldown to avoid the cooldown double cycling.

Changelog

🆑

  • tweak: All non-arrivals shuttles are defaulted to have a 60 second cooldown before they can FTL again.
    ADMIN:
  • add: Admins can now vvwrite FTLCooldownOverride to override the FTL Cooldown's timer.

@PJBot PJBot added S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. S: Needs Review Status: Requires additional reviews before being fully accepted. Not to be replaced by S: Approved. size/S Denotes a PR that changes 10-99 lines. labels Jan 2, 2026
@VerinSenpai VerinSenpai added P3: Standard Priority: Default priority for repository items. D3: Low Difficulty: Some codebase knowledge required. T: Balance Change Type: Balance changes through direct value changes, or changes to mechanics that affect it A: Combat Area: Combat features and changes, balancing, feel and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Jan 2, 2026
@PJBot PJBot added S: Awaiting Changes Status: Changes are required before another review can happen and removed S: Needs Review Status: Requires additional reviews before being fully accepted. Not to be replaced by S: Approved. labels Jan 7, 2026
@ArtisticRoomba
Copy link
Member

please read our pull request conventions on changelogs

@mikeysaurus
Copy link
Contributor Author

please read our pull request conventions on changelogs

Thanks, the changelog has been updated with the ADMIN tag

@PJBot PJBot added S: Needs Review Status: Requires additional reviews before being fully accepted. Not to be replaced by S: Approved. and removed S: Awaiting Changes Status: Changes are required before another review can happen labels Jan 9, 2026
@PJBot PJBot added S: Awaiting Changes Status: Changes are required before another review can happen and removed S: Needs Review Status: Requires additional reviews before being fully accepted. Not to be replaced by S: Approved. labels Jan 9, 2026
@PJBot PJBot added S: Needs Review Status: Requires additional reviews before being fully accepted. Not to be replaced by S: Approved. and removed S: Awaiting Changes Status: Changes are required before another review can happen labels Jan 9, 2026
Copy link
Member

@beck-thompson beck-thompson left a comment

Choose a reason for hiding this comment

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

looks good! Thanks for the PR. I'll ask some other people about the cooldown increase

@PJBot PJBot added the S: Approved Status: Reviewed and approved by at least one maintainer; a PR may require another approval. label Jan 9, 2026
@beck-thompson
Copy link
Member

looks like people like this! Thanks for the pr

@beck-thompson beck-thompson added this pull request to the merge queue Jan 9, 2026
Merged via the queue into space-wizards:master with commit ec02400 Jan 9, 2026
10 checks passed
@mikeysaurus mikeysaurus deleted the increase-ftl-cooldown branch January 9, 2026 08:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A: Combat Area: Combat features and changes, balancing, feel D3: Low Difficulty: Some codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Approved Status: Reviewed and approved by at least one maintainer; a PR may require another approval. S: Needs Review Status: Requires additional reviews before being fully accepted. Not to be replaced by S: Approved. size/S Denotes a PR that changes 10-99 lines. T: Balance Change Type: Balance changes through direct value changes, or changes to mechanics that affect it

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants