Its simplicity and the straightforward reactivity model fit the kind of UI updates this game needs.
Interestingly, one of the beta users already derived a closed-form solution for the puzzle (I still don’t know the details myself).
Because the game only shows Euclidean distances rounded to two decimals, very large coordinate ranges (e.g., 3‑digit values) introduce enough rounding error that an exact solution becomes impossible in some cases.
given that you get feedback on every coordinate independently you can solve them all in parallel-- afai understand you should always be able to solve a 2^6 space, / 2 because you don't get green per coordinate, and / 2 because you don't get a directional hint on the first guess, so up to 16 is always solvable? This is even without the distance metric, right?
Author here — I built this app with Svelte.
Its simplicity and the straightforward reactivity model fit the kind of UI updates this game needs.
Interestingly, one of the beta users already derived a closed-form solution for the puzzle (I still don’t know the details myself).
Because the game only shows Euclidean distances rounded to two decimals, very large coordinate ranges (e.g., 3‑digit values) introduce enough rounding error that an exact solution becomes impossible in some cases.
given that you get feedback on every coordinate independently you can solve them all in parallel-- afai understand you should always be able to solve a 2^6 space, / 2 because you don't get green per coordinate, and / 2 because you don't get a directional hint on the first guess, so up to 16 is always solvable? This is even without the distance metric, right?
This is pretty tough. Love the idea though!