Posted December 3, 20222 yr Hi, I am trying to help a modder to pin down an issue that's happening on my system and I am trying to figure out how to set the log level of forge file logging to debug. My attempts at googling and using the usual log4j settings have failed. I do not have access to the source code of the mod, so I need to set the log level on the command line. Edited December 3, 20222 yr by Two My Mods New Dawn - A completely new terrain engine for Minecraft TwoTility - Blocks and Items for a better Minecraft TwoGraves - Keeps your items safe on death
December 5, 20222 yr Basically, add '-Dforge.logging.console.level=debug -Dforge.logging.markers=REGISTRIES' to your JVM arguments in your game profile.
December 5, 20222 yr Author Thank you, but this doesn't actually change anything about the log output. I also tried to set the file logger to debug, but again: no change in the log output. My Mods New Dawn - A completely new terrain engine for Minecraft TwoTility - Blocks and Items for a better Minecraft TwoGraves - Keeps your items safe on death
December 5, 20222 yr 1 hour ago, Two said: Thank you, but this doesn't actually change anything about the log output. I also tried to set the file logger to debug, but again: no change in the log output. Did you check the debug.log in the logs folder?
December 7, 20222 yr Author There is no debug log in the logs folder. My Mods New Dawn - A completely new terrain engine for Minecraft TwoTility - Blocks and Items for a better Minecraft TwoGraves - Keeps your items safe on death
December 7, 20222 yr If you are using curseforge, you need to enable the forge debug.log in its settings. Otherwise, it's likely something you are doing when trying to change the log configuration is incorrect and you have broken the logging. Since you don't say what you have actually done, it's impossible to help further. Forge's debug logging is enabled by default, when launchers don't elect to turn it off. Edited December 7, 20222 yr by warjort Boilerplate: If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one. If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install Large files should be posted to a file sharing site like https://gist.github.com You should also read the support forum sticky post.
December 8, 20222 yr Author I was setting the debug defines on the commandline used to start Minecraft in the Minecraft launcher as ChampionAsh535 suggested, this had zero effect. However enabling debugging in Curseforge did it. I have no idea what Curse is doing to suppress the commandlines, but if running with the Curseforge Launcher using that specific setting seems to be the only way to activate debug logs. Which is a bit odd, because it should listen to the commandline settings, especially if enforcing something like a log4j config file, but it is not. Thanks for the help! Edited December 8, 20222 yr by Two My Mods New Dawn - A completely new terrain engine for Minecraft TwoTility - Blocks and Items for a better Minecraft TwoGraves - Keeps your items safe on death
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.