Well I know that println is useful for debuging but having things like :
"[13:06:06] [Server thread/INFO] [STDOUT] : [atm.bloodworkxgaming.actuallyaddon.blocks.advancedreconstructor.TileAdvancedReconstructor:writeClientDataToNBT:178]: energy changed [13:06:06]"
spamming the console each time the advanced reconstructor do a thing or :
"[CommonPool-worker-2/INFO] [STDOUT]: [atm.bloodworkxgaming.bloodyLib.networking.PacketHandler$sendToAllAround$1:doResume:37]: Sending to all around at pos BlockPos{x=9960, y=90, z=9812}"
each time a packet is send is a bit disturbing.
Perhaps you can add a config option to enable/disable debuging messages or just comment those lines when you compile the mod.
Thanks anyway for doing this mod, the advanced recostructor is very useful.
Well I know that println is useful for debuging but having things like :
"[13:06:06] [Server thread/INFO] [STDOUT] : [atm.bloodworkxgaming.actuallyaddon.blocks.advancedreconstructor.TileAdvancedReconstructor:writeClientDataToNBT:178]: energy changed [13:06:06]"
spamming the console each time the advanced reconstructor do a thing or :
"[CommonPool-worker-2/INFO] [STDOUT]: [atm.bloodworkxgaming.bloodyLib.networking.PacketHandler$sendToAllAround$1:doResume:37]: Sending to all around at pos BlockPos{x=9960, y=90, z=9812}"
each time a packet is send is a bit disturbing. Perhaps you can add a config option to enable/disable debuging messages or just comment those lines when you compile the mod.
Thanks anyway for doing this mod, the advanced recostructor is very useful.