Bukkit

@Zidkon

No, it doesn't. I wanted to implement that, but then I read that Notch wants to increase the attack distance in Minecraft 1.0 (which will probably be released in a week), so I won't bother doing that now and wait what Notch/Mojang does.

@darkcloud784

Can you give an example of such a skill that won't work? That plugin has many dozens of those things. I already made NoCheat compatible with the "quicken" skill (I believe it's called like that) of the latest Heroes plugin version. So updating your version of Heroes and NoCheat may fix that, if that's your problem.

@Schlumpf9

I've updated my warning about PermissionsEx in the text above and the "Permissions" section.

@qazzi

And do you get any error messages? You are editing the "config.txt", right?

I've been rewriting big parts of NoCheat (again) to reduce the work I'll have to do in future. Those changes need testing, therefore it'll take some time for me to get out a new version of NoCheat. You'll probably have to wait for a 1.9 compatible version until bukkit "officially" releases an RB for that.

@EVIL0033

If you can tell me what the ".lag" command does, I can tell you if I can fix it. Alternatively, send me a download link to the client via PM and I'll take a look myself.

@efstajas

"derp.derp.*" isn't part of the superperms specification (intentionally), that's what parent-child relations are for, which are also much more flexible than "derp.derp.*" - but anyway, I'm not satisfied with the "fixed" version of PermissionsEx. Here is why:

I wrote today a small plugin that tests the performance of "SuperPerms" permissions plugins by doing lots of "player.hasPermission(...)" in a controlled environment with various patterns of assigned and unassigned permission nodes. It will then tell you how long (on average) the lookup of a permission took. Here are the results for

PermissionsEx 1.15:

layer11: 346 ns layer21: 363 ns layer31: 341 ns layer41: 355 ns

layer12: 148 ns layer22: 152 ns layer32: 151 ns layer42: 152 ns

layer13: 147 ns layer23: 150 ns layer33: 153 ns layer43: 149 ns

layer14: 359 ns layer24: 149 ns layer34: 152 ns layer44: 152 ns

layer15: 348 ns layer25: 346 ns layer35: 146 ns layer45: 151 ns

layer16: 349 ns layer26: 349 ns layer36: 343 ns layer46: 151 ns

undefi1: 148 ns undefi2: 152 ns

Time for random tests: 255 ns.

PermissionsEx 1.16

layer11: 853 ns layer21: 1923 ns layer31: 2746 ns layer41: 3669 ns

layer12: 463 ns layer22: 454 ns layer32: 454 ns layer42: 472 ns

layer13: 473 ns layer23: 1095 ns layer33: 1646 ns layer43: 2257 ns

layer14: 855 ns layer24: 456 ns layer34: 1058 ns layer44: 1631 ns

layer15: 844 ns layer25: 1813 ns layer35: 473 ns layer45: 1069 ns

layer16: 845 ns layer26: 1800 ns layer36: 2698 ns layer46: 462 ns

undefi1: 501 ns undefi2: 667 ns

Time for random tests: 1246 ns.

As you can see, the new version is about 5 times slower than the old version, for some permission nodes (e.g "layer41") more than 10 times slower. PermissionsEx butchers the SuperPerms system with its new version, which will result in less performance of all plugins that do frequent "player.hasPermission(...)" calls.

@qazzi

Do you get any error messages on the console? What program do you use to edit the config files?

@deleted_6835265

It has always been like that. There is no way to differentiate between real sneaking and what "HeroSneak" does. You can mitigate that problem by setting "moving.runfly.checksneaking = false" in the config.txt of NoCheat.

@pynn100

It does not support Permission 2/3. Only plugins that support "SuperPerms" will work with NoCheat. By default NoCheat will fall back to "OP has permission, normal player doesn't" logic.

@Bikkel007

Same as above. If you use Permissions 2/3, those are not supported and have been dead for months now. They are no longer developed any further and you should think about switching to one of the more active plugins like bPermissions, Essentials GroupManager, PermissionsBukkit or PermissionsEx.

@don4of4

It counts time and number of events starting from the last time you did "/reload" (or restarted the server). "total" is (roughly) the time beginning from when NoCheat gets the event handed over from CraftBukkit to the time when it gives it back. "relative" is that time divided by the number of "events" that were counted that way, so ultimately total = relative * events. "Total time spent" is just the sum of all these numbers.

People have strange ideas of how long it takes to handle e.g. a playerMove event and fear that NoCheat may eat away all of their servers resources by doing lots of calculations for each event (20 events per player per second is a lot).

I will probably at some point add an additional information about how long the measuring has been going on, to give the "total" times a bit more meaning, maybe make it a "x % of your processors time" or similar.

PS: Measurement is done by calling "System.nanoTime()" twice, at the beginning and the end of each event and calculating the difference.