You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A clear and concise description of what the bug is.
What do we have to do to reproduce this bug?
Steps to reproduce the behavior:
Create a new command with the executor PLAYER_AND_CONSOLE
allow custom parameters
put this in the onCommand(KelpPlayer,String[]) method:
System.out.println(Arrays.toString(args));
What would you expect to happen?
When the executorType is PLAYER_AND_CONSOLE and you execute the command with parameters, you see nothing in the console. But when the executorType is PLAYER_ONLY then everything works and you see the args in the console.
Environment information
Operating system: Windows 10 20H1
Java-Version: 1.8
Kelp-Core-Version: v.0.0.3
Version-Implementation: 1.8
The text was updated successfully, but these errors were encountered:
I have now fixed the bug. Actually, it was not a real bug, as PLAYER_AND_CONSOLE only called the onCommand(ConsoleSender, args) method and not the player method, because the command should be the same for players and consoles. But I have now changed it so that you can have both onCommand methods and depending on the executor, the corresponding method will be called.
If you want to have the same command handler method for both player and console, then you could do something like that:
Describe the bug
A clear and concise description of what the bug is.
What do we have to do to reproduce this bug?
Steps to reproduce the behavior:
What would you expect to happen?
When the executorType is PLAYER_AND_CONSOLE and you execute the command with parameters, you see nothing in the console. But when the executorType is PLAYER_ONLY then everything works and you see the args in the console.
Environment information
The text was updated successfully, but these errors were encountered: