Bukkit

@shukamu

I lost track it seems. You can of course run the latest dev build and report problems simply, such will help !

@asofold

I might push a couple of builds within the next few hours, most of which will just contain minor fixes or adaptions, unless stated otherwise here (and on the dev pinboard page). Then i will release it on bukkitdev.

For those interested in (admittedly not yet complete nor too much guiding) explanations for globalchat: Dev Pinboard/globalchat

@PhanaticD

morepackets violations in bunches are an indicator of lag, they not necessarily cause lag.

But given lag spikes (wherever they camoe from) the alerts themselves might lead to even more lag, so if you have problems with thta occuring you should turn off some logging for lower violation levels for things like morepackets. (especially file or console logging icf = ingame console file, in many cases one would suffice, but only adapt it for the frequently occurring checks)

@chrishillz I am sure that such will happen with time - probably we can even provide a config switch which one sets while deleting all other entries to generate the normal/strict/whatever configs.
I have been thinking of globalchat - the easiest default config is to keep the checks disabled :) but there are some options to balance it and i will give simple advice on the config page once ready. Also i had in mind of writing a simulator for chat to test out settings automatically. For the moment i would rather say to just adjust the weight for globalchat if it is too slack in your oppinion and if you have trouble with certain kind of trash/spam i might give advice on how to tackle, if possible with the current implementation.

@xXSshadowXx

That seems to happen depending on browser/security settings due to redirection or whatever - try this one: http://www.nocheatplus.org:8080/job/NoCheatPlus/

@LordKainzo

Yes, though most seems to come from nolagg tasks, which seem to be chunk generation. There are some small/medium peaks though and also one time an extreme peak like almost 20 ms from player move, yet. Difficult to find areason, but maybe i will see later.

@chrishillz

I wil add documentation soon. globalchat records some scoring for messages over a period of 30 seconds roughly. Thus it aims at the more medium term chat spam/annoyance. Rather than just recoridng chat frequency in, it assigns a score to each message and records that over time, trying to give annoyances more weight, such as upper case, repetition of words or parts of words. Older message scores count less than new ones.

The message score consists of some simple basic checks like comparing message length to word lengths and letters vs. special characters and uppercase, which can make message count roughly up to 3 times at most, plus the by default deactivated extended checks in the player and global sections. The global checks are fed with data from all players the player checks are using data from each player individually. You might not need to activate both player and global. The words check counts frequency of whole words and assigns a score if words get repeated more frequently, the prefixes check assigns a score based on word prefixes being repeated (writing hello and then hell quickly will get some score). Similarity will check recently used words for similarity similar to the nopwnage check, just with many words, it is the heaviest in terms of runtime used. I will make a page for details. You can see the effect of settings with setting "globalchat: ... debug: true" to log scores to the console but probably it is better to wait for the page.

Build number 74 adds more uncertainty by introducing fixes to asynchronous actions execution, which also make the chat handling much more direct on violations (no waiting for the main thread anymore).

Who feels uncomfortable about the "dev" nature of 73/74,
should stay with build number 72.

@LordKainzo

That would be great!

@LordKainzo

• This did not happen with the check deactivated?
• Are there also no entries like "moved too quickly" in the logs (i have to ask that:))?

Could be another check resetting though (survivalfly).

@LordKainzo

Set the cancel level higher. That will allow couple more packets but not deactivate the check, for instance: actions: vl> 4 log:morepackets:10:10:f cancel vl>100 log:morepackets:15:20:f cancel

If 4 or more like 8 is the right value is up to you, but these actions would prevent cancelling for just occasional spikes.

Do you have any data/indication for that NoCheatPlus is causing lag spikes (not that i consider it impossible, but it would help to know something more specific...)?

It is possible to reduce the moving processing by some percentage, either at the cost of fly detection accuracy or at the cost of tolerance of the nofall check (running down full-block-stairs for instance). (Try the actions first, if necessary ask back, maybe.)