E.g.
- 1-4 bits for the piece class to move.
- 3 bits for the column of the destination
- 1-3 bits left over for disambiguation. E.g. Column
That's perhaps a bit too much optimization for a troll project. But fun nonetheless.
No no, not where all the pieces are, but I want you to send me everything about where the board is in space, it's material, dimensions, weight, etc...
If only we had known.
I've used Morse code because the original theories of how this was done was that Hans used Morse, so I used it as well. - to stay as close as possible to the actual leading theory and not invent my own method.
I considered abstracting the decoder, so it's not a hard-coded `MorseEncoder()` but just an IMoveEncoder interface where you can inject any encoder that takes a move as input and returns a pattern output
I also thought - Morse is a "common standard" - it would possibly be easier to learn and remember than a custom made encoding scheme
wrote this to combat the inefficiency. transcodes chess notation into a new code which leverages N independently vibrating beads
Reductive Hammond coding scheme, or something.