Is there a way to disable the Forge outputs on console?

[American2050]

Is there any way to disable the:

 

[Client thread/WARN]:

[Client thread/INFO]:

[Client thread/ERROR]:

 

And other Console outputs during a pack launch?

[XFactHD]

Why do you want to disable them?

[Draco18s]

Can: almost certainly yes, but using Reflection/ASM

Should: absolutely fucking not, hiding stack traces (and other info lines) that Forge produces is not kosher

[American2050]

Can: almost certainly yes, but using Reflection/ASM

Should: absolutely fucking not, hiding stack traces (and other info lines) that Forge produces is not kosher

Wont those still be on the .log file? Or maybe a way to make them dissapear from Console, and make them only exist on the .log files for those that need it.

[American2050]

Why do you want to disable them?

To reduce Console spam

[Draco18s]

There's already a JMV run flag to set an output level.

I don't remember what it is, though.

[LexManos]

Can: almost certainly yes, but using Reflection/ASM

no hacks and ASM needed just edit the log4j confit

 

However console spam shouldn't be a issue for you so there is still no reason to.

[American2050]

Can: almost certainly yes, but using Reflection/ASM

no hacks and ASM needed just edit the log4j confit

 

However console spam shouldn't be a issue for you so there is still no reason to.

Well, on a pack with close to 100 Mods it get's kinda messy all the information shown there. I know it's not a big issue, it's just something personal, I never liked that.

 

Gonna take a look on that about Log4J but I don't think that's something I can get working on a ModPack distribution right? That would be a way to reduce the console outputs just locally?

[diesieben07]

If mods put out useless information on the console that is something that should be talked about with the mod author.

[American2050]

If mods put out useless information on the console that is something that should be talked about with the mod author.

 

I'm on that already, but it's a long journey, specially when a lot of the mods are still in Alpha or Beta stages. Having an option on Forge itself, would be usefull on this cases.

 

My idea is that a final user (Players of X ModPacks) don't really need that information showing on console, I understand it's handy for ModPack developers and in case of crashes, but I like the idea of the final players getting a cleaner interface and a cleaner console, and not a bunch of red lines that will make them think that the pack is loasing with bunch of errors and all that.

[diesieben07]

What I mean is things like this:

 

"ModX preInitializing!!"

"Registering Items!!"

 

Which duplicate what forge does already and which is especially annoying when they are posted on inappropriate logging level (e.g. INFO).

[American2050]

What I mean is things like this:

 

"ModX preInitializing!!"

"Registering Items!!"

 

Which duplicate what forge does already and which is especially annoying when they are posted on inappropriate logging level (e.g. INFO).

Yes for that stuff I already contacte a couple of mod developers. Thanksfully some of them agree that the spam was too much. Like PlaceMod outputing a line for every Schematic loaded on the pack (About 6500 Schematic) used to be on those days.

Now they cleaned the schematics a lot and also added config to disable that outout on the console.

Same with other mods developers showing information like "Config file created" or "found" and stuff like that (Mea culpa, I used to do the same on my mod as I forgot some of those lines from when developing the configs files)

[jabelar]

Can: almost certainly yes, but using Reflection/ASM

no hacks and ASM needed just edit the log4j confit

 

You mean edit the configuration file directly in the Minecraft JAR in your workspace, right? That's what I had to do in the past when I changed the log level, and the pain with that was I had to update it every time I updated Forge. Or did they fix it so you can put your own log4j directly in your project?