Skip to content

Its cogging time(again) #4140

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

Closed

Conversation

wraith-54321
Copy link
Collaborator

@wraith-54321 wraith-54321 commented Nov 7, 2024

About The Pull Request

CWC changes, read the CL
Ports tgstation/tgstation#76616, tgstation/tgstation#77500

Why It's Good For The Game

Changelog

🆑 MrMelbert
balance: Clock cultists are given a slowing status effect after warping to the station
add: Anchoring crystals now bend reality the more of them there are
balance: anchoring crystals now lock down the shuttle while active
balance: abscond can only be invoked from marked areas and takes 45 seconds, servant antag info now lists marked areas
balance: vitality sigils no longer create borg shells but shells can be made by on station tinker's caches
balance: the soul vessels given by vitality sigils can now be converted to cogscarab shells
balance: clockwork mobs can now warp to the station but are restricted to marked areas
fix: various clock cult bugs
balance: reduced the maximum amount of cogscarabs from 9 to 6
/:cl:

@Absolucy
Copy link
Member

Absolucy commented Nov 8, 2024

suggestion: completely forbid shuttle recalls or changing alert from Reebe. or perhaps just make comms consoles not work there at all.

@wraith-54321
Copy link
Collaborator Author

wraith-54321 commented Nov 9, 2024

clock cultists are only able to recall one time and then are blocked, also I thought comms consoles did not work off Z level

@destrucktoid
Copy link
Contributor

I feel like 1 minute is far too long. 3 seconds is too short yes but a whole minute is waaaaaay too long. Breaking out of cuffs takes about the same length of time (i think it's 60 seconds for cablecuffs and 90 for handcuffs but i might be wrong). Especially so if it's multiplied by 3 if you aren't in a marked area

Either way, i still think it's far too long. My suggestion would be to make it 10 seconds as that's more than enough time for someone to catch up to you if you are in a chase, 15 seconds if you are dragging someone and double it if you aren't in a marked area.

@github-actions github-actions bot added Merge Conflict DO NOT RENAME THIS LABEL and removed Merge Conflict DO NOT RENAME THIS LABEL labels Jan 21, 2025
Absolucy added a commit that referenced this pull request Feb 19, 2025
…5506)

## About The Pull Request

This ports a minor change from
#4140 - clockwork
slabs no longer shock non-cultists when they're picked up, only if they
try to use it in-hand. Also reduces the shock damage from 25 to 20.

## Why It's Good For The Game

Instantly losing because you accidentally clicked on a clockwork slab
that a cultist dropped during a fight is not fun gameplay, and I'm
certain that could be _abused_ by clockies too.

## Changelog
:cl: Absolucy, wraith-54321
balance: Clockwork slabs no longer shock non-cultists when picked up,
instead shocking them if they try to use it in-hand.
balance: Slightly reduced the damage done by clockwork item shocks from
25 to 20.
/:cl:
Copy link
Contributor

github-actions bot commented Apr 9, 2025

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

Copy link
Contributor

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

Copy link
Contributor

This PR has been inactive for long enough to be automatically marked as stale. This means it is at risk of being auto closed in ~ 7 days, please address any outstanding review items and ensure your PR is finished, if these are all true and you are auto-staled anyway, you need to actively ask maintainers if your PR will be merged. Once you have done any of the previous actions then you should request a maintainer remove the stale label on your PR, to reset the stale timer. If you feel no maintainer will respond in that time, you may wish to close this PR youself, while you seek maintainer comment, as you will then be able to reopen the PR yourself

@github-actions github-actions bot added the Stale label May 13, 2025
@github-actions github-actions bot closed this May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Balance perfectly balanced as all things should be Code: Fix fix da bug Feature: Expansion Some addons for a big new thing Merge Conflict DO NOT RENAME THIS LABEL Stale
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants