/setup
Configure Fork command-role access through a reviewed recommendation or the dashboard.
Availability
Section titled “Availability”Public source-edition command; execution remains conditional on installation, server policy and the running service. This reference is built from the repository, not a live Discord registration probe. The builder does not declare explicit context restrictions; handler and policy checks still apply.
Syntax
Section titled “Syntax”/setup [mode:String]Angle brackets indicate required input; square brackets indicate optional input. In Discord, choose the command and fill its named options, rather than typing the brackets.
Parameters
Section titled “Parameters”| Name | Type | Required | Allowed values / bounds | Default when omitted | Description |
|---|---|---|---|---|---|
mode |
String | No | fork, manual |
fork | Choose how to configure Fork |
Permissions
Section titled “Permissions”Required native member permission(s): Administrator (Administrator normally satisfies native permission checks).
Fork role access is evaluated using the underlying setup policy key, even when the slash name is grouped. Native Discord permission checks remain separate from Fork role grants. Sensitive commands fail closed before valid setup; native Administrator bypasses Fork’s role matrix, not Discord’s bot permissions or target hierarchy. See Permission model.
Examples
Section titled “Examples”/setupPrefix equivalent and aliases
f!setupDefault prefix: f!; installations can configure another. Handler aliases: config, perms, permission. Aliases are prefix names, not additional slash commands.
Grouped prefix routes also delegate to the original handlers, but aliases retain that handler’s argument parsing. Conflicting aliases are rejected as ambiguous. Prefix replies are generally visible in the channel; prefer slash privacy controls for sensitive personal data.
Expected result
Section titled “Expected result”Fork mode prepares role-access recommendations; manual mode opens Role Permissions. Opening the dashboard alone does not complete setup. Native Discord permissions are not rewritten.
Failure cases
Section titled “Failure cases”Administrator permission, preflight blockers, stale recommendations or persistence failures can prevent setup. Resume the existing state instead of creating duplicate work. Check the returned error, current bot status and the relevant server permissions. A timeout or uncertain receipt is not proof that nothing happened; inspect state before repeating a mutation.
Usage limits
Section titled “Usage limits”No fixed command-specific cooldown is declared in this reviewed entry. Discord rate limits, provider budgets, service admission and server policy can still apply; this is not an unlimited-usage promise.
Related commands
Section titled “Related commands”Related guides
Section titled “Related guides”Source edition v1 · Registration, direct handler and shared authorization review are hash-bound in the local documentation validation. This is not a production feature-availability certification.