-
-
Notifications
You must be signed in to change notification settings - Fork 493
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
feat: Slowness NoSlow #4888
base: nextgen
Are you sure you want to change the base?
feat: Slowness NoSlow #4888
Conversation
player.attributes.getCustomInstance(EntityAttributes.GENERIC_MOVEMENT_SPEED)?.updateModifier( | ||
EntityAttributeModifier( | ||
Identifier.of("effect.slowness"), | ||
-multiplier * (slowness + 1.0), | ||
EntityAttributeModifier.Operation.ADD_MULTIPLIED_TOTAL | ||
) | ||
) |
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.
I don't like the idea of editing the effect like that. It should really hook it where it's applied, I guess?
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.
but then we can't modify pre existing effects
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.
No, I mean where it applies the effect. Not where the effect is applied.
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.
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.
Yes, then fix that?
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.
the reason this does nothing is because the attribute is applied by the server and not the client, we would have to modify the attribute when we receive the attribute packet, which as I said before, won't let us disable this, or modify the multiplier after the effect is applied
No description provided.