You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently Trident Boost is a flat adjustment to trident boosting.
Can we add an option in Trident Boost to ignore depth strider to fix the below bug where having depth strider reduces the range of Riptide? I think this would be a very easy one to add as there are a few different mods that do this. One is listed below for reference. I would rather have this one setting in Trident Boost vs running a mod that fixes a bunch of different things I may not need.
https://modrinth.com/mod/tiefix/ MC-136249 Depth strider decreases Riptide's launching effect when underwater
Fix: Ignore depth strider's increased drag while using riptide
Before submitting a suggestion
This feature doesn't already exist in the client. (I have checked every module and their settings on the latest dev build)
This wasn't already suggested. (I have searched suggestions on GitHub and read the FAQ)
The text was updated successfully, but these errors were encountered:
Describe the feature
Currently Trident Boost is a flat adjustment to trident boosting.
Can we add an option in Trident Boost to ignore depth strider to fix the below bug where having depth strider reduces the range of Riptide? I think this would be a very easy one to add as there are a few different mods that do this. One is listed below for reference. I would rather have this one setting in Trident Boost vs running a mod that fixes a bunch of different things I may not need.
https://modrinth.com/mod/tiefix/
MC-136249 Depth strider decreases Riptide's launching effect when underwater
Fix: Ignore depth strider's increased drag while using riptide
Before submitting a suggestion
This feature doesn't already exist in the client. (I have checked every module and their settings on the latest dev build)
This wasn't already suggested. (I have searched suggestions on GitHub and read the FAQ)
The text was updated successfully, but these errors were encountered: