Core mod initialization logging is neither qualified nor saved
ChloeDawn opened this issue ยท 3 comments
ItemPhysic version: v1.4.14_mc1.16.4
CreativeCore version: v2.0.10_mc1.16.4
Forge version: 1.16.5-36.0.0 (can also be produced on 1.16.4-35.1.37)
The following is printed raw to the console with no timestamps or logger name/context
Init CreativeCore coremods ...
Init ItemPhysic coremods ...
These messages are also not printed to the latest.log
file
There is also
[pool-3-thread-1/INFO] [ne.mi.co.Co.itemphysic/COREMODLOG]: start
Which is printed to latest.log
, but is a fairly redundant message
This was reproduced with only ItemPhysic and CreativeCore present in a MultiMC instance
Why exactly is this a problem? Not sure if it's even possible to properly log something as a core mod. This is just a little help for me.
ASMAPI has a log
method that is scoped to your coremod context