Jump to content

Small additions to the logs, potentially large benefits for troubleshooting


Recommended Posts

Posted

As it is, when troubleshooting other people's problems it's sometimes difficult to tell if two, or more, logs actually come from the same (presumably failed) Minecraft run which tends to cause confusion both for the users asking for help and for those trying to help them.

 

Information that would, in some cases, be invaluable to have in every log (latest, debug and if applicable, the crash-log):

 

Full system time and date. (already present in crash log but not latest nor debug)

The full path of the root-minecraft folder of the current instance and at least the relative paths to each sub-folder Forge looks in for various files. (that way you would never have to assume that files are located where you expect them to be).

 

 

 

 

Posted

Full system time and date:

date is redundant IMO, but it's already there:

[11Mar2019 16:36:24.841] [main/INFO] [cpw.mods.modlauncher.Launcher/MODLAUNCHER]: ModLauncher starting: java version 9.0.1

 

 

Folder paths:
 

[11Mar2019 16:36:25.169] [main/DEBUG] [net.minecraftforge.fml.loading.FMLPaths/CORE]: Path GAMEDIR is Z:\Projects\Forge\Forge_113\projects\forge\run
[11Mar2019 16:36:25.170] [main/DEBUG] [net.minecraftforge.fml.loading.FMLPaths/CORE]: Path MODSDIR is Z:\Projects\Forge\Forge_113\projects\forge\run\mods
[11Mar2019 16:36:25.171] [main/DEBUG] [net.minecraftforge.fml.loading.FMLPaths/CORE]: Path CONFIGDIR is Z:\Projects\Forge\Forge_113\projects\forge\run\config

 

All the information is there if you look.

I do Forge for free, however the servers to run it arn't free, so anything is appreciated.
Consider supporting the team on Patreon

Posted

I guess I should have been more specific and included "for all supported versions of Forge" ?

 

 

However, I hadn't noticed the changes to logging in 1.13 so went to check it out and found that logging appears to be broken with the vanillanative Windows launcher (everything default and freshly installed, no mods). latest.log appears to be using old/vanilla formatting and debug.log isn't created at all. The launcher-log.txt file contains mostly vanilla log spam and only some latest.log loggings (no debug) from Forge.

This is probably Mojang's fault (it wouldn't be the first time their launcher breaks logging...)

 

Logging on a dedicated 1.13 server does work in that both latest.log and debug.log (20k lines after just loading an empty modless world...holy crap!) are created and properly formatted but there's no logging at all in the server GUI console (not that anyone actually cares about the server GUI?).

 

 

 

 

 

 

 

 

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.