Skip to content

Rewrite Dominant Spark transfer#4963

Merged
TheRealWormbo merged 2 commits intoVazkiiMods:1.20.xfrom
NEstoll:fix-sparks
Feb 14, 2026
Merged

Rewrite Dominant Spark transfer#4963
TheRealWormbo merged 2 commits intoVazkiiMods:1.20.xfrom
NEstoll:fix-sparks

Conversation

@NEstoll
Copy link
Contributor

@NEstoll NEstoll commented Feb 13, 2026

Fixes #4833

@williewillus
Copy link
Member

given how sensitive this system has been, it would be nice to have some gametests to assert the correctness of things here

@NEstoll
Copy link
Contributor Author

NEstoll commented Feb 13, 2026

Do you have a definition for what correct would be? Because this PR does change the behavior somewhat

@TheRealWormbo TheRealWormbo merged commit b9d92b0 into VazkiiMods:1.20.x Feb 14, 2026
1 check passed
cjlarose added a commit to cjlarose/Botania that referenced this pull request Feb 15, 2026
The changes in VazkiiMods#4963 generally
fixed behaviors associated with establishing and re-establishing mana
transfers to dominant sparks, but I think introduced an unintended
consequence: it made it possible for dominant sparks to receive
`TRANSFER_RATE` mana every tick from each unaugmented spark in range.

Prior to the change, a dominant spark could receive at most `TRANSFER_RATE`
mana from a single pool per tick. This change restores that behavior.

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

Spark Network seizes up when charging items that drain mana constantly.

3 participants