Limits and errors

Sugar limits keep public creations fast, predictable, and safe. The editor stays lightweight while you type. JOI compiles and checks the complete program in Sandbox Mode or when the creation actually runs.

Authoring limits

Program limits

A single dice expression may roll up to 10 dice using d2, d4, d6, d8, d10, d12, or d20. Dice modifiers may not exceed 1000 in magnitude.

Creator functions cannot use direct or indirect recursion.

Collection limits

Collections may contain text, numbers, booleans, None, lists, and objects.

Embed limits

Banner, thumbnail, and field icon media must resolve to named images, not videos or arbitrary URLs.

Chip limits

App limits

A chat and a host Item can each belong to one current Session. A lobby expires after one hour if it never starts. An active Session expires after 24 hours without activity. Standalone message interactions expire after one hour; interactions belonging to a Session live with that Session.

Apps require account Plus.

Libraries produced while migrating older per-action media keep every resource even when the combined result exceeds the normal Media Library limit. New uploads remain unavailable until the library is brought below that limit.

Common errors

Unknown variable

Check spelling and capitalization. Add $ for App variables.

Cannot be assigned

This type of code cannot change the variable. Common examples are const declarations, Item objects, and App variables outside the Automation’s selected scope.

Unexpected statement

Check for a missing semicolon, unmatched { }, or an if, else if, or else branch without braces. Value-producing conditionals still require both then and else.

Expected a list

A one-entry list needs a trailing comma:

({ title: "Score", text: score },)

Media does not exist

Check the exact name and confirm that the media is available to the Item, Boop, or linked App. Embed image properties require an image, not a video.

Function cannot be used here

Conditions and templates cannot change outside variables. Automations cannot add message content or use functions that require confirmation.

Item changed before use

The inventory or Item changed while the confirmation screen was open. Run the action again so JOI can use the latest values.

Not enough Lore

The available balance cannot cover every requested payment. Sugar includes earlier charges and transfers from the same program when checking the balance.