/social propose
Send a dating proposal to another user.
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 propose <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 | Yes | No registration choices declared; handler validation applies. | Required input | The user you want to ask out |
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 propose 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”/social propose user:@AlexPrefix equivalent and aliases
f!propose @AlexDefault prefix: f!; installations can configure another. Handler aliases: date, cikmateklifi, askout. 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 target can accept or decline using the proposal controls; no relationship is created merely by sending the request.
Failure cases
Section titled “Failure cases”Self-proposals, existing relationship conflicts, declined/expired requests or unavailable storage may prevent a 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”The target has 60 seconds to accept or decline. Only that target can answer the proposal controls.
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.