Skip to content
Fork Docs
Guide v1

/social profile

View a stored relationship profile.

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. Explicit registration contexts: server, bot DM, private channel.

Syntax

Section titled “Syntax”
/social profile [user:User]

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
user User No No registration choices declared; handler validation applies. The caller. Target user to inspect

Permissions

Section titled “Permissions”

No native default-member permission is declared for this path, and no additional native member permission was identified in its reviewed direct handler.

Fork role access is evaluated using the underlying relationship 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”
Slash options
/social profile
Prefix equivalent and aliases
Default prefix
f!relationship

Default prefix: f!; installations can configure another. Handler aliases: iliski, love, couple. 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”

Shows status, partner, anniversary, ring and affinity when present. Without a target it shows the caller.

Failure cases

Section titled “Failure cases”

Missing relationship is shown as single; storage failure is not proof of no relationship. 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.

Section titled “Related commands”
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.