/image
Generate an image or edit an attached image/avatar reference.
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”/image <prompt:String> [user:User] [aspect_ratio:String] [resolution:String] [image:Attachment]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 |
|---|---|---|---|---|---|
prompt |
String | Yes | No registration choices declared; handler validation applies. | Required input | Detailed text description of the image to generate or edit |
user |
User | No | No registration choices declared; handler validation applies. | No avatar reference. | Target Discord user whose avatar to use as drawing reference |
aspect_ratio |
String | No | 16:9, 1:1, 9:16, 4:3, 21:9, 3:2 |
1:1 | Aspect ratio of generated image |
resolution |
String | No | 2K, 4K |
2K | Resolution tier (2K or 4K Ultra-HD) |
image |
Attachment | No | No registration choices declared; handler validation applies. | No attached reference. | Optional reference image file for image-to-image editing |
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 image 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”/image prompt:A monochrome lunar observatory aspect_ratio:16:9Prefix equivalent and aliases
f!image A monochrome lunar observatory --aspect-ratio 16:9Default prefix: f!; installations can configure another. Handler aliases: draw, imagine, generateimage, drawuser. Aliases are prefix names, not additional slash commands. Handler-declared usage: f!image <prompt> [@user] [--aspect-ratio <ratio>] [--resolution 2K|4K] [image attachment].
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”Returns the generated image attachment. An attachment takes precedence over a user-avatar reference.
Failure cases
Section titled “Failure cases”One generation per hour per user, provider failure, invalid input or unavailable reference can prevent output. 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”One generation per hour per user, enforced by the image limiter. Provider/account limits also apply.
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.