Being Pulled Blocks Uncuff Doafter. #2269
Open
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.
About the PR
The TryUncuff function now checks if the target is being actively pulled by another entity. If they are, it will prevent them from performing the DoAfter. No other changes in regards to being cuffed.
Port of #2226 from Impstation.
Why / Balance
It's mostly just QoL for Sec and potentially anyone else who would have someone cuffed. Being cuffed kinda suck not gonna lie, but the fact that you have to keep an eye on your cuffed target even when they are actively being pulled around by you is kinda stinky. There is a very low chance that you'll get away with uncuffing in the presence of your capturer anyway, but this just prevents the annoyance of needing to punch or pull around someone cuffed.
Technical details
3 line addition in SharedCuffableSystems.cs, specifically the TryUncuff function, including comments.
Media
2026-01-03.mp4
Requirements
Breaking changes
Changelog
🆑