/faq set
Add or replace a server knowledge topic used by Fork AI.
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”/faq set <topic:String> <content: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 |
|---|---|---|---|---|---|
topic |
String | Yes | No registration choices declared; handler validation applies. | Required input | Topic name (e.g. rules, roblox_group, discord_link) |
content |
String | Yes | No registration choices declared; handler validation applies. | Required input | Detailed content or answer for this topic |
Permissions
Section titled “Permissions”Required native member permission(s): ManageGuild (Administrator normally satisfies native permission checks).
Fork role access is evaluated using the underlying faq 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”/faq set topic:community-night content:Community night starts at 19:00 UTC on Friday.Prefix equivalent and aliases
f!faq set community-night Community night starts at 19:00 UTC on Friday.Default prefix: f!; installations can configure another. Handler aliases: knowledge, serverfaq. 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”The topic is saved and can be used as server context; this does not train a model or guarantee every answer will include it.
Failure cases
Section titled “Failure cases”Requires Manage Server in the handler. Missing topic/content or unavailable storage prevents a save. 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.