Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Random ticks are cached as disabled when blocks are made oxidizable after being registered #4226

Open
haykam821 opened this issue Nov 14, 2024 · 0 comments
Open

Random ticks are cached as disabled when blocks are made oxidizable after being registered #4226

haykam821 opened this issue Nov 14, 2024 · 0 comments

Comments

@haykam821
Copy link
Contributor

A block registered and then added to the oxidizable blocks map using OxidizableBlockRegistry will never randomly tick, because the random tick boolean, which is computed based on the oxidizable blocks map, will be cached upon block registration.

Refer to this Discord message for the original context.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@haykam821