Console spamming STDOUT messages

[drag0n1zed]

Whenever the chunkloading block moves to a new chunk, console spams a LOT of STDOUT messages:
[14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 27 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 27 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 27 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 27 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 27 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 27 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:40] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:42] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:42] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:42] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:42] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:42] [Server thread/INFO]: [STDOUT]: Forcing 28 17 [14:45:42] [Server thread/INFO]: [STDOUT]: Forcing 28 17
This is taking up a lot of storage.

[thebrightspark]

I've come here about this too... this console spam is ridiculous. Please at least put these kinds of "debug" logs behind a config option, and also consider using SLF4J as your logger instead of just printing to the standard output.

Line in question:

CreateChunkloading/fabric/src/main/java/org/embeddedt/createchunkloading/fabric/ExampleExpectPlatformImpl.java

Line 28 in a2e9625

System.out.println("Forcing " + chunkX + " " + chunkZ);