RECIPE IMPORT · OCTOBER 7, 2026
Schedule 1 recipe: what a mix hash loads and leaves unchanged
We tested this website's live import interface and independently ran its saved decoder and mixing engine. These are calculator experiments under standard mixing, not game measurements or a guarantee of compatibility with every other tool.
A reproducible hash and its exact recipe
Open the calculator and expand Have a mix hash? For a clean baseline, set Quantity to 1 and Base production cost to 0. Paste this test hash into Current Schedule1 Tools hash, then select Load:
T0cgS3VzaDpIQUhEREtB
The decoded text is OG Kush:HAHDDKA. In this deployed rules snapshot, H is Banana, A is Cuke, D is Donut and K is Paracetamol. The ordered list becomes Banana → Cuke → Banana → Donut → Donut → Paracetamol → Cuke. Duplicate letters are separate additions, not a request to combine duplicate names.
Our live baseline displayed Mix loaded., seven ingredient steps, $17.00 batch cost, $98.00 sell value and $81.00 profit. Those figures use one unit and zero entered production cost. The same saved engine independently returned ingredient cost 17 and unit sell price 98. A successful load restores the recipe inputs; it does not establish that the recipe is optimal or that the current game gives identical results.
Why a hash can produce a different batch profit
We next entered Quantity 20 and Base production cost 5, then loaded the same hash with spaces before and after it. The status again said Mix loaded. The whitespace was trimmed, while quantity remained 20 and production cost remained 5. The displayed batch cost was $440.00, value $1,960.00 and profit $1,520.00.
The recipe hash contains no quantity or expense field in this accepted format. The interface retained the values already in those controls. Batch cost was 20 × ($17 ingredient cost + $5 entered production cost) = $440. Batch value was 20 × $98 = $1,960. Profit was $1,960 − $440 = $1,520. Every input here is declared; $5 is a test expense, not an observed in-game production bill.
For a comparison with another person's output, match product, full ingredient order, quantity, entered production cost and rules version. Matching only the hash can leave different batch totals because it does not overwrite the expense and quantity controls. Our mobile input walkthrough explains how to distinguish unit figures from batch figures.
Eight controlled import cases
The table shows the decoded text before Base64 encoding, except the malformed string which is supplied directly. Cost / value in accepted rows is the independently executed one-unit, zero-production-cost engine result. The saved audit also contains each exact encoded input.
| Case | Decoded text or input | Import | Unit cost / value |
|---|---|---|---|
| valid seven-step | OG Kush:HAHDDKA | Accepted | $17 / $98 |
| empty recipe | OG Kush: | Accepted | $0 / $39 |
| unknown product | Unknown:AH | Rejected | Previous recipe retained in live error tests |
| unknown ingredient | OG Kush:Z | Rejected | Previous recipe retained in live error tests |
| extra field | OG Kush:AH:20 | Rejected | Previous recipe retained in live error tests |
| twenty steps | OG Kush:AAAAAAAAAAAAAAAAAAAA | Accepted | $40 / $46 |
| twenty-one steps | OG Kush:AAAAAAAAAAAAAAAAAAAAA | Rejected | Previous recipe retained in live error tests |
| malformed | %%%not-a-hash | Rejected | Previous recipe retained in live error tests |
For the twenty-step row, the decoded ingredient field is twenty A characters; for twenty-one it is twenty-one. The decoder can recognise twenty-one ingredients, but the UI rejects it at the twenty-step boundary. This distinction matters: recognisable codes alone do not make an input acceptable to the current website.
We loaded the valid seven-step baseline first, then tried unknown product, unknown ingredient, extra field, twenty-one steps and malformed input. All five live failures displayed: Use one valid current-format hash with at most 20 ingredients. Legacy seeds are not supported.
In every failure readback, the previous seven-step recipe and $17 / $98 / $81 result stayed on screen. The identical error does not distinguish the five causes; our deliberately controlled inputs identify which boundary each test exercised.
An empty recipe is accepted, but it is not a free-production claim
The hash T0cgS3VzaDo= decodes to OG Kush:. It is a known product followed by an empty ingredient field. The website accepted it and changed the list to zero ingredient steps. That is different from a malformed hash.
With the retained quantity 20 and cost 5, the live display showed $100 cost, $780 sell value and $680 profit. The engine's zero-addition unit value was $39. Thus cost = 20 × (0 + $5) = $100; value = 20 × $39 = $780; profit = $780 − $100 = $680. Zero additions mean no mixing-ingredient cost in this model, not zero production expense.
We also loaded the twenty-Cuke test with those same retained controls. It showed twenty ingredient steps, $900 cost, $920 value and $20 profit. Independent unit figures were $40 ingredient cost and $46 value, giving 20 × ($40 + $5) = $900 and 20 × $46 = $920. This is a boundary test, not a recommended recipe.
Questions to ask before using an imported result
Can I paste Copy result text into the hash field?
The accepted format in this test is an encoded product-and-ingredient string. Copy result is a human-readable report in the deployed source; it is not a hash-export control. This site currently provides import but does not present a recipe-hash generator. Keep the report and the encoded input distinct.
Does a displayed profit mean the import succeeded?
No. Our five failed imports kept the old profit visible. Read the import status and then inspect the ordered list. The numbers alone do not prove a new recipe was loaded.
Does loading a hash reset my costs?
It did not in the declared live tests. Quantity20 and cost5 survived the valid, empty and twenty-step imports. Set them explicitly before comparing batch results.
Will an old seed or another website's hash work?
That was not established. The live error specifically excludes legacy seeds. We tested this deployed decoder and constructed inputs only; a label referring to a format is not proof that all current external generators share it.
Evidence, scope and original work
The complete audit records eight constructed inputs, exact hashes, decoder results, engine outputs and the live UI checks. The engine source is the MIT-licensed Schedule1 Tools snapshot74607081; its SHA256 is included in the audit. The independent experiments, preserved-input comparison, boundary cases, original flow diagram and calculation explanations were prepared for this article. The fixed benchmark's Mix Hash field suggested the question; its prose was not reused.
This independent fan tool is not official or endorsed by the developer. We did not measure customer offers, production time, game-build compatibility or real earnings. The imported inputs use a fixed source snapshot and Seeded Mixing is outside its scope.
Grouping checked recipe results
See the checked recipe collection for complete inputs and base-specific results.