You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When two (or more) tiny planet blocks are placed near one another, a mana burst entering the range of the two always orbits one of the two arbitrarily. This might be considered not a bug, but I would say it's not expected or useful.
Looking at the code, it's clear that this happens because one of the tile entities ticks before the other, snatching all bursts in range. It would be interesting to make a burst orbit the nearest tiny planet in range, so a burst could actually swap between two as the orbit expands. But just making the burst orbit only the tiny planet it comes in range of first would be more useful and expected.
Steps to reproduce
Place two tiny planets within ~5 blocks of each other
Place 2 pulse mana spreaders, one pointing to each tiny planet
Give the spreaders mana and fire them
Both pulses will orbit only one of the tiny planets
Other information
No response
The text was updated successfully, but these errors were encountered:
Mod loader
Forge
Minecraft version
1.16.5
Botania version
1.16.5-420.1
Modloader version
36.2.22
Modpack info
No response
The latest.log file
https://pastebin.com/ei8DZcD7
Issue description
When two (or more) tiny planet blocks are placed near one another, a mana burst entering the range of the two always orbits one of the two arbitrarily. This might be considered not a bug, but I would say it's not expected or useful.
Looking at the code, it's clear that this happens because one of the tile entities ticks before the other, snatching all bursts in range. It would be interesting to make a burst orbit the nearest tiny planet in range, so a burst could actually swap between two as the orbit expands. But just making the burst orbit only the tiny planet it comes in range of first would be more useful and expected.
Steps to reproduce
Other information
No response
The text was updated successfully, but these errors were encountered: