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

isolated issues are logged as SEVERE but should be INFO #25

Closed
ZathrasNotTheOne opened this issue Jun 3, 2012 · 3 comments
Closed

isolated issues are logged as SEVERE but should be INFO #25

ZathrasNotTheOne opened this issue Jun 3, 2012 · 3 comments

Comments

@ZathrasNotTheOne
Copy link

When an issue gets logged, it looks like this:
[SEVERE] [AntiCheat] xxxx tried avoid fall damage.
[SEVERE] [AntiCheat] xxxx tried to walk on water.
[SEVERE] [AntiCheat] xxxx tried to break a block of STONE without swinging their arm.

These used to be WARNING and now they are SEVERE, but they really should just be INFO since they are isolated incidents that are often not really problems, but lag induced.

If a player's threat level gets moved up, that's a good WARNING.

SEVERE should be reserved for a major error or perhaps a player being KICKED.

As a server admin, if I see SEVERE, I stop whatever I'm doing to investigate.

Request is to change these to [INFO] messages so admins don't get concerned when they don't need to.

@gravitylow
Copy link
Owner

Confirmed, this was an issue I saw but did not worry about before pushing a release, It's some issue that popped up when I was switching the logger to fix your other issue. I'll investigate.

@ZathrasNotTheOne
Copy link
Author

On server stop...

[SEVERE] [AntiCheat] Disabling AntiCheat v1.2.1

gravitylow added a commit that referenced this issue Jun 9, 2012
@gravitylow
Copy link
Owner

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

No branches or pull requests

2 participants