Deprecate JDACommandManager and add JDA4CommandManager
This commit is contained in:
parent
530ecc4f73
commit
c5873e46e6
4 changed files with 88 additions and 13 deletions
|
|
@ -26,7 +26,7 @@ package cloud.commandframework.examples.jda;
|
|||
import cloud.commandframework.Command;
|
||||
import cloud.commandframework.arguments.standard.StringArgument;
|
||||
import cloud.commandframework.execution.CommandExecutionCoordinator;
|
||||
import cloud.commandframework.jda.JDACommandManager;
|
||||
import cloud.commandframework.jda.JDA4CommandManager;
|
||||
import cloud.commandframework.jda.JDAGuildSender;
|
||||
import cloud.commandframework.jda.JDAPrivateSender;
|
||||
import cloud.commandframework.jda.parsers.UserArgument;
|
||||
|
|
@ -66,7 +66,7 @@ public final class ExampleBot {
|
|||
|
||||
final PermissionRegistry permissionRegistry = new PermissionRegistry();
|
||||
|
||||
final JDACommandManager<CustomUser> commandManager = new JDACommandManager<>(
|
||||
final JDA4CommandManager<CustomUser> commandManager = new JDA4CommandManager<>(
|
||||
jda,
|
||||
message -> "!",
|
||||
(sender, permission) -> permissionRegistry.hasPermission(sender.getUser().getIdLong(), permission),
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue