Enter the arithmetic result, then use the new light. The Calculation module’s last key depends on that light and whether your original result is even or odd. The result and the finishing key are two different instructions.
Jump to the final-key table ↓Finish the sum. Then finish the panel.
Enter the result.
Read the complete equation, including its operator. Calculate the result and enter those digits on the panel. Check each printed key rather than assuming a familiar keypad layout.
Choose the final digit.
After the panel changes, report the light color. Classify the original arithmetic result as even or odd, find the matching entry below, and press that final digit.
Read the full equation.
Keep the numbers and operator together. A missing sign changes the result before any manual lookup happens.
Calculate and enter it.
Label the number as the “result.” Confirm its digits and locate their actual keys. The recorded keypad is not arranged like a standard calculator.
Wait for the new state.
Report the light that appears after the result is entered. Do not reuse another panel’s light or an earlier observation.
Keep the original result for parity.
An even integer is divisible by two; an odd integer is not. Classify the arithmetic result, not its digit count or the eventual finishing key.
Relay and press the final key.
Mute uses the manual to signal the digit; Deaf relays it to Blind. Confirm what happened after the input before moving on.
Light + result parity → final key.
Use this only for the second stage. Each cell is the digit printed on the key, not a physical key position and not another calculation.
| New light | Even result | Odd result |
|---|---|---|
| Red | 5 | 3 |
| Yellow | 0 | 7 |
| Green | 9 | 2 |
| Blue | 1 | 0 |
The captured table covers four light colors and integer parity. It does not establish how a future version handles unlisted colors, non-integer results or other states. Use the current manual if your panel does not fit.
Keep both numbers in the callout.
These examples combine the manual table with Stumpt’s Demo transcript. The diagrams explain the reported inputs; they are not interactive calculators or screenshots of the keypad.
59 + 8 = 67
67 is odd. In the Yellow row, the odd-result column gives 7. The final instruction is “press 7,” after entering 67 in stage one.
The transcript reports 59 + 8, an entered result of 67, then a Yellow light. At 18:10 the team calls seven; at 18:35 they acknowledge finishing the attempt and explain the two-stage process.
57 + 30 = 87
87 is odd. In the Blue row, the odd-result column gives 0. The final instruction is “press 0,” after entering 87 in stage one.
The transcript reports 57 + 30, an entered result of 87 and then a Blue light. Around 19:47 the team calls zero, acknowledges the input and moves on to Direction. This is a reported module transition, not independent frame-by-frame verification.
An earlier attempt with 57 + 24 = 81 breaks down during the zero callout and ends in failure. That segment is useful for diagnosing communication, not as evidence of a successful solve.
Which stage went wrong?
We entered the answer to the sum. Why isn’t it finished?
The recorded module has a second stage. Read the new light and combine it with the original result’s parity to obtain the final key. Do not keep entering the arithmetic result.
Is “odd or even” about the last key?
No. Use the arithmetic result. In the second example, 87 is odd and Blue selects final key 0. The fact that 0 is even does not send you back to the even column.
Do I press a normal calculator’s key position?
Locate the required digit on this panel. The recorded player has to find the digits because the keys are not in the familiar order. A correct number spoken aloud still needs a correctly identified key.
The team has no agreed signal for zero.
Decide on a distinct signal and confirm its meaning before playing. The Demo transcript contains confusion between zero and ten; that discussion does not change a 0 in the manual into a 10.
Does a wrong key reset the whole module?
The sources used here do not establish a universal reset behavior. Recheck whether the panel is showing the equation or the later light state before deciding what to enter next.
A captured table and two recorded calls.
The eight final-key entries are readable in Cob’s multi-view Demo recording at 06:33. The video displays v0.1.8. The manual places even results above odd results and colors Red, Yellow, Green and Blue across the columns; this page rearranges those same entries into one row per color.
The examples use Stumpt’s Demo recording as represented in the collected transcript. Spoken acknowledgements support the reported outcome; this page does not claim an independent frame-by-frame check of those two inputs.
We have not playtested the module or verified this mapping against the full release. For the shared reading process, open the manual overview; for another panel, use the module directory.
Manual frame and transcript checked September 9, 2026. Demo scope retained throughout.