-
-
Notifications
You must be signed in to change notification settings - Fork 163
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
Unusual animal size-variance on Paper server #1335
Comments
what is in your BetterAI config? the only way for this kind of thing to happen is either if it’s configured to have extreme variances, or something else on the server had already applied variance multipliers that are multiplying the ones set by craftbook |
|
It seems that the older the entity is, the more repeated modifiers there are. For an entity 37500 ticks old there are 11 modifiers, an entity 925000 ticks old has 40-50 of them. Although, I'm not sure there is a correlation since I've been able to find 100000 ticks old entities with hundreds of modifiers. I can 100% confirm this is CraftBook related since only entities listed for variance in config are affected. |
The modifiers in your screenshot are not the ones added by CraftBook, it uses a size_variance and size_variance_breeding tag, such as can be seen in this video- https://x.com/the_me4502/status/1800491075884478902?s=46&t=9fkuzVwR2af-no0wwGig9g if the tag is initially being added by CraftBook, then something else is merging that data into the generic scale tag and removing CraftBook’s tag- hence why it’d be getting added multiple times |
CraftBook Version
5.0.0-SNAPSHOT+4863-9cb04b6
Platform Version
Paper version 1.21.1-16-master@bf5852a (2024-08-16T07:29:16Z) (Implementing API version 1.21.1-R0.1-SNAPSHOT)
Confirmations
Bug Description
Animals suddenly became gigantic or miniature - possibly because of animal scale variance applied by CraftBook5 retroactively/incorrectly?
Expected Behavior
Normal-sized animals with scale variance
Reproduction Steps
Anything Else?
No response
The text was updated successfully, but these errors were encountered: