-
Notifications
You must be signed in to change notification settings - Fork 17
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
in_tag Damage condition doesn't exist (1.20 1.10.0.5) #414
Comments
Looks like the condition type was created, but simply not registered. |
Will fix next update, thanks for looking into it. |
I am having the same issue for origins:type as well (I haven't looked through the code but I am getting the exact same error as when using in_tag) any idea when this will be fixed? |
I don't remember an |
https://origins.readthedocs.io/en/latest/types/damage_condition_types/type/ |
This damage condition type was added after Origins 1.10, and is 1.20.2+ only on Fabric. |
Trying to use this damage condition at all results in the condition failing to load with
Unknown registry key: origins:in_tag
This feature exists in 1.10.0 for Origins Fabric.
Looking at the condition/damage package in Apoli Forge, it looks like this was just never added.I am blind, but for some reason I am getting this error.
The text was updated successfully, but these errors were encountered: