Solved How Can I Prevent The Console From Logging Certain Commands?

I have a server where players login by typing "/login <password>".
How can I disable Bukkit from logging "Player issued server command /login <theirPassword>"?
Thanks in advance.

 

We don't give support for servers with "online-mode = false" here. Sorry.

 

You mustn't assume it's offline. The server could just use that plugin because he likes the idea of it.

 

I believe there is an option in the Bukkit.yml which involves logging. Setting it to the lowest setting possible would fix this, but may also remove other messages. (such as plugins who use the logger's "info" method)

 

He likes the idea of cracked servers? Right.

 

You as in who? This is development question. Why assume anything here?
We are all developers and this is a development question. If you want me to rephrase it I can but I will still implement it however the hell I want.
Here is my new question since my old one was not good enough for your help.
How can I prevent a server from logging commands to the console?

Thank you. I will try this and let you know.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

Rprrr there is a chance he's using it for website authentication, like I do?

 

So do you know a way I can do this?

I just checked and I cant find this option anywhere.

EDIT by Moderator: merged posts, please use the edit button instead of double posting.

 

The idea of having a login system... Doesn't have to be cracked. You're just full of yourself today.

 

Perhaps - might be wrong, though - you can use this: http://jd.bukkit.org/rb/doxygen/d4/..._1player_1_1PlayerCommandPreprocessEvent.html

You can cancel it, but still take the input to do the action expected. It might not log it then, if it is cancelled, though I am not sure, not having tried it.

 

Rprrr

*Late reply*
Not all servers that use a plugin that has a login system are cracked. My friend had a similar plugin on his server and it wasn't 'offline'.
AuthMe is a plugin that has a login system and has 2% of server that are online and the rest are offline - This doesn't really help but it shows not all server that use a login system are cracked.

Also these people have a point because I am currently making a plugin for my own server which will use a login system to link the forums to the server and have in-game rewards for forum achievements. Whilst the server is 'online'.

 

add a filter to the bukkit logger that filters contains " issued server command /login "

 

The console hooks into the logger. The logger logs everything that occurs. The only way to modify what is and isnt displayed in the console is by setting the "Level" of logging to display. You can alter it so that only "Level.WARNING" and above is displayed, etc. That's how it works. As far as I am aware, you cannot "omit" lines from being displayed unless you specifically create an environment to do so (i.e. alter or create a plugin).

 

Solved. Did this if anyone is curious.
(This is in my OnEnable() method)

Code:java

 
Filter f = new Filter(){
public boolean isLoggable(LogRecord line) {
if (line.getMessage().contains("/login") || line.getMessage().contains("/register") || line.getMessage().contains("pass")) {
returnfalse;
}
returntrue;
}
 
public String doFilter(String arg0) {
returnnull;
}
 
public String doFilterUrl(String arg0) {
returnnull;
}};
 
 
log.setFilter(f);
 

 

Tooner101

Just optimising/shortening your method:

Code:java

public hoolean isLoggable(LogRecord line) {
    return !(line.getMessage().contains("/login") || line.getMessage().contains("/register") || line.getMessage().contains("pass"))
}

 

Hoolean maybe use .startsWith() instead of .contains() - to stop somebody putting "/login" at the end to avoid a potential situation being logged.

 

You could but its not like the users or anyone else will even know that the console doesnt log certain phrases.

 

jayfella Tooner101

True, always a good precaution. Additionally, make everything lowercase first; I think it may be logged as /LOGIN if a user types it in such a manner

 

Oh ya. Thats what I forgot to do. In any case, its working in the way I want to it to right now. I just have to put that extra check in there.