literalplus / quietcord

A simple BungeeCord plugin which aims to reduce log spam caused by InitialHandler.
MIT License
5 stars 5 forks source link

Not working with bungeecord-1119 #7

Closed NyviaNetwork closed 6 years ago

NyviaNetwork commented 6 years ago

Using QuietCord and it doesnt get rid of the Intialhandler has connected thing.

Using this version of bungeecord: https://yivesmirror.com/grab/bungeecord/BungeeCord-1119.jar

With latest version of QuietCord: 1.0

If this could get fixed that would be fantastic!

literalplus commented 6 years ago

Hi, thanks for your bug report! Sadly, I have been unable to reproduce this behaviour with both the latest BungeeCord version as well as the version you provided.

Please verify that your server log contains the following important messages:

18:45:40 [INFO] [QuietCord] This logger is now filtered by InitialHandlerFilter{filterPings=true, filterJoins=false}
18:45:40 [INFO] Enabled plugin QuietCord version 1.0-git-00f2196 by Literallie

2018-02-23_18 02 19

Can you try to reproduce the problem in a minimal clean install (it didn't occur for me in such an installation)?

If the problem doesn't appear there, please provide your full BungeeCord startup log up to the point where the wrong message appears, your QuietCord configuration file, and the list of other BungeeCord plugins you're using (all from the Bungee server where the problem is happening of course), so that we can figure out the cause.

literalplus commented 6 years ago

Sorry, you were right – I assumed that the build number from your website would match the official build numbers, but apparently they don't… The official build 1119 works, but the mirrored one doesn't.

You could try using the official build from here for now: https://ci.md-5.net/job/BungeeCord/1119/

Update: It seems to also occur with the official build, but only sparely, randomly, and only for joins. I can't get it to print for server list pings.

literalplus commented 6 years ago

Okay, next update: I haven't worked with this plugin in a while. The InitialHandler has connected messages aren't blocked for joins by default because they may provide valuable debug information. These look like this:

18:17:59 [INFO] [Literallie] <-> InitialHandler has connected

If you wish to turn these off, set filter.initialhandler.join to true in plugins/QuietCord/config.yml.

If, however, you were referring to these messages (note the IP address), we're looking at a bug:

18:17:51 [INFO] [/127.0.0.1:50046] <-> InitialHandler has connected

Please report back with whether this was the issue, and if not, the server logs and configuration file.

NyviaNetwork commented 6 years ago

Still getting the initialhandler has connected thing even with the bungeecord you have sent me.

literalplus commented 6 years ago

Please read the other comments too, especially the last one.

literalplus commented 6 years ago

I'm sorry, that reply was a little rude. What I meant to say was, please show the configuration file (plugins/CommandBlockerUltimate/config.yml) that is causing the issue and the exact messages that are wrongly getting through.