Beacon no longer needs to be lit in 1.18
DarkYuan opened this issue · 2 comments
While there are config options to change the base radius and step radius, there's no way to make it required to be lit but still have even steps up for range. Vanilla beacon range behavior is [0, 20, 30, 40, 50], but with the config it's only possible to have [10, 20, 30, 40, 50] or [0, 10, 20, 30, 40].
Proposed fix: "base_range" should pertain to a lit beacon, rather than a beacon on the ground with nothing under it, in which case the default config would be 20.
After doing a series of tests I can confirm that there is a bug:
- no base: 10 range ❌
- block above base: 0 range ✅
- 1 level: 20 range ✅
- 2 levels: 30 range ✅
I think that bug has been there ever since the first implementation for MC 1.10 as I never rewrote the range logic
Just pushed a fix: 11eeb11, I'll close once it's released :)
Here we go https://www.curseforge.com/minecraft/mc-mods/magic-feather/files/3885425 (edit: once curseforge has approved it)