KvK Roles

KvK Roles is a member-management tool for servers created with the KvK Server Generator on the Codex Helper website. The generator builds a full KvK server, complete with kingdom and camp roles, channels, and a structure for running a Kingdom versus Kingdom matchup. The /kvk role commands are how you assign people into that structure once the server exists.

When you assign someone a role, the bot does several things in one step: it grants the right kingdom role, adds the matching camp parent role, updates the member’s nickname with a kingdom tag, and sets a hidden sort character so members line up in the correct order in voice channels.


Tier	KvK Server Generator (not free or Patron)
Command	`/kvk role assign`, `remove`, `settings`
Who can use	Admins, plus kingdom R5/Officer leaders within their own kingdom or camp (see Permissions)
Also on dashboard	No

How it works

The KvK Server Generator creates a set of roles for every kingdom in the matchup: an R5 (King) role, an Officer (R4) role, a Member role, and a Pilot role, plus camp-wide “lead” and “member” roles that group kingdoms together. The generator records how those roles map to each kingdom and camp.

/kvk role assign and /kvk role remove use that map. You pick a member, a kingdom number, and a role type, and the bot applies (or strips) the full set of roles that go with it. Kingdom numbers autocomplete as you type, showing each kingdom and the camp it belongs to.

Assigning a role also:

Grants the camp parent role. Assigning R5 or Officer also adds the camp’s lead role; assigning Member adds the camp’s member role. R5 and Officer assignments also grant the kingdom Member and camp Member roles, so leaders are part of their camp too.
Adds Ruins and Altar reminder roles. If those reminder roles exist in the server, they are attached automatically so the member gets event pings. These persist across re-assignments.
Sets a nickname tag. The member’s nickname is prefixed with a tag based on their role: [1234 King] for R5, [1234 R4] for Officers, [1234] for Members, and [Pilot] for pilots (where 1234 is the kingdom number).
Sorts voice channels. A hidden sort character is added so Kings appear first, then Officers, then Members, then Pilots in voice channel member lists.

Removing a role reverses this. The bot strips the kingdom role, and if the member no longer holds any leader (or member) role for that camp, it removes the camp parent role too, then recalculates the nickname tag.

When the bot has the Members intent enabled, it also watches for role changes made by hand and keeps the camp roles and nickname tags in sync as a bonus, without anyone running a command.

Both assign and remove are logged to a channel named log (or logs) if one exists, with an embed showing who changed what.

Commands

`/kvk role assign`

Assign a KvK role to a member.

Option	Type	Required	Description
`member`	Member	Yes	The member to assign the role to.
`kingdom`	Number	Yes	The kingdom number. Autocompletes with the kingdoms set up in this server, each shown with its camp.
`role_type`	R5 / Officer / Member / Pilot	Yes	The type of role to assign.

Behavior:

Grants the kingdom role for the chosen type, the matching camp parent role, and (for R5/Officer) the kingdom and camp Member roles too.
Removes any KvK roles the member held from a previous assignment, so a member only ever holds one kingdom’s role set.
Updates the member’s nickname tag and voice-sort position.
If a camp role cannot be found (for example it was deleted), the bot still assigns what it can and tells you which role it could not apply.

Example

/kvk role assign member:@Player kingdom:1234 role_type:Officer

`/kvk role remove`

Remove a KvK role from a member.

Option	Type	Required	Description
`member`	Member	Yes	The member to remove the role from.
`kingdom`	Number	Yes	The kingdom number. Autocompletes with the kingdoms set up in this server.
`role_type`	R5 / Officer / Member / Pilot	Yes	The type of role to remove.

Behavior:

Removes the kingdom role for the chosen type.
If the member no longer holds any leader role (for R5/Officer) or member role (for Member) for that camp, the camp parent role is removed as well.
Recalculates the member’s nickname tag based on the roles they still have, clearing it if they have none.

Example

/kvk role remove member:@Player kingdom:1234 role_type:Member

`/kvk role settings`

View or change KvK role settings for this server (admin only).

Option	Type	Required	Description
`cross_kingdom`	True / False	No	When on, R5/Officers can use `/kvk role` across every kingdom in their camp. When off (the default), only their own kingdom. Leave blank to view the current setting.

Behavior:

Run with no option to see whether cross-kingdom assignment is currently on or off.
Set cross_kingdom:True to let kingdom R5/Officers manage members across every kingdom in their camp. Set cross_kingdom:False to restrict them to their own kingdom.
This setting only affects non-admins. Server admins can always assign across any kingdom.

Example

View the current setting:

/kvk role settings

Allow camp-wide assignment:

/kvk role settings cross_kingdom:True

Permissions

KvK Roles uses a leadership hierarchy, so kingdom leaders can manage their own people without needing server-wide admin rights.

Server admins (Administrator, Manage Server, or Manage Roles) can assign and remove any role type for any kingdom.
R5 (King) of a kingdom can assign the Officer role within their own kingdom, and Member/Pilot roles subject to the cross-kingdom setting.
Officers (R4) can assign Member and Pilot roles, subject to the cross-kingdom setting.
The R5 (King) role itself can only be assigned by a server admin.

How the cross-kingdom setting changes things for R5/Officers:

Off (default): they can only manage members in their own kingdom.
On: they can manage members across every kingdom in their camp.

/kvk role settings is admin-only: it requires Administrator or Manage Server, or the server’s configured Bot Admin role.

The bot also needs Manage Roles to grant and remove roles, and Manage Nicknames to apply the kingdom tags. Make sure the bot’s own role sits above the KvK roles in the server’s role list, or it will not be able to assign them.

Limits and behavior

Generator servers only. These commands are published only to servers created by the KvK Server Generator. They do not exist in other servers.
One kingdom’s roles at a time. Assigning a member to a kingdom clears their previous KvK roles first, so they never end up in two kingdoms.
Nicknames are tagged automatically. The bot prefixes nicknames with the kingdom tag. It cannot change the server owner’s nickname, and very long names are trimmed to fit Discord’s 32-character limit.
Reminder roles ride along. Ruins and Altar reminder roles are added on assignment if they exist, and they are kept when KvK roles change.
Automatic sync is a bonus, not a guarantee. If the bot has the Members intent, manual role changes are mirrored automatically. Where that intent is unavailable, use the commands directly.

Troubleshooting

“Kingdom N not found in this server’s KvK setup.” That kingdom number is not part of this server’s generated setup. Use the autocomplete to pick a valid kingdom.
“Only server admins can assign the R5 (King) role.” R5 assignment is admin-only. Ask a server admin to grant it.
“You can only assign members from your own kingdom.” Cross-kingdom assignment is off. An admin can enable it with /kvk role settings cross_kingdom:True.
“I don’t have permission to assign those roles.” The bot’s role is below the KvK roles in the role list. Move the bot’s role above them.
“Couldn’t resolve this camp’s role.” A camp role is missing, likely deleted. Re-run the KvK generator for the server to relink the roles if it keeps happening.