CaveCrafterGuide 04 · Simulation
Plan the batch from end to end
Simulation calculates what your factories produce together, what they consume from each other and what is left to sell. Any missing materials become required purchases. The result represents the selected batch, not a day of production.
Configure factories and levels
Simulation opens in the Game view, with factory images. Executive presents the same plan in a different visual layout. Changing the view does not turn the batch into a daily estimate.
- Configure the five columns and adjust the number of active factories in each row for the scenario you want to evaluate.
- Choose a starting set of levels: All level 1, All max or My factories. Use Custom to explore individual levels.
- Adjust each factory's level using the selector in its box. To others copies that level to the other active factories in the same row and column, without changing another occurrence of the token or your My factories setup.
- Enter the final products' cycles. Factories supplying other active recipes will have their cycles calculated automatically.
Custom lets you keep individual levels. When you change a factory to a level different from its saved setting, this mode is selected automatically; if all active factories match My factories again, that option is selected again. The same factory type can have different levels in different columns without changing your general setup.
Why do some rows have automatic cycles?
If another active recipe uses a token, it is an intermediate in the batch. The engine adds up demand for that resource across all columns and calculates how many whole rounds of its factories are needed to meet it.
The capacity of one round is the sum of the output per cycle from all active factories of that token. They may have different levels; in this automatic stage, they run the same number of rounds. The total number of executions also takes the active factory count into account.
Hypothetical example: three factories meeting the same demand
Suppose three factories produce 4, 6 and 10 units of A per cycle respectively. Together, they produce 20 units in one round. If the rest of the batch needs 45 units, 3 rounds are required.
The group produces 60 units, consumes 45 internally and has 15 left over. Each factory ran 3 cycles, totaling 9 executions — not 3 for the entire group.
This shared production comes from the factories configured in the simulation. The planner does not automatically read your actual in-game or wallet inventory.
Final products, surplus and required purchases
The engine classifies tokens across all columns, not just the adjacent row. Production supplies the batch's own recipes first. Only the remaining balance counts as a sale.
| Category | Meaning |
|---|---|
| Final products | Produced tokens that are not used by another active recipe. They are the production goals of that batch. |
| Surplus | The excess of intermediates after meeting internal consumption. These units are also considered for sale. |
| Required purchases | Missing quantities, including inputs whose factory is not active in the scenario. |
The Summary filters let you see all items, purchases only, surplus only or final products only. They change the displayed list; they do not remove the other categories from the calculation.
Hypothetical example: a sale, a surplus and a purchase
The batch produces 30 units of A and consumes 25. It also produces 2 units of a final product and needs to buy 4 units of B. If A sells for 1 COIN, each final product for 20 COIN and B costs 2 COIN, revenue is 5 + 40 = 45 COIN.
With 6 COIN of power in the batch, the result is 45 − 8 − 6 = 31 COIN. The 25 units of A used internally do not appear as a sale and are not charged again as a purchase.
The sales shown in rows and columns are parts of the batch's sales. Use the Summary total to evaluate the whole; do not add those subtotals to the result again.
Use the combination suggestions
Find the best combinations opens suggestions that explore blueprints in columns 2 through 4 and factory choices in column 5, while keeping column 1's configuration. Each candidate is compared using the whole batch's result, including purchases, sales and power.
If you have already configured columns 1 through 4, use the option in the column 5 header to search for combinations only in that column. The earlier columns' configurations stay in place; automatic cycles may change to supply the new demand.
Examine the values before using Apply. The search is limited and heuristic: it compares candidates but does not guarantee the best result among every possible combination. A suggestion also depends on the prices and parameters used at that time.
A batch is not a schedule
Simulation calculates required quantities and cycles. It does not schedule each factory's start, estimate the full completion time of its dependencies or limit the batch to the hours in your day. Daily playing time is used in Profit Loss's daily estimates.
To interpret the result correctly, confirm that the factories and levels represent the intended scenario, that the power cost is filled in and that all required purchases are acceptable. Then consult the batch-balance methodology to check the formulas.