Bukkit

@HighlifeTTU

I'll definitely make it toggleable anyway, just to be sure. I'll probably call it "aggressiveMode" or something like that, because to get this "nofall" patch to work I'll have to deal fall damage manually to the player, instead of just correcting the fall damage value of the player and letting the server do the actual damage dealing.

@ImJoenemesis

Ok, I tested this now. But for me it works exactly like it should. I used PermissionsEx 1.18 (only the "PermissionsEx.jar", not the "Permissions.jar", because according to changelog that's no longer needed) and no matter which of these 3 I give myself, all 3 allow me to fly:

• nocheat.checks.moving.flying (allows flying according to flying speed limits)
• nocheat.checks.moving.runfly (allows unlimited speed flying)
• nocheat.checks.moving (allows unlimited speed flying and also disables the "morepackets" check).

I've read for some of you that you use ".*" at the end of permissions. Don't do that for NoCheat. NoCheat's permissions are defined without the ".*" at the end. It is already designed such that e.g. "nocheat.checks" means every NoCheat permission that starts with "nocheat.checks".

Especially don't use things like:

• nocheat.checks.moving.flying.*

because that means all permissions starting with "nocheat.checks.moving.flying" but not "nocheat.checks.moving.flying" itself. Therefore it doesn't do anything.

The only things I can say is:

- "Towny" blocks flying - "Factions" may block flying, at least someone told me that some time ago. I never checked if it is true though, so I may be totally wrong here.

@ImJoenemesis

I can't test it now, but I sure will tomorrow. I don't think I changed anything related to permissions when going from 2.xx to 3.0.0 though.

@HighlifeTTU

For the nofall. Yes, I know how that works. But I still try to figure out a way to stop it (easy) without breaking other plugins (hard).

For the block breaking speed. I don't think I'll ever add a check for that because there are too many uncertainties that I can't know of, e.g. maybe a plugin is breaking blocks early for the player or somehow else modifies how long a block breaking takes. But I may add at some point a check that limits how many different blocks can be broken within a specific timeframe. That'd probably do something. Currently I have different priorities, so don't count on getting that anytime soon.

@mrchasez

Version 3.0.2:

- allow to toggle lag warning messages (disabled by default, option "logging.debugmessages" is used to enable them).

@felipepcjr

Without an error message I can't really help you.

NoCheat v.3.0.1:

• Updated the default limit of the fight.speed check from 10 to 15 (you'll have to do that yourself, it will only be done automatically when a new config gets generated)
• Reduced the maximum speed limit when sprinting from 0.4 blocks to 0.35 blocks per step (let's see how that goes)
• Print a warning on the console when NoCheat detects lag and subsequently deactivates some checks (moving.morepackets, fight.speed).
• Really compile with CB 1.1 R3 and not like I accidentially did for 3.0.0 with the yet unfinished CB 1.1 R4 (shouldn't make a difference, but "rather safe than sorry")

http://dev.bukkit.org/server-mods/nocheat/pages/changelog-and-downloads/

I'm amazed that so far nothing blew up in flames. Seems for once I didn't completely screw up a major update.

PS: As you can see I use a new versioning system. The idea is the same as the old one: "major.minor.maintainance".

• "Major" version change means your stuff will break, hard.
• "Minor" version change means new features or changed features, you may need to adapt some config settings, but overall it should still work.
• "Maintainance" version change means you shouldn't have to do anything, it's just small bugfixes or modifications.

@HighlifeTTU

Those are only used for "log" actions. They represent where the message should be logged.

• c = server console
• i = ingame chat
• f = NoCheat's logfile

You can freely combine these three for each log action. E.g. If you want to log certain things only to the ingame chat and the server console, but not to the logfile, you'd use ":ci". The order of letters doesn't matter btw, ":cif" is the same as ":ifc" or ":fci" (and NoCheat may change the order of the letters automatically).