Skip to content
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

Specify LogLevel in Config #409

Closed
CyreX541 opened this issue May 12, 2021 · 2 comments · Fixed by #468 · May be fixed by #421
Closed

Specify LogLevel in Config #409

CyreX541 opened this issue May 12, 2021 · 2 comments · Fixed by #468 · May be fixed by #421

Comments

@CyreX541
Copy link

Feature Request

Set LogLevel in Server Config File and / or Docker Environment Variables

Feature Information:

Trimming Output at Console by specifying some kind of LogLevel could be useful.

LogLevel for Instance.

  • Debug: Print as many Infos as collected to the console and / or LogFile
  • Info: Print less Info than Debug Level but still with useful Info
  • Warning: Print less Info than Info Level to console
  • Error: Just print Error Messages to Console e.g. Config Error at Server side

I confirm:

  • [x ] that I have searched for an existing feature request matching the description.
@CyreX541 CyreX541 changed the title LogLevel Specify LogLevel in Config May 12, 2021
@js6pak
Copy link
Member

js6pak commented May 13, 2021

You already kinda can do that, if you use debug build loglevel is Debug, if release then Information, if you use --verbose or --errors-only as command line argument its going to be Verbose or Error respectively.

@iwa
Copy link

iwa commented Nov 16, 2021

would be great to be able to disable anticheat logs, cause even if you disable the anticheat, it stills show up warnings in console and it spams a lot when playing with modded client (cf. screenshot) ://
Screen Shot 2021-11-16 at 22 10 36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants