Disable or reduce Moved too quickly and Moved wrongly spam

Would it be possible to add an option to disable these messages or reduce them? No matter what number I set either of those options to, I get insane spam in the console from it. I've had log files grow into nearly a gigabyte because of how much it's spammed.

Am I missing something, how is everyone dealing with this?

[electronicboy]

Those messages are triggered from players moving in a manner that the server isn't sure is actually legit; This generally falls down to plugins, bad performance (e.g. TPS drops) or players with hacked clients.

I know.

[electronicboy]

The part you're missing, is that people look into those 3 different potential issues and fix them.

It seems highly counterproductive for Paper to add a system to disable messages that are telling you that something is wrong, especially when the server has to take a set of actions that may actually impede the playability to players causing issues such as lagging back.

Because there is no lag, it's at solid 20.0* TPS, there is a relaxed anti cheat plugin. This happens for very few players and not everyone and there are no complaints from anyone about lag or rubberbanding. Those very few players it happens for just happen to spam the console so much it's unusable.

I don't see how an option to disable it for people that don't need it hurts

[electronicboy]

Because it's a message that is there for a reason, that only fires when the server takes an action to limit a players movement due to them making an invalid movement that could potentially crash the server. It's counterproductive to have a patch on the server in order to disable a message that indicates that a player is doing something that the server is having to take an action against in order to potentially keep your server running.

You're more than welcome to add such an option to your own server, or use a plugin/log4j configuration to filter the logs for such a message, however adding an option to disable warning messages of issues you should fix is counterproductive to server owners who should be fixing their servers to prevent the message from firing in the first place, as well as just creates another patch that needs to be maintained with no actual benefit to server owners most likely at the expense of us when we get hit with issues by people who are experiencing such cases, however aren't actually knowing it because they've disabled the messages.

[aikar]

we don't need to add a flag for something that only 1 person would likely use.

These messages do not "hurt".

If you want to get rid of them, you can configure the logger to ignore them.

There are plugins that can do this for you:
https://dev.bukkit.org/projects/consolefilter
https://dev.bukkit.org/projects/logfilter

[reverofevil]

@zetglob

[suresttexas00]

triggered from players moving in a manner that the server isn't sure is actually legit; @electronicboy I get these messages all the time when ever I execute a valid "tp <player> x, y, z". Why doesn't the server know that the movement is from a command it executed??

[18:13:38] [Server thread/INFO]: Teleported SurestTexas00 to 65.5, 69.0, -267.5
[18:13:38] [Server thread/WARN]: SurestTexas00 moved wrongly!

[electronicboy]

That's generally down to the player moving while being teleported and other various fun aspects of teleportation

[suresttexas00]

I TP myself from console (so I know my player client is not moving).. so Again; sounds like a bug. This happens on my vanilla server - and I know this is probably the wrong place for it, but you guys were the only ones coming close to dealing with the issue at any level.

[aikar]

@suresttexas00 please report the concern to mojang. We are not in a position to rewrite that code.

If the log messages concern you, I linked some plugins that can filter the logs for you.

You can also just run a custom Log4J config thats configured to filter them too.

[suresttexas00]

Yea, sorry to barge in. I really hate dealing with their (mojangs) bug report process. Thanks!

[CosmicCatnap]

PaperMC: Lets make a custom minecraft server that offers something spigot and vanilla can't

User: Can you just turn off this annoying log message that we all know the meaning of and has been the pain point of log management on every minecraft server I have ever ran and by itself would give me a solid reason to use paperMC instead?

PaperMC: no, now go away and never speak of this again.

To say that you can't fix how you wrap logging speaks volumes about either your initiative or the fragility of your implementation...

Seriously, my first thought after reading this was "This must be uncharacteristic of them, they must have been off that day or something" but no, I go to look for other related posts and very consistently you seem to find gray area where you can say "That is minecrafts fault" or "Its the fault of your plugins" or often times "we don't care, and if you do this again you are banned" without context but here is a perfect example of something your platform would be perfect for implementing, something that isn't even minecraft, it could be scripted easily and painlessly without a single line of java and something I was on the edge of my seat head over heels gitty to click on, something that was going to make me switch to this tonight...alas instead I will spend it writing my own wrapper to fix the logs, let me know if you want to pull it in, shouldn't take me more than a few hours -_-

[electronicboy]

That "annoying log message" indicates a potential state which can cause servers to crash, it would be highly counterproductive of us to remove logging messages which can lead us to these issues. it's easy to remove these messages, but at the same point, it makes the burden on us much harder when people start bringing logs to us with critical warnings like these disabled. You're more than welcome to filter out such messages, just do not expect support when you impede our ability to read what is going on in the server.