Allows servers to prevent chickens from laying eggs by setting EggLayTime to -1#12247
Closed
brickmonster wants to merge 1 commit into
Closed
Allows servers to prevent chickens from laying eggs by setting EggLayTime to -1#12247brickmonster wants to merge 1 commit into
brickmonster wants to merge 1 commit into
Conversation
Member
|
I'm not sure I like changing the vanilla behavior of that value. Server's can just set it to max int, which is like 3.5 years of uptime or whatever, of if we really want a thing to prevent it, I'd rather it be a separate field that we add. |
Member
|
Agreed with above, just honestly set it to a big number. |
Contributor
Author
|
It could pause at max int instead, making the setter's intent match the behaviour. Otherwise that's fine by me, feel free to close. |
Member
|
Yeah, gonna close this. Just in general with alot of MC related fields like this, setting it to a big number is just fine. Ty for ur contribution, however. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was surprised that NoAI:1 still causes eggs to be laid, but is a more flexible solution for servers that want both as -1 is never normally reached.
-1 prevents ticking.
0 works as before for instant egg lay.
Try with
/data merge entity @n[type=chicken] {EggLayTime:-1}