MIX / 01 · Calculator

RULE CHECK · OCTOBER 8, 2026

Schedule 1 wiki: check the rules behind your mixing result

Check the rule snapshot before trusting a recipe result. This calculator uses standard mixing: 7 base products, 16 ingredients, up to 20 additions and 8 final effects. Seeded save-specific rules are not included. Start with an empty OG Kush recipe: this audited snapshot returns $39, then $46 with Cuke alone.

This is a mixing-focused rule reference, not a complete encyclopedia of the game. Its practical question is why a recipe from another reference can disagree with this calculator. The figures below come from independent execution of the saved engine and named checks on the public interface, not a game session.

A three-checkpoint fingerprint for every product

We executed 21 inputs: each of the seven products with no additions, Cuke alone and Banana alone. These are three independent recipes per row. Do not add Banana after Cuke when reproducing the last column. Every run used standard mixing; the quoted figures are calculated unit sell values before any customer negotiation.

ProductStored base valueNo additionsCuke onlyBanana only
OG Kush$35$39$46$50
Sour Diesel$35$40$48$47
Green Crack$35$43$43$57
Grandaddy Purple$35$44$52$51
Meth$70$70$85$84
Cocaine$150$150$183$180
Shrooms$65$65$79$78

The complete seven-row baseline and Cuke columns were also checked through the public interface on October 8. The Banana column was run independently against the saved engine. Each single-addition recipe costs $2 in this snapshot; an empty recipe has no mixing-ingredient expense. Base production expense was entered as zero for the interface checks, so these are not fully costed earnings.

Use the differences to locate a mismatch

Subtract the empty result from the Cuke-only result. In table order the differences are $7, $8, $0, $8, $15, $33 and $14. For Banana alone, the differences are $11, $7, $14, $7, $14, $30 and $13. These two vectors are derived directly from the 21 recorded outputs; they are a reproducible diagnostic, not a claim of a unique signature.

If an empty recipe already differs, adding a long ingredient list hides the earliest disagreement. Compare the product value, starting effects and rounding first. If the empty recipe agrees but one single-addition result differs, compare that ingredient’s default effect and transformation rule. Matching all three checkpoints still does not prove that every later interaction is identical; it only narrows what you have checked.

Green Crack illustrates why both the base and transformed columns matter. Its empty and Cuke-only values are both $43, whereas Banana alone produces $57. OG Kush instead moves from $39 to $46 or $50. The same $2 ingredient expense does not imply the same price change across products. A checker that substitutes one universal increment for every product would fail this matrix.

Check the same rule inputs before comparing resultsMatch product + mode + ordered inputsCheck empty recipe → Cuke → Banana separatelyCompare effects → unit price → entered costsA matching checkpoint is evidence, not a version guarantee
Original diagnostic flow for the audited standard-mixing snapshot.

The stored base value is not the empty result

All four weed products have a stored base value of $35 here. Their empty results are $39, $40, $43 and $44 because their initial effects differ. The engine calculates round(base value × (1 + sum of final effect multipliers)).

For OG Kush, Calming contributes 0.10: round(35 × 1.10) = round(38.5) = 39. Sour Diesel starts with Refreshing at 0.14: round(35 × 1.14) = 40. Green Crack starts with Energizing at 0.22: round(35 × 1.22) = 43. Grandaddy Purple starts with Sedating at 0.26: round(35 × 1.26) = 44. Inputs and rounding come from this engine, not inferred current-game prices.

Meth, Cocaine and Shrooms have no starting effects in this snapshot, so their empty values equal their stored values: $70, $150 and $65. This gives another checkpoint before you investigate ingredient order. A $35 product field and a $39 displayed result are compatible; comparing them as though they were the same field creates a false discrepancy.

Identify the snapshot without inventing a game build

The adapted source commit is 74607081cd79b8ad2052b75a1d40dd367cb29cb7. The tested app.js SHA256 is 3aac8856a0d22f3c21cd29c29ad9dc23a07346b46708f004b18fa29d57f3fb08. A commit names source history; a file hash identifies the exact audited bytes. Neither supplies an exact game-build number.

This file contains 34 effect definitions, but a finished recipe is capped at 8 effects. The definition count is a vocabulary inventory, not permission to pack all of them into one mix. The interface admits 20 ingredient additions; repeated ingredients remain separate additions. These two limits describe different objects.

Which mode does this reference cover?

Standard mixing only. The public page states that Seeded Mixing is off, and the audited calculation has no save-specific seed input. If your comparison relies on a save-specific rule set, this table cannot validate it. Adding an ingredient in another order is also a different input, not a reliable test of the same recipe.

Questions to resolve before replacing a recipe

Does a mismatch prove the other reference is wrong?

No. First match the mode and source version, then compare the checkpoints. We have not tested every game build or every other calculator. Record the first differing input and output instead of declaring a universal winner.

Does a newer article guarantee newer rules?

The date alone does not identify the calculation rules. Use the source identifier and the reproducible outputs to establish what was actually checked. An article date and an engine version are separate evidence.

What should I save with a disputed result?

Save the product, ordered additions, mode, final effects and calculated unit value, plus the source version if available. Keep entered production cost and quantity alongside them. That record lets you separate a rules mismatch from a different cost input.

Audit record and limits

The complete audit contains all 21 inputs and outputs, starting product data, ingredient names, the effect-definition count and source identifiers. The checkpoint matrix, difference vectors, base-versus-empty calculations and diagnostic flow are original analysis of these executions. The reviewed benchmark explains individual rules and prices; we did not reuse its wording or claim this diagnostic exists nowhere else.

Numbers here describe this website’s saved standard-mixing engine. We did not measure completed sales, hourly income, customer acceptance or seeded-save behavior. This is an independent fan reference with no official game endorsement.

From quote to retained receipt to marginQuote × (1 − deduction) = retained receiptRetained receipt − unit cost = unit marginUnit margin × sold units = scenario marginHypothetical deductions are not verified game commissions
Original worksheet flow. Supply observed inputs before treating a scenario as a sale record.

Effect count and value

Same effect count, different calculated sell valuesOG Kush · exactly two additions2 effects39–643 effects45–84Two effects at 64 exceed three effects at 45Range maxima set bar length; ranges are engine sell values
Original range comparison: the bars show each group’s maximum, while labels give its minimum and maximum.