Bukkit

Version 2.25:

• 
  
• BREAKING CHANGE: To use NoCheats commands, you'll need now the "nocheat.admin.commands" node. All the individual nodes per command have been removed. This way Bukkit can handle permission checking for me.
  
• New check "chat.color": Filters color codes from chat messages from players. As usual, there is a permission node, config file stuff etc. for it.
  

Because people requested the color thing. By default the message will still be displayed, but all colors will be removed from them first.

@GameOverRules

Then you'd need to give more information. I assure you, it works well for others. Here are some frequently encountered problems:

• "Towny" blocks flying too. If you use it, read it's configuration files to find out how to fix that.
  
• The nodes are called "nocheat.checks.some.thing". Make sure to use the correct names: http://dev.bukkit.org/server-mods/nocheat/pages/permissions/ .
  
• Also, you shouldn't need to use a "*" for these permissions. "nocheat.checks.moving" includes "nocheat.checks.moving.flying" and all the other children already.
  
• If you give a player a permission node, then he is allowed to bypass that check (he can cheat). No node = no permission. Some people manage to mix that up.

@TerrorBiteIndustries

NoCheat can identify the use of Potion of Swiftness and will allow the player to move faster automatically in that case.

@GameOverRules

Simply set up your PermissionsEx permission nodes correctly and it will work.

As you may have noticed, I've not been around for almost a week. I was sick.

@FurmigaHumana

Yes it is. Kicking is actually done in some cases already, look at the config.txt at the stuff related to "inventory.drop" or "chat.spam". They both have an action called "...kick", which only does issue the console command "/kick playername". You can write your own actions like that.

Open your "actions.txt" and copy-paste this line into it:

[code]consolecommand actionname 0 1 command parameters[/code]

Choose "actionname" yourself (something that describes what it does), "command" should be the console command that you want to execute, and "parameters" the parameters that the console command needs. E.g. kicking works by default like this:

[code]consolecommand dropKick 0 1 kick [player][/code]

[player] will be automatically replaced by the name of the player. When you are finished with defining your action, you save the file, open config.txt and write the name of your new action to whatever checks you want, right next to the existing "...Log" or "...Cancel" actions.

http://dev.bukkit.org/server-mods/nocheat/pages/actions/

@Munkyman587

That's the risk of using a development build of CraftBukkit. I won't fix problems that only appear in development builds and will most likely get fixed anyway before the release of a RB.

In your case, the dupe glitch has been fixed now by CraftBukkit.

@Crayder

Sorry, I can't help you with that because I don't know.

@The_Wizard

Yes, you are correct. I called those "bogus" items, because they were stacks with a negative amount. I'm not sure how useful that would be though, because if I remember correctly, it is possible to split these stacks into a normal stack of size 1 and a stack of "original size minus 1", therefore still having infinite items anyway.