MOBILE WORKFLOW · OCTOBER 6, 2026
Schedule 1 mixing guide: check quantity and costs on mobile
This guide is a walkthrough of our website, with four live browser readbacks. It is not a game capture, a guaranteed customer offer, or a claim that this is the best recipe. Use standard mixing with Seeded Mixing off.
1. Build one recipe in the declared order
Open the calculator. Choose OG Kush under Base product. Leave Quantity at 1 and Base production cost at 0 while checking the recipe. Select each ingredient in the dropdown and tap Add ingredient once per step:
- Banana
- Cuke
- Banana
- Donut
- Donut
- Paracetamol
- Cuke
There are repeated ingredients on purpose. Three different names do not describe this seven-step recipe. Keep both Banana additions, both Donut additions and both Cuke additions in their original positions. Check the ordered list before interpreting Result. The Up, Down and Remove controls change that list; they are editing controls, not optional steps in this test.
At this baseline, Result must show one unit, ingredient cost $17.00, sell price per unit $98.00, batch cost $17.00 and batch profit $81.00. The final effect count is 8 / 8. If the baseline differs, stop here and inspect the chosen product and ordered ingredients rather than changing quantity to hide the discrepancy.
2. Read unit figures and batch figures separately
On a narrow screen the input panel and result panel appear in a vertical workflow. Scroll to Result after completing the inputs. Ingredients / unit and Base cost / unit describe one unit. The large Batch profit, Cost and Sell value numbers describe the quantity you entered. Compare like with like: a twenty-unit total should not be compared directly with a one-unit price.
With the same ingredients, enter 20 in Quantity. Keep production cost at zero for this checkpoint. The engine still gives $17 ingredient cost and $98 value per unit. The batch now costs $340 and has calculated value $1,960, leaving $1,620 profit before unentered production expenses. Quantity changes the totals; it does not add ingredients or change the eight final effects.
3. Enter production cost per unit, not per batch
The cost field is explicitly labelled per unit and optional. For our reproducible example, enter 5. This is a declared test input, not a measured production expense from the game. Do not enter the full twenty-unit production bill into this per-unit field.
Our arithmetic is batch cost = quantity × (ingredient cost per unit + entered production cost per unit). Thus 20 × ($17 + $5) = $440. Batch value = 20 × $98 = $1,960. Batch profit = $1,960 − $440 = $1,520. The $100 difference from the zero-cost checkpoint is 20 × $5. Sell value stays unchanged because entering your expense does not change the recipe's effect calculation.
Four checkpoints actually read from the live interface
We entered these four cases on the live website on October 6, 2026 and read the visible Result panel after each change. We also ran the same saved engine independently and checked the arithmetic. The recipe remained fixed throughout; each row changes only quantity and the optional production-cost input.
| Quantity | Production / unit | Batch cost | Batch value | Batch profit |
|---|---|---|---|---|
| 1 | $0.00 | $17.00 | $98.00 | $81.00 |
| 20 | $0.00 | $340.00 | $1960.00 | $1620.00 |
| 20 | $5.00 | $440.00 | $1960.00 | $1520.00 |
| 3 | $2.50 | $58.50 | $294.00 | $235.50 |
The last case checks a decimal input: 3 × ($17 + $2.50) = $58.50 cost, 3 × $98 = $294 value, and $294 − $58.50 = $235.50 profit. This is a separate UI checkpoint, not a rounded extrapolation from the twenty-unit example. The effect count stayed eight and unit value stayed $98 in all four readbacks.
What to check when your result differs
- Check Base product first. This article uses OG Kush only.
- Count seven additions and read their order. Duplicate names are separate steps.
- Check whether Quantity shows 1, 20 or another entered value.
- Check the per-unit production field. Zero means that expense is excluded; it does not establish that production is free.
- Compare the same unit or batch metric used by the relevant checkpoint.
If those inputs match but the result still differs, record the exact inputs and displayed figures. A different rules snapshot or game build may require a new test. We have not identified a precise game build for the source snapshot, so matching this tool's result does not establish agreement with every current save.
Questions answered by this test
Should I enter the base product's sale value as its production cost?
No. This field is for the expense you choose to include per unit. The base product's game value participates in the value calculation; it is not evidence of your production expense. Our test uses $5 as an explicit input.
Why did entering a cost change profit but not sell value?
The recipe was unchanged. Cost rose by quantity × the entered expense, while the saved engine's unit value stayed $98. At twenty units, adding $5 per unit reduced profit by $100.
Does changing quantity change ingredient order or effects?
It did not in our four declared cases. All used the same seven additions and returned eight effects. A new ingredient or reordered step is a different experiment; see the controlled order test.
Is $1,520 my actual in-game net profit?
It is this calculator's batch result after the entered costs. Customer quotes, equipment, packaging, wages and other unentered expenses were not measured here. The number cannot establish actual net earnings.
Evidence and limits
The saved audit records all inputs, four checkpoints, engine SHA256 and source commit. It uses our deployed engine adapted from the MIT-licensed Schedule1 Tools snapshot 74607081. This article adds the mobile workflow, live readbacks, unit-versus-batch checks, decimal-cost checkpoint, arithmetic and original diagram. The fixed competitor's product-first interface informed the workflow structure; its wording was not reused.
This is an independent fan website, not official or endorsed by the developer. The evidence concerns our calculator's visible behavior, not game performance or current customer demand.