Bukkit

@horsetears

nocheatplus.command.notify is for toggling with the command. If given, you also do receive notifications.

nocheatplus.notify is just to receive notifications.

If "notify off" shows usage, it means that you don't have the nocheatplus.command.notify permission. Docs might need updating, commands could also use more clear messages.

@Bodyash

I think i scheduled it for doomsday, or vice-versa. It is not often requested, so i suggest you upvote the Corresponding Ticket, and probably get other people to upvote it as well, this might put it on higher priority for us. There are other things on the lists as well and of course severe bugs come first. Things like this and what we were confronted with recently need a lot of testing, potentially - if we don't have enough time, then progress is slower on adding features like this.

So concerning when it might be added i can't promise much, because we have to ensure that 1.7.2 works well. Then we have the fighting checks iteration pending and the documentation still needs updating. Then still an iteration about moving checks is planned, this could fit in there, though i am not mentioning the next major plugin version requiring a full recode for about everything.

@Puremin0rez

File a ticket please, we would want to fix velocity. We do need "ncp version" output and a rough idea of what your plugin does (trampoline is too rough - does it lead to adding velocity repeatedly, what amounts of velocity? Does it trigger "moved too quickly" if exempted from NCP?). A way to help us find a way to fix it would be to provide us with a moving trace (set moving.debug to true, reproduce a couple of times, paste the log - using TestNCP would be even better because it logs a little more but the trace would get us most far).

You could also hook into NCP to exempt the player temporarily and reset with a delayed task, however that does not fix the problem.

@j1752s

Check out our development builds, we are adjusting to 1.7.2 - however there can still be a lot of bugs/problems. Also the CraftBukkit builds should not be trusted to run on a production server unless you have backups and quick reactions.

@MinecrafrGi

Please provide more information, consider filling in a ticket.

We do need:

• Output of the "ncp version" command.
• At least the part of the server log from enabling NCP to the point after enabling all plugins (last ncp startup message).

Could use:

• Full startup log.
• Plugin list (if startup log is not available).

(Please send by PM if not meant public.)

@dotapurex1

Thanks, we will have to go over god modes again. Though it seems that the versions with staying totally passive (lava/water) might be detectable as well, unfortunately the ways to deal damage properly with Bukkit are limited (in fact there is none that accounts for all the enchantments and armor, unless i missed something for a couple of months).

@Magiciangoh

Usually not - typically ncp "lags" when your server lags, but that is another effect. You should however adjust the logging/notification settings to focus on what you need, these create more overhead especially for bigger servers, since they are not done asynchronously (yet). NCP is designed to run "smooth", so it should not create lag spikes on its own, still it is not exactly light-weight.

@Jleeevinnn

To reduce any impact of NCP itself, the first thing to do is to reduce logging as much as possible (e.g. turn off console logging or all file logging), just to have mentioned it.

I don't see your impression backed up by the data, though. On the one hand you present way too few events covered (200k moving events is still about 10 fold too few for a somewhat reliable statement), on the other hand i do not see anything in the data that shows that NCP is taking too much of resources. I rather suspect the number of 60 (in addition to 1.7 hacks) to cause lag rather.

NCP is kicking people periodically ? Do the logs / kick messages indicate that? If your server is lagging anyway, it might happen due to Minecraft accepting moving events from before a teleport, then leading to extreme moves with latency. If that happens a lot, you should set the vl needed for the kick action to something significantly higher (e.g. 10000 instead of 1000). That way players hovering would not get kicked, but overly simplistic moving hacks would still lead to a kick, so the cheater can't create too much server load.

High on the list does not necessarily mean lag... of course you can replace NCP by 3 to 5 "chicken run" or "silly hat" plugins, but they just don't protect against too many things (except maybe boredom).

@Jleeevinnn EDIT: Not sure, but the "lag effect" might be players lagging back repeatedly after moving off spawn or positions just teleported to? In that case we would have the "extrem moves" resulting from latency + Minecraft not being able to drop moving events that were sent by the client before a teleport happend on server side and which arrive before the client received the teleport (see above description to lessen the teleporting by NCP - do note that Minecraft itself could set back the players as well on such occasion).

@dotapurex1

Please test again, but first do "ncp remove PLAYERNAME" and after testing with getting set back one or more times do "ncp info playername" right away - if NCP sets you back, then this will show something which we are interested in.

Also check the server log for "moved to quickly", just to be sure.

As far as i can see the plugin uses velocity + "setAllowFlight", so this should usually be a bug in NCP rather, because we want NCP to process both correctly. You do have a lot of plugins, which might need us to do dig deeper., though.