/scope add
/scope add <save_as> [telescope_model] [focal_length] [aperture] [aperture_diameter_mm]
Saves a named telescope profile (focal length + aperture) for
reuse with /maxexposure, so you don’t have to retype your
optics every time — especially handy with more than one scope.
Recommended: keep the first save simple, then finish with
/scope edit. Discord submits this command the instant you
press Enter — save_as is the only required field, so hitting
Enter partway through picking a telescope_model submits
immediately with just that name. The reliable flow:
/scope add save_as: "My RedCat" telescope_model: [pick from autocomplete] (just those two — this alone fills in verified
focal length and aperture), then use /scope edit for anything
else. Its dropdown-then-form flow can’t accidentally
half-submit the way a slash command with several optional
fields can.
Usage: /scope add save_as: "My RedCat" telescope_model: [pick from autocomplete] for a known telescope body — this
fills in verified focal length and aperture in one step. If
your exact model isn’t listed, use /scope add save_as: "RedCat 51" focal_length: 250 aperture: 4.9 if you know the f-number
directly, or focal_length: 250 aperture_diameter_mm: 51 if
you only know the raw aperture diameter (f-number gets derived
as focal_length ÷ diameter). Precedence when more than one
source is given: focal_length > telescope_model’s focal
length; aperture > aperture_diameter_mm > telescope_model’s
aperture diameter. Using a telescope_model together with your
own focal_length (e.g. a focal reducer) correctly computes
the resulting effective f-ratio, not the stock one.
telescope_model autocompletes as you type, pulling from a
shared database rather than a fixed list — new models added
there show up immediately, without needing a bot update.
save_as autocompletes your existing saved scopes as you type
— picking one updates that profile in place rather than
creating a duplicate, no need to delete and re-add it — and
only touches the fields you actually provide: leaving out
focal_length (or both aperture/aperture_diameter_mm) on a
later save keeps whatever was already saved for that field, so
you can update just the aperture (a new reducer, say) without
re-stating the focal length too, and vice versa.
Also see /scope edit for a guided, dropdown-and-form way to
update an existing profile, showing its current values instead
of requiring you to know or retype them.
For a smart telescope (Seestar, Dwarf, Vespera, etc.), save a
scope profile for its fixed optics here, and also save a
camera profile (/savecamera) for its built-in sensor’s pixel
pitch — two separate profiles describing one device, since
those are independent specs everywhere else in this bot.
Parameters
| Name | Required | Description |
|---|---|---|
save_as | Yes | A label to save this scope under, e.g. 'RedCat 51' or 'Seestar S50' |
telescope_model | No | Pick a known telescope body for verified focal length + aperture |
focal_length | No | Focal length in mm (overrides telescope_model if both given) |
aperture | No | f-number (e.g. 4.9) -- takes precedence over aperture_diameter_mm/telescope_model if given |
aperture_diameter_mm | No | Physical aperture diameter in mm (overrides telescope_model's own diameter) |