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.

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

Edgecase in optimizedTNT #1989

Open
cubicmetre opened this issue Aug 29, 2024 · 1 comment
Open

Edgecase in optimizedTNT #1989

cubicmetre opened this issue Aug 29, 2024 · 1 comment

Comments

@cubicmetre
Copy link

With the rule enabled, The first TnT to explode at a position forms a cache of the affected entities within the blast radius and uses that cache for future explosions which occur at the same position within the same tick. However this cache does not account for entities entering the blast radius after the intial cache is created.

For example it is possible for TnT to move into a position, explode, then an entity moves within range after the explosion and is not included in the intitial cache and gets ignored by future explosions at that position.

@Slinel
Copy link

Slinel commented Aug 29, 2024

It is also important to note that the exposure can change while explosion is processing, for example:
explosion can kill an armor stand which instantly triggers a sculk catalyst which instantly sends block updates which instantly closes a trapdoor which changes the exposure for next entity to be processed, this behavior is occasionally useful in cannon tech and cache breaks it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants