Looking at a filler will kill a server with WAWLA installed.
psychofad opened this issue ยท 4 comments
When installing WAWLA on the client and server and then looking at a filler that is in operation the server will grind to a halt and become overloaded until you look away for a minute or so. I wrongly assumed that this was a buildcraft issue, but after removing WAWLA on a hunch the server is unaffected when I look at a filler. There are no crash logs as this does not crash the server it simply overloads it (TPS = 0.01) so unfortunately I have nothing to post with this issue. I did test looking at a filler after placing it and this will not trigger the issue. The filler must be operational (tested with clearing land) for this to occur.
Steps to reproduce.
- run a server and client with at least buildcraft, waila and wawla installed
- use markers to mark out a 64x64x64 area to clear (tested clearing mostly stone)
- place filler down and set to clear area
- Supply power to filler.
- look directly at the filler block as the red cubes are flowing out of it
- check server tps
What are we looking at here? Probably a case of syncing the entire NBT tag, which for BC fillers can easily go into a megabyte or two.
Yeah, no problem.
I prefer to only push larger builds, so this change isn't included in any of the downloads on my pages (yet), however given the nature of this issue, I would assume you and your players will want to use the latest change as soon as possible. Here is a build containing this patch for you, feel free to use it yourself, put it on your server, or use in a modpack. Download Link
As @asiekierka suggested, this is likely an issue with NBT being sent to the client from the server. Waila will sync the entire nbt of any tile or entity when looked at, this is so all information displayed is accurate. Within Waila, you register the blocks that you want to cause the sync of nbt data, and then that block and all blocks which extend from that block will also be synced using packets. Unfortunately my mod Wawla has a lot of general features that do not pertain to just one block, such as light level, so I register all blocks by default.Fortunately, I don't make use of the generalized nbt syncing right now, so I should be able to remove it.