Bukkit

@Absolutionmc

A new version is waiting for approval.

If you need the new version now, you can download it from the CI server specified in the description.

EDIT: Have you considered giving free cookies to the angry players?

Often worked for me ;-)

@Absolutionmc

I guess this happened when somebody mentioned the same hostname in a short period of time twice... Sorry about that, I didn't think the process of resending through completely... I think my latest fix should correct this, I'll put it up as soon as possible, meanwhile, I'll include a link to my CI server in the description, so you can get an updated version fast.

@Apple_columb

Was that a question? If so, the answer is: Yes, you can do that, so when somebody mentions this server in the chat, no actions will be performed

@_Mahagon

Oops :-D Will be fixed in the next version.

@Hulipill

That's not exactly how it works, as 8.8.8.8 is a DNS server run by google (AFAIK), it won't be treated as advertisement.

Replacing by a configurable text rather than by * characters isn't implemented yet, but that's only a small change to do ;-)

I haven't tested the plugin with 1.5.1, but since there are no major changes concerning the chat and plugin handling, it should work just fine :-)

@Absolutionmc

Thanks a lot :-) It's always good to hear from people who appreciate my work.

@Nickshelton80

Yep, sorry about that but the author of TownyChat has to make a small change to his plugin as well as it doesn't distinguish between cancelled chat messages (that won't be sent) and chat messages that will be sent. I've already sent a Pull Request to his github code base, hoping he will merge it

You should stick to using the old 2.0 version as I had misinterpreted the execution order based on the listener priorities, so the fix in TownyChat should suffice at least for normal chat messages. I can't guarantee this for commands as the developer set the listener priority for his command event to LOWEST, which I can't undercut. The execution order will then depend on the order the plugins are loaded in, which I can't influence...

Therefore I removed the newer build (also to keep the version numbers going) ;-)

@Absolutionmc

Yes it does, but only if there is a minecraft server running at that address (additional port information like address:port is read too)

@Nickshelton80

Oh, I didn't think of that issue :-D The low priority of the chat listener of my plugin makes the towny plugin think the same message has been sent twice in a short period of time, even though the first message has been cancelled...

The problem here is that the TownyChat plugin uses the priority 'high' to check the chat and assumes that the message won't be blocked by other plugins. Therefore a message that is first blocked but later resent is considered spam...

EDIT: I see that I've been looking through an older version of the source code of TownyChat, in the current version, the listener has low priority. I'll change the priority of my chat listener and with a small change I suggested to the author of Towny, that problem should be solved ;-)

@lst96

That behaviour is intended.

How should the plugin be able to distinguish between a 'legitimate address' like google.com, youtube.com, minecraft.net and a server that is currently not running, like example.no-ip.org? (Actually, when looking through some old chat logs, I found about as much server advertising as mentions of minecraft.net, e.g. when the login didn't work for some people due to downtime)

As I wrote in the plugin description, only addresses of running minecraft servers will cause measures against the player.