AuthMe
Hiding messages when changing to another server
Hiding messages when changing to another server. Hide these messages: You have successfully logged into the server! Session saved!
...and so on
I connetced my bungeecord server now, but now if i go back to the lobby server i see this: http://prntscr.com/isg4j1
- i was longer than 1 minute(Cache) away
- 2 messages that are saying i already logged in but its just going back to the lobby... Can you fix this problems please?
I suggest making the parameter in the AuthMe config file. Add a "bungee mode" that would hide unnecessary messages and generally, optimize AuthMe under Bungee.
This plugin isnt supported anymore i think, the author isnt fixing any bugs while there are a few importand that have to get fixed.
@ItzRonaldLG what are you talking about? Today I fixed a mayor issue. Nobody complained about such bugs. @DarkFort Just found a possible ENHANCEMENT. instead of posting your issue there just open a new report, or your report will be IGNORED or even deleted. Thank you.
Today? It was reported like 6 monthes ago.. Not verry active plugin author, i already have another plugin becouse of the inactivity
It was ignored because you posted it in the wrong place, does it make sense to report a bug in an enhancement suggestion report? -_-
The other thread was the same problem and was longer ago posted and still took monthes to fix. So its the same thing again, aothor is to inactive.
This thread is linked to the other thread from "DarkFort" he made the thread withe the same issue as i had, so i didnt response anymore here becouse it was already dealt with. But like i said again i dont like inactive recources becouse they wont fix bugs. This is my last message to this plugin, i have already a better one. Bye.
@ItzRonaldLG bye, that's the respect you gain for maintaining free and opensource project, thank you, what an amazing community ;)
@sgdc3,hmmm. I understand that you will not do anything from what I wrote because the issue is not published there?
@DarkFort i was talking to @ItzRonaldLG because he reported a different issue, not strictly related to this one