It is not a requirement to provide a conductive path to the person though. The patterns (glyphs as we call them) are detected and tracked regardless of whether they are being touched. However, when there is a conductive path to the person, the system detects that which provides another input vector.
This screams for compatibility with 3d printers. eg: design a piece to be "absorbed" by a LEGO brick (2x4, duh!), and design a capacitive pathway for "two buttons" a-la: https://a.co/d/f7wm3GA
3D print your goblin army, snap it to the base, touch the sword arm to attack, the shield arm to defend, etc. light up the base via capacitive to 0/1/2 inputs and you're set!
The Unity SDK is C# and slots right into the typical Unity patterns for touch input.
Two contact types are provided:
Finger – Representing a single touch point, e.g, a finger
Glyph – Representing a tangible object
For each contact, you get ID, Position, and Phase. For Glyphs, you also get orientation and touched status, as in the system knows whether the object is being touched or not. There tunable parameters for the tracking system as well.
For event systems (e.g., menus, etc), BoardUIInputModule in provided in place of Unity's default InputSystemUIInputModule.
Please reach out if interested to develop: https://board.fun/pages/developers
My colleague has some discussion here about 3D printing pieces: https://news.ycombinator.com/item?id=45754851