Appearance
Open questions
These are unresolved implementation details, grouped by the part of the system they affect. No final choices are implied by examples elsewhere in the wiki.
Hardware and geometry
| Question | Related page |
|---|---|
| Which ESP32-class main controller and development board? | Base Board hardware |
| Can the chosen CH32 board support seven ADC inputs alongside buses, chain, robber, and debug pins? What is the exact allocation? | Smart Hex hardware |
| What excitation, ADC reference, logic rails, and level compatibility are required? | Sensing and wiring |
| Which resistor IDs and non-overlapping tolerance bands identify pieces? | Resistor registry |
| Which contacts, conductive pads, springs, or pogo pins should be used? | Playable Pieces hardware |
| What magnet geometry and alignment arrangement works for each piece? | Playable Pieces hardware |
| How do road/building ownership, boundary sensors, and orientation cover all 19 hexes? How is the 15-road-channel deficit resolved? | Geometry |
| Which prototype positions are actually sensed, and how are global IDs assigned? | Board model |
| What OLED mechanical mount accommodates module variation? | Smart Hex hardware |
| Which Raspberry Pi and Waveshare display, interface, supply, and kiosk mount? | Display Unit hardware |
| What power distribution topology, wire gauge, load budget, and runtime are achievable? | Power |
| What charging current and load/charge arrangement suits the owned battery? | Power |
Firmware and communication
| Question | Related page |
|---|---|
| Which CH32 language, toolchain, and programming/debug hardware? | Hex software |
| How do boot addressing, CHAIN levels, assignment acknowledgment, and recovery work? | Protocol |
| What are the final I²C speed, framing, commands, CRC, retries, limits, and version negotiation? | Protocol |
| Should sensor changes be polled or signaled? How are coherent snapshots and stale data handled? | Base Board software |
| Which filtering parameters, calibration ownership, and storage strategy work reliably? | Calibration |
| What bootloader/IAP design can fit and recover interrupted writes? | Firmware updates |
Game and applications
| Question | Related page |
|---|---|
| What language and execution location should the game engine use? | Game engine |
| Where do web assets and the API run, and what local-network/internet assumptions apply? | Software architecture |
| What authentication, joining, player binding, and reconnection behavior are needed? | Mobile Web App |
| How are game persistence, duplicate commands, recovery, and physical confirmation handled? | Game engine and reconciliation |
| What exact ruleset, licensing, branding, and product positioning apply? | Goals |
The documentation website is publicly hosted with Sites. Hosting the actual game applications remains a separate question; see wiki hosting.