-
Notifications
You must be signed in to change notification settings - Fork 4.7k
Stunnable New Status and Cleanup #38618
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
Stunnable New Status and Cleanup #38618
Conversation
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
Me when I forget to update my master branch x2 |
|
What the fuck is causing this test fail goddamn |
Content.Shared/Movement/Components/SlowdownStatusEffectComponent.cs
Outdated
Show resolved
Hide resolved
|
Also need remove all yml references to removed old status effects |
|
you can use #38620 |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
|
This pull request has conflicts, please resolve those before we can evaluate the pull request. |
# Conflicts: # Content.Server/Stunnable/Systems/StunOnCollideSystem.cs # Content.Shared/Bed/Sleep/SleepingSystem.cs # Content.Shared/Movement/Systems/MovementModStatusSystem.cs # Content.Shared/Slippery/SlipperySystem.cs # Content.Shared/StatusEffectNew/StatusEffectSystem.Relay.cs # Content.Shared/Stunnable/SharedStunSystem.cs # Resources/Prototypes/Entities/Mobs/Cyborgs/base_borg_chassis.yml # Resources/Prototypes/Entities/Mobs/NPCs/elemental.yml # Resources/Prototypes/Entities/Mobs/NPCs/silicon.yml # Resources/Prototypes/Entities/Mobs/NPCs/simplemob.yml # Resources/Prototypes/Entities/Mobs/Species/base.yml
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Kinda okay but i want to talk about that StunnedStatusEffectComponent.Remove flag.
Other then that - i am pretty much ready to approve :3
Testing is a bit hard, i think. The whole thing can be nice with some admin commands? Not in this PR but in following stuff. I had to change timers on falsh and on vomiting to do my testing, and it worked.
…' into stunnable-new-status-and-cleanup
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yep.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
everything looks good, I didn't notice any errors
|
PR so good i approved twice (somehow) |
Co-authored-by: Princess Cheeseballs <[email protected]> Co-authored-by: pa.pecherskij <[email protected]>
Co-authored-by: Princess Cheeseballs <[email protected]> Co-authored-by: pa.pecherskij <[email protected]>

About the PR
Helps with: #38575
Requires: #38617
Requires: #38660
Project Zero warnings PR basically.
Cleaned up every warning in Stunnable and moved Stun and Knockdown to New Status
Moved SlowedDown to its own system in Movement and updated it to the new status system.
Got rid of a number of miscellaneous warnings in areas I was touching anyways.
Should be compatible with: #36881 (Although I'll have to eat some fat merge conflicts)
Why / Balance
Warnings bad, new status good.
New status good, warnings bad.
Technical details
Media
Requirements
Breaking changes
TrySlowdown and relevant components have been moved to MovementModStatusSystem in the Movement folder.
TrySlowdown has had its refresh bool moved to the end of the component to match how other status effects work.
TrySlowdown has been renamed to TryModMovement.
Changelog
no cl no fun