Limits
Craft caps how much one account, world or game can hold, and how big some things inside it can be. The caps keep large worlds fast and stop one runaway world from slowing Craft down for everyone. Most are far above what a real world needs. The ones you are most likely to meet are the projects and games your plan allows, and the GM instruction budgets. This page lists every limit, grouped by where it applies, with a link to the doc that explains each one.
How it is used
- A limit is checked when something is added. Creating, importing, pasting, moving or installing past a limit is refused, with a message that names the limit. Nothing already saved is deleted.
- What is already over a limit keeps working. A world that grew past a limit before the limit existed still opens, plays, publishes and starts games. An account whose plan dropped keeps every project and game it owns. Either way, you can't add more until you are under the limit.
- Copies Craft makes for you aren't checked. Publishing a release, cloning a world's contents and starting a game copy the files as they are, so a large world still starts games.
- A world and each game count separately. A game started from a world gets its own copy of the files, and its own file, folder and file type limits.
Projects and games per plan
Your plan sets how many projects (worlds) and games you can own at once. Each game you own counts, including games in the trash.
| Plan | Projects | Games |
|---|---|---|
| Free | 10 | 10 |
| Starter | 50 | 20 |
| Plus | 75 | 30 |
| Pro | 100 | 40 |
| Max | 150 | 60 |
| Ultra | 250 | 100 |
- The trash still counts. A deleted project or game stays in the trash for 3 days, where you can restore it, and it counts until it is deleted forever or the trash empties itself. To make room now, delete it forever from the trash. See deleting a game.
- Cloning a world or importing one as a new project takes a project slot, and starting a game takes a game slot.
- Moving to a smaller plan deletes nothing. You keep everything, but can't create, clone or start more until you are under the new limit.
See energy and credits for what each plan costs and includes.
A world or game
These hold for each project and each game.
| Limit | Value |
|---|---|
| Files | 10,000 |
| Folders | 1,000 |
| How deep folders nest | 15 levels |
| File types | 100 |
| Linked locations on one location | 100 |
Files, folders and types in the trash don't count. See files.
These hold for each project (how invites and editors work: working with others):
| Limit | Value |
|---|---|
| Editors besides the owner, pending invites included | 4 |
| Project invites one account sends | 50 in 24 hours |
| Tags on a project | 3 |
| Items in the project gallery | 48 |
| Each art direction text | 5,000 characters |
See project and linked locations.
File types and fields
| Limit | Value |
|---|---|
| Top-level fields in a type | 200 |
| Fields directly inside one object, or one item of a list of objects | 100 |
| Values in one enum | 50 |
| File types one reference field can target | 5 |
| A type's layout | 1 MB |
| Expressions a type's files can have | 16 |
A type already over a field limit can be saved with the same number of fields or fewer, never more. A layout over its limit can be saved at the same size or smaller, never larger.
Computed fields have their own limits on expression length, nesting and work per field, and reference filters on conditions and values:
| Limit | Value |
|---|---|
| Expression length | 5,000 characters |
| Nesting depth | 64 levels of brackets, calls and operators |
| Functions inside functions | 8 deep |
| Work per field | 100,000 steps; each step inside a function passed to a method counts again for every item it runs on |
| Size of a computed value | 10,000 items and keys in all, and 262,144 characters as JSON |
See file types, expressions and references.
GM instructions and trackers
The GM reads your instructions every turn, so they have budgets of their own. A budget counts the largest game a player can make by picking options, so every combination fits.
- Always-on text: at most 10,000 characters of names and text in the largest game a player can pick. Craft's defaults take about 2,200 of it. Trackers don't count.
- Situational instructions: at most 100 in that largest game.
- Procedures: at most 25 in that largest game, Craft's editable ones included. The four built into every game don't count.
- Instructions in all: 200, the world's own and every choice's.
- Text of one instruction: 2,000 characters always on or for a tracker's rules, 1,000 situational, 10,000 for a procedure.
- Titles and triggers: 120 characters each.
- Player options: 9 in a game, Craft's 2 included, with up to 8 choices each.
- Option and choice names: 60 characters; descriptions 200; keys 60.
- Sections: up to 30, each name up to 40 characters.
At most 10 trackers are in a game at once, not counting the time, and a tracker has 1 to 8 fields. The full list of tracker limits is in tracker kinds.
The Instruction tester runs up to 20 tests a minute and 300 a day for each creator. The day resets at midnight UTC. See GM instructions.
Scripts and script cards
A world's scripts, and each run of one, are limited:
| What | Limit |
|---|---|
| Scripts in a world | 30 |
| A script's source | 64 KB |
description |
1,000 characters |
beforeNarrationTrigger |
500 characters |
afterNarrationTrigger |
500 characters |
| Time a run gets, its game calls included | 3 seconds |
| Memory a run gets | 16 MB |
| A result | 64 KB |
console.log output in a run |
16 KB |
Lookups in a run (every get(), each key of a getMany() and currentLocation(), found or not, and every file an include brings in) |
100 |
create() and update() calls in a run |
30 |
Files computed fields' load() reads in a run (apart from the lookups) |
1000 |
game.currentState.update() calls in a run |
20 |
| People brought into the current state in a run | 30 |
| People, trackers or details named in one change | 30 |
| Details on one person | 20 |
| A tracker's text field, a list item or its note, or a detail's text, in the current state | 160 characters |
| A tracker's or someone's name in the current state | 60 characters |
| A field's or detail's label, or the words someone is out of action in | 40 characters |
time |
80 characters |
purpose |
300 characters |
| Rolls, effects and reactions in a run | 40 |
| A card | 32 KB and 200 elements |
A card's own starting state |
4 KB |
| Actions on one script's card | 20 |
See defining a script and cards.
Dice
| Limit | Value |
|---|---|
| Dice groups and modifiers in one roll the player makes | 20 |
| Dice of one size in the dice builder | 20 |
| Dice a player's roll throws in 3D (more show as a flat readout) | 14 |
| Dice with a 3D model | d4, d6, d8, d10, d12, d20, d100 |
| Dice in one roll a script makes | 100 |
| Sides on a die a script rolls | 1000 |
See dice.
Images
| Limit | Value |
|---|---|
| A picture's prompt | 5,000 characters are kept |
| Free character portraits | 3 a day for each person |
| Images combined into one in the studio | 4 |
Generating and uploading through the CLI has its own daily caps, listed under the CLI below. See generating images and the studio.
Handbooks, flows and visual novels
| Limit | Value |
|---|---|
| Chapters in a handbook | 50 |
| A chapter's title | 120 characters |
| A chapter's text | 100,000 characters |
| A flow step's AI instruction | 2,500 characters |
| Pages in a visual novel | 2,000 |
| GM turns one visual novel export takes | 500 |
See handbooks, flow steps and visual novels.
Orbit
| Limit | Value |
|---|---|
| Steps in one reply (each step is one round of reading or changing things) | 50 |
| Time one reply can run | 20 minutes |
| Subagent tasks in one hand-off | 24 |
| Subagents working at the same time | 8 |
| Steps for each subagent | 20 |
See Orbit.
The CLI
| Limit | Value |
|---|---|
| Changes in one push | 500 |
| Size of one push | 25 MB |
| Images generated, per account per 24 hours | 50 |
| Reference images per generation | 3 |
| Size of an uploaded image | 10 MB |
| Images uploaded, per account per 24 hours | 50 (1,000 with a subscription) |
| Versions one history lookup shows | 20 by default, up to 100 |
See the Craft CLI.
Import and export
| Limit | Value |
|---|---|
| A zip you import | 50 MB |
| Changes one import makes | 20,000 |
| Files in one export | 10,000 |
See import and export.
Doing it well
- Out of project or game slots: delete what you no longer need, then delete it forever from the trash, or move to a plan with more slots.
- Too many files or folders: remove what isn't used, or fold small files into fewer, richer ones. A list of minor items often belongs in one file, not one file each.
- Too many file types: merge types that share most of their fields into one type with a field that tells them apart.
- Too many fields in a type: group related fields into object or list fields, and drop fields nothing reads.
- Over a GM instruction budget: make always-on rules situational where you can, move long steps into a procedure, merge procedures that run alike, and cut anything that repeats Craft's defaults. See GM instructions.
- Plan bulk work against the limits. Before adding hundreds of files or importing a large set, check how many the world already holds and how many the change adds.
Mistakes
- Deleting to make room, then still being blocked. A deleted project or game is in the trash and still counts. Delete it forever. See deleting a game.
- Splitting one thing into many files to dodge a field limit. It spends the file limit instead and scatters what the GM reads. Group the fields instead.
- Retrying a refused change unchanged. A limit doesn't lift on its own; the change has to get smaller, or something has to be removed first.