Jump to content

Recommended Posts

Posted (edited)

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 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

Posted

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

Posted (edited)

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 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.

Posted (edited)

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 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.

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



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • Looks like I've figured it out, after entirely too much time wasted on trial-and-error.   The solution was to create /resources/data/minecraft/ and place the tags under there, rather than the mod's data directory. I also needed to add  "replace": false, to the JSON files under /resources/data/minecraft/tags/block/ -> needs_stone_tool.json and mineable/pickaxe.json.   I cannot overstate how dumb this is. I don't think developers should be needing to create additive Minecraft subdirectories for files that belong to a mod. These properties should belong to the block properties anyway, since we're specifying that a tool is required... we should be specifying what that tool is in the same place. (I'm so glad I came back to this mess!) Anyway, it is fixed. Hopefully this helps some poor unsuspecting newbie somewhere down the road.
    • I downloaded Forgematice, moved the file to the mods folder, but after starting Minecraft it does not detect any modifications, I need help
    • Upon registering a new account on here, there's a simple security question. Something along the lines of "name a tool you can craft in vanilla Minecraft" and "name a weapon you can craft in vanilla Minecraft". I answered these with answers that are correct. Yet I'm told I "didn't pass the security check". This happens with every answer to every question. If you can't craft a pickaxe, or use a sword as a weapon in vanilla Minecraft then you and I must be playing a totally different game!!
    • Hello, and happy new year! I've returned to modding while on break from work, and cannot make heads or tails of the method for setting the correct tool for breaking a custom block. This should be a simple affair, but after digging through the vanilla files, all I could find was  assets/data/minecraft/tags/block/mineable/pickaxe.json (and axe, hoe, shovel). So I figured this must be how they're specifying the tool for each block. Yet, after implementing a similar file in my own data folder, it still doesn't work. Plus, this doesn't address the issue of specifying what level of tool is required (wood/stone/iron, etc).   So, please... how should this be being done, properly? And could it be done through the Java code rather than JSON files, without overriding functions for block breaking? I'm either missing something obvious, or -- as is more likely the case -- this is just far more convoluted than it ought to be, for something that should just be a field or two in the Block Properties.
    • and this forge error, is just for forge 1.19.2
  • Topics

×
×
  • Create New...

Important Information

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