Bukkit

@dotapurex1

I don't know yet, what in-game alerts do you get for using the plugin skill?

@FabioWidmer

thx :).

@dotapurex1

This is opposite of what i thought.

There is three main points: 1. Did you try setting the fight.direction.strict flag to false, yet?
2. Did you in addition try to set the fight.reach.reducedistance to 0? This gives kill auras more leverage, but they are still confined to 4.25 distance on server side.
3. For fighting situations with players moving a lot, latency might be a problem: the players are not close enough to hit on server side, but appear so on client side, thus the reach check prevents the hits, because NCP can only see the server side. This will be addressed in the next development iteration.

@FlOppythp

I don't know what you have been trying to see if NCP is there ... assuming you have been using the latest version of NCP available at BukkitDev, i would still like to know what kind of cheats you tried, just chat spamming?

Please be aware that we always need the version of the server (e.g. CraftBukkit) and of NCP in order to be able to judge things. Whenever someone is testing if NCP blocks anything, one has to make sure that the checks are activated for the tester:

• Not be op.
• Not have bypass permissions (e.g. wildcard permission like '*' for GroupManager, PEX and similar).
• (Not be in game-mode for testing anti-fly.)
• (If the config has been changed: is the check enabled at all?)

Can't ask less...

@dotapurex1

I am not quite sure about that analogy, can it be expressed in "block distance"?

What kind of alerts are logged for these cases?

For very-close-combat problems:
This likely is the direction check in the fight-section. Setting the strict flag to false might improve the situation.

@dotapurex1

I don't have enough information. Can you fill in a ticket? ncp version ... does it suddenly appear or has it been like that for longer time ? What kind of pvp situations does this happen for?

@FlOppythp

Of course the plugin works.

Two things to start with:

• Check the server log for errors.
• Check your permissions and op status (don't be op and don't have bypass permissions for testing).

Another question is on what server version you run which version of the plugin, so please also provide the output of the "ncp version" command.

@chris752w

You can register a hook that implements IStats (similar to what TestNCP does). However you might only want to receive violations for which violation handling has not been cancelled by another hook, so you would also implement ILast to ensure your hook is called late (see hooks package). You can register the hook to only receive input for specific check types.

If you want to cancel violation handling (actions) for some reason, then you must not implement IStats, and probably need not implement ILast.

This gives you input about violations for checks that have actions.

@Jleeevinnn

I can't tell. What is your server size / player number? Do you have logging to file/console activated ?

@Mr360zack

An extra plugin would be overkill, since it would receive similar tickets and roughly doubles the work to maintain.

You could start here with your issue: https://github.com/asofold/NCPDocs/blob/master/wiki/configuration/checks%2Fchecks.creole#how-actions-work-an-overview

Configuring NCP to do such is not exactly equivalent to what you want, but can come pretty close. However it needs testing concerning which violation levels are reached without cancelling actions. We can't really test all cases out on ourselves, so you will need to do some balancing, though not cancelling ever means a lot of rampage happening, so we suggest to apply that idea only to checks where you really need it. The next major version of NoCheat(Plus) might contain designs to make such easier, though.

I probably won't bring in too much for Spigot in the near future, especially not for the 1.7 hacks, but i might do some adaptions that will make NCP work at alll. If it helps transition to 1.7.2 CB then it is even better. Developing for the Spigot API might happen with a new design on the next major version, if it is useful or even needed to implement certain features that otherwise would not be possible without a plugin or some magic..

@bukkitCensoresComments

Development build 646 should prevent NCP future crashes on 1.7.x due to LOCKED_CHEST.

@FightManiac

Likely you can not fix "it", but you could fill in a ticket and give us some more information, so we can attempt to find out what "it" is and if/how it can be fixed.

Specifically we need:

• Output of the "ncp verison" command.
• Any kind of log entries you have a bout a player that used the cheat (ingame alert messages, server.log, nocheatplus.log, ...), also the output of "ncp info PLAYERNAME" for a player that just used the cheat, if available. If possible the "ncp info ..." output for a player right before using such cheat would be very useful. Sometimes people can be lured into showing it off to a (seemingly) non-staff player or so.
• What alerts show up at what phase (before/while being invincible, after tp) ?
• More details about what is happening. Is pvp necessary for the exploit, what means "starts flying"... does the player actually fly, what means "tp home". All details you can recall/get for this might help.
• List of plugins would be good for checking for cross plugin issues (pm if not intended to be public).