Severely range-limited brush activation in builds 267 and 269.
Selkit opened this issue ยท 4 comments
After recently updating mc.doridian.de to 1.7.2, we've discovered that Voxelsniper no longer operates within the expected range. Brushes do behave as expected, but only when you're within the usual Minecraft interaction range for a block (IE: The usual "edit this block" highlight has appeared and you could otherwise break/place by hand). Edits do spill over well outside of the vanilla-Minecraft edit range, so I don't believe the issue stems from any form of no-cheat conflict preventing longer range block edits (I can quite blissfully entomb myself in 30-block ball brushes, but only if I stick my face against a surface first)
The problem builds are 267 and 269, and multiple users on the server are reporting this problem, independent of their own personal hardware/OS choices. The server itself is running a gently-modified CraftBukkit, https://github.com/Doridian/CraftBukkitPlusPlus, though no edits have been made to Bukkit that have not played nice with VoxelSniper in past; We've been running it for about two years now with similar edits in place, and have only ported previous functionality forward. Further relevant details for troubleshooting:
- VS range is not enabled, and has been toggled on and off to determine if that's the cause.
- Client restarted, system rebooted. No effect. Happens on all systems.
- Vanilla MC client used. The server's custom client is not currently updated for 1.7.2
- Build 267 and 269 both tried.
- Configs from previous builds wiped in case of conflicting settings. Made no difference.
- Server restarted post-installation.
- Server is running 64-bit Debian install. Same server config as 1.6.4 and prior working versions of VS.
I'm at a loss for anything further to try server and clientside. Halp!
Can confirm that this issue exists. As those builds are still untested, this was almost to be expected. I'll look into it.
Ok done some research. jnks269 should be affected. jnks267 should be still fine. I'm going to revert some changes made to the code, that caused this issue. Essentially the Bukkit API doing something stupid.