-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Block console spam #34
Comments
Note that this is on a modpack. And its not with every block that this happens. Just some (probably odd) modded blocks. I have yet to find a proper one that causes the stacktrace. I'll investigate this further if needed. |
Copy of the error that shows up for me. |
do you have a list of mods you were running when this occurred or even better what block was broken? @OmarWazzan @Whazaaaaa |
Hello,
I'm getting a lot of spam in my console of writes not going well.
Could you implement a simple config for it to not spam this on every .printStackTrace(). Or even better have a seperate logfile where it saves all these logs to use/fix at a later date?
something like:
debugmode=print/log/none
Or something else you can come up with.
Or better yet if you are able to fix why its catching, and thus spamming the console with stacktraces.
Forge: forge-1.12.2-14.23.4.2705-universal
Sponge: spongeforge-1.12.2-2705-7.1.0-BETA-3126
Ashield: AdamantineShield-0.4.1
Log of stacktrace: admanantineshieldstacktrace.txt
Thank you for this plugin!
The text was updated successfully, but these errors were encountered: