Module: core

These commands are a core part of Nevini and are always available. In other words, this module is active by default and cannot be deactivated.

Command	Description
help	provides a list of commands or details on a specific command
module	displays and configures modules
permission	displays and configures permission node overrides for bot commands
ping	measures the bot’s communication latency
prefix	displays and configures the command prefix

Command: help

Provides a list of commands or details on a specific command.

If a valid command is provided, this will display details on that specific command.
If no valid command is provided, this will display a list of commands.

This command can be executed in a text channel or via direct message.

Permission overrides may be applied on node core.help.

Option	Description
[<command>]	the specific command to look up

Keyword	Aliases
help	about info

Command: module

Displays and configures modules.

By default, this command will behave the same as module get.

This command can only be executed in a text channel and not via direct message.

Keyword	Aliases
module	modules

Command	Description
module get	displays a list of modules
module activate	activates a module
module deactivate	deactivates a module

Command: module get

Displays a list of modules.

If a module is provided, this will display a list of all matching modules.
If no module is provided, this will display a list of all modules.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Server permission to execute this command.
Permission overrides may be applied on node core.module.get.

Option	Description
[–module] <module>	Refers to all bot modules with a matching name. The --module flag is optional if this option is provided first.

Keyword	Aliases
get	display echo list print show
–module	//module

Command: module activate

Activates a module.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Server permission to execute this command.
Permission overrides may be applied on node core.module.activate.

Option	Description
[–module] <module>	Refers to a specific bot module with a matching name. The --module flag is optional if this option is provided first.

Keyword	Aliases
activate	add enable +
–module	//module

Command: module deactivate

Deactivates a module.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Server permission to execute this command.
Permission overrides may be applied on node core.module.deactivate.

Option	Description
[–module] <module>	Refers to a specific bot module with a matching name. The --module flag is optional if this option is provided first.

Keyword	Aliases
deactivate	disable remove -
–module	//module

Command: permission

Displays and configures permission node overrides for bot commands.

By default, this command will behave the same as permission get.

This command can only be executed in a text channel and not via direct message.

Keyword	Aliases
permission	permissions perm perms

Command	Description
permission get	displays effective permissions for bot commands
permission allow	configures permission node overrides for bot commands
permission deny	configures permission node overrides for bot commands
permission reset	resets permission node overrides for bot commands
permission debug	displays a permission node trace for bot commands
permission overrides	displays all configured overrides for the specified node or nodes

Command: permission get

Displays effective permissions for bot commands.

Permission node overrides for bot commands are applied in the following order:

1. Default permissions
   
2. Server permissions
   
3. Permissions based on effective permissions (e.g. “Manage Server”)
   
4. Role permissions
   
5. User permissions
   
6. Channel permissions
   
7. Channel-specific permissions based on effective permissions (e.g. “Manage Server”)
   
8. Channel-specific role permissions
   
9. Channel-specific user permissions

If multiple overrides on the same “level” disagree with each other (e.g. conflicting roles), allow will trump deny.
Server owners and administrators are not restricted by permission node overrides.
Users can only configure permissions for permission nodes they have themselves.
Users can only configure permissions for roles of a lower position than their highest role.
Users can only configure permissions for users whose highest role is lower than their highest role.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Roles permission to execute this command.
Permission overrides may be applied on node core.permission.get.

Option	Description
[–node] <node>	Refers to all permission nodes for bot commands with a matching name. The --node flag is optional if this option is provided first.
–all	Explicitly refers to all permission nodes.
–server	Refers to the current server.
–permission <permission>	Refers to a specific permission with a matching name (e.g. “Manage Server”).
[–role] <role>	Refers to a specific role with a matching mention, id or name. The --role flag is optional if a role mention is used.
[–user] [<user>]	Refers to a specific user with a matching mention, id, name, nickname or in-game name. The --user flag is optional if a user mention is used. Refers to the current user if only the --user flag is provided.
[–channel] [<channel>]	Refers to a specific text channel with a matching mention, id or name. The --channel flag is optional if a channel mention is used. Refers to the current channel if only the --channel flag is provided.

Keyword	Aliases
get	display echo list print show
–node	//node -n /n
–all	//all -a /a
–server	//server –guild //guild -s /s -g /g
–permission	//permission –perm //perm -p /p
–role	//role -r /r
–user	//user –member //member -u /u -m /m
–channel	//channel -c /c

Command: permission allow

Configures permission node overrides for bot commands.

Permission node overrides for bot commands are applied in the following order:

1. Default permissions
   
2. Server permissions
   
3. Permissions based on effective permissions (e.g. “Manage Server”)
   
4. Role permissions
   
5. User permissions
   
6. Channel permissions
   
7. Channel-specific permissions based on effective permissions (e.g. “Manage Server”)
   
8. Channel-specific role permissions
   
9. Channel-specific user permissions

If multiple overrides on the same “level” disagree with each other (e.g. conflicting roles), allow will trump deny.
Server owners and administrators are not restricted by permission node overrides.
Users can only configure permissions for permission nodes they have themselves.
Users can only configure permissions for roles of a lower position than their highest role.
Users can only configure permissions for users whose highest role is lower than their highest role.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Roles permission to execute this command.
Permission overrides may be applied on node core.permission.allow.

Option	Description
[–node] <node>	Refers to all permission nodes for bot commands with a matching name. The --node flag is optional if this option is provided first.
–all	Explicitly refers to all permission nodes.
–server	Refers to the current server.
–permission <permission>	Refers to a specific permission with a matching name (e.g. “Manage Server”).
[–role] <role>	Refers to a specific role with a matching mention, id or name. The --role flag is optional if a role mention is used.
[–user] [<user>]	Refers to a specific user with a matching mention, id, name, nickname or in-game name. The --user flag is optional if a user mention is used. Refers to the current user if only the --user flag is provided.
[–channel] [<channel>]	Refers to a specific text channel with a matching mention, id or name. The --channel flag is optional if a channel mention is used. Refers to the current channel if only the --channel flag is provided.

Keyword	Aliases
allow	add grant
–node	//node -n /n
–all	//all -a /a
–server	//server –guild //guild -s /s -g /g
–permission	//permission –perm //perm -p /p
–role	//role -r /r
–user	//user –member //member -u /u -m /m
–channel	//channel -c /c

Command: permission deny

Configures permission node overrides for bot commands.

Permission node overrides for bot commands are applied in the following order:

1. Default permissions
   
2. Server permissions
   
3. Permissions based on effective permissions (e.g. “Manage Server”)
   
4. Role permissions
   
5. User permissions
   
6. Channel permissions
   
7. Channel-specific permissions based on effective permissions (e.g. “Manage Server”)
   
8. Channel-specific role permissions
   
9. Channel-specific user permissions

If multiple overrides on the same “level” disagree with each other (e.g. conflicting roles), allow will trump deny.
Server owners and administrators are not restricted by permission node overrides.
Users can only configure permissions for permission nodes they have themselves.
Users can only configure permissions for roles of a lower position than their highest role.
Users can only configure permissions for users whose highest role is lower than their highest role.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Roles permission to execute this command.
Permission overrides may be applied on node core.permission.deny.

Option	Description
[–node] <node>	Refers to all permission nodes for bot commands with a matching name. The --node flag is optional if this option is provided first.
–all	Explicitly refers to all permission nodes.
–server	Refers to the current server.
–permission <permission>	Refers to a specific permission with a matching name (e.g. “Manage Server”).
[–role] <role>	Refers to a specific role with a matching mention, id or name. The --role flag is optional if a role mention is used.
[–user] [<user>]	Refers to a specific user with a matching mention, id, name, nickname or in-game name. The --user flag is optional if a user mention is used. Refers to the current user if only the --user flag is provided.
[–channel] [<channel>]	Refers to a specific text channel with a matching mention, id or name. The --channel flag is optional if a channel mention is used. Refers to the current channel if only the --channel flag is provided.

Keyword	Aliases
deny	block refuse
–node	//node -n /n
–all	//all -a /a
–server	//server –guild //guild -s /s -g /g
–permission	//permission –perm //perm -p /p
–role	//role -r /r
–user	//user –member //member -u /u -m /m
–channel	//channel -c /c

Command: permission reset

Resets permission node overrides for bot commands.

Permission node overrides for bot commands are applied in the following order:

1. Default permissions
   
2. Server permissions
   
3. Permissions based on effective permissions (e.g. “Manage Server”)
   
4. Role permissions
   
5. User permissions
   
6. Channel permissions
   
7. Channel-specific permissions based on effective permissions (e.g. “Manage Server”)
   
8. Channel-specific role permissions
   
9. Channel-specific user permissions

If multiple overrides on the same “level” disagree with each other (e.g. conflicting roles), allow will trump deny.
Server owners and administrators are not restricted by permission node overrides.
Users can only configure permissions for permission nodes they have themselves.
Users can only configure permissions for roles of a lower position than their highest role.
Users can only configure permissions for users whose highest role is lower than their highest role.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Roles permission to execute this command.
Permission overrides may be applied on node core.permission.reset.

Option	Description
[–node] <node>	Refers to all permission nodes for bot commands with a matching name. The --node flag is optional if this option is provided first.
–all	Explicitly refers to all permission nodes.
–server	Refers to the current server.
–permission <permission>	Refers to a specific permission with a matching name (e.g. “Manage Server”).
[–role] <role>	Refers to a specific role with a matching mention, id or name. The --role flag is optional if a role mention is used.
[–user] [<user>]	Refers to a specific user with a matching mention, id, name, nickname or in-game name. The --user flag is optional if a user mention is used. Refers to the current user if only the --user flag is provided.
[–channel] [<channel>]	Refers to a specific text channel with a matching mention, id or name. The --channel flag is optional if a channel mention is used. Refers to the current channel if only the --channel flag is provided.

Keyword	Aliases
reset	clear default
–node	//node -n /n
–all	//all -a /a
–server	//server –guild //guild -s /s -g /g
–permission	//permission –perm //perm -p /p
–role	//role -r /r
–user	//user –member //member -u /u -m /m
–channel	//channel -c /c

Command: permission debug

Displays a permission node trace for bot commands.

Permission node overrides for bot commands are applied in the following order:

1. Default permissions
   
2. Server permissions
   
3. Permissions based on effective permissions (e.g. “Manage Server”)
   
4. Role permissions
   
5. User permissions
   
6. Channel permissions
   
7. Channel-specific permissions based on effective permissions (e.g. “Manage Server”)
   
8. Channel-specific role permissions
   
9. Channel-specific user permissions

If multiple overrides on the same “level” disagree with each other (e.g. conflicting roles), allow will trump deny.
Server owners and administrators are not restricted by permission node overrides.
Users can only configure permissions for permission nodes they have themselves.
Users can only configure permissions for roles of a lower position than their highest role.
Users can only configure permissions for users whose highest role is lower than their highest role.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Roles permission to execute this command.
Permission overrides may be applied on node core.permission.debug.

Option	Description
[–node] <node>	Refers to a specific permission node for bot commands with a matching name. The --node flag is optional if this option is provided first.
–all	Explicitly refers to all permission nodes.
–server	Refers to the current server.
–permission <permission>	Refers to a specific permission with a matching name (e.g. “Manage Server”).
[–role] <role>	Refers to a specific role with a matching mention, id or name. The --role flag is optional if a role mention is used.
[–user] [<user>]	Refers to a specific user with a matching mention, id, name, nickname or in-game name. The --user flag is optional if a user mention is used. Refers to the current user if only the --user flag is provided.
[–channel] [<channel>]	Refers to a specific text channel with a matching mention, id or name. The --channel flag is optional if a channel mention is used. Refers to the current channel if only the --channel flag is provided.

Keyword	Aliases
–node	//node -n /n
–all	//all -a /a
–server	//server –guild //guild -s /s -g /g
–permission	//permission –perm //perm -p /p
–role	//role -r /r
–user	//user –member //member -u /u -m /m
–channel	//channel -c /c

Command: permission overrides

Displays all configured overrides for the specified node or nodes.

Permission node overrides for bot commands are applied in the following order:

1. Default permissions
   
2. Server permissions
   
3. Permissions based on effective permissions (e.g. “Manage Server”)
   
4. Role permissions
   
5. User permissions
   
6. Channel permissions
   
7. Channel-specific permissions based on effective permissions (e.g. “Manage Server”)
   
8. Channel-specific role permissions
   
9. Channel-specific user permissions

If multiple overrides on the same “level” disagree with each other (e.g. conflicting roles), allow will trump deny.
Server owners and administrators are not restricted by permission node overrides.
Users can only configure permissions for permission nodes they have themselves.
Users can only configure permissions for roles of a lower position than their highest role.
Users can only configure permissions for users whose highest role is lower than their highest role.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Roles permission to execute this command.
Permission overrides may be applied on node core.permission.overrides.

Option	Description
[–node] <node>	Refers to all permission nodes for bot commands with a matching name. The --node flag is optional if this option is provided first.
–all	Explicitly refers to all permission nodes.

Keyword	Aliases
overrides	override
–node	//node -n /n
–all	//all -a /a

Command: ping

Measures the bot’s communication latency.

This command can be executed in a text channel or via direct message.

Permission overrides may be applied on node core.ping.

Keyword	Aliases
ping	pong latency

Command: prefix

Displays and configures the command prefix.

By default, this command will behave the same as prefix get.

This command can only be executed in a text channel and not via direct message.

Command	Description
prefix get	displays the currently configured command prefix
prefix set	configures the command prefix
prefix unset	removes the configured command prefix

Command: prefix get

Displays the currently configured command prefix.

This command can only be executed in a text channel and not via direct message.

Permission overrides may be applied on node core.prefix.get.

Keyword	Aliases
get	display echo list print show

Command: prefix set

Configures the command prefix.

The command prefix cannot be longer than 32 characters and must not contain spaces.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Server permission to execute this command.
Permission overrides may be applied on node core.prefix.set.

Option	Description
[–prefix] <prefix>	The command prefix to use. The flag is optional.

Keyword	Aliases
–prefix	//prefix

Command: prefix unset

Removes the configured command prefix.

This command can only be executed in a text channel and not via direct message.

By default, you need the Manage Server permission to execute this command.
Permission overrides may be applied on node core.prefix.set.