Skip to content

Check for lava once per tick - #196

Merged
windcolor-dev merged 6 commits into
Wind-Development:masterfrom
xii69:fix/lava-combust-event
Oct 22, 2026
Merged

windcolor-dev merged 6 commits into
Wind-Development:masterfrom
xii69:fix/lava-combust-event

Conversation

@xii69

@xii69 xii69 commented Oct 13, 2026

Copy link
Copy Markdown
Contributor

What was wrong

Standing in lava could spam EntityCombustByBlockEvent, and the “block that set you on fire” was always null. That’s noisy for plugins and breaks the event contract.

What this changes

Only fire the combust event on first ignition for living entities (fireTicks <= 0). Track lastLavaContact and pass that real lava block into the event. Already-burning entities just refresh fire without re-firing the event.

Why this is needed

Plugins listening to combust-by-block expect a real block and a reasonable fire rate. Spam + null is both a perf annoyance and an API bug.

Testing

LavaCombustTest 4/4; full server suite green; package OK.

Inline Paper combust-once + combuster block rules in burnFromLava.

Co-authored-by: xii69 <[email protected]>
@cursor
cursor Bot force-pushed the fix/lava-combust-event branch from e233240 to a10530b Compare October 14, 2026 21:17
@windcolor-dev windcolor-dev changed the title Fix lava combust event spam and null combuster block Check for lava once per tick Oct 22, 2026
@windcolor-dev
windcolor-dev merged commit 6f527e2 into Wind-Development:master Oct 22, 2026
2 checks passed
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

Successfully merging this pull request may close these issues.

4 participants