Skip to content

Desuq Cafe
Documentation menu

Touch, Consent, and Replay

Touch zones

A touch zone is a region of a strand or garment that an author paints by hand in Unity’s Scene view, using a brush tool that shows a live heatmap of what is currently painted. A grabber component points at a set of touch zones and a specific zone within it, and that is what makes a piece of hair or cloth actually grabbable at that spot. Painting by hand on the real mesh is the intended path, since it can see the avatar’s actual shape in a way a script-based selection cannot.

Every touch zone carries its own consent rule, independent of every other zone on the same avatar. The available rules run from fully open (anyone may grab it, a reasonable default for a casual headpat zone), through owner-only (only the avatar’s own owner may grab it) and keyed (the owner, or anyone holding a matching granted key), to fully closed (no one may grab it at all). An author sets the more restrictive rules on intimate zones by default. That is the wholesome-first convention the whole package is built around, not an afterthought bolted on top.

Consent is not a one-time check at the moment a hand reaches in. It is re-checked every single frame a grab is held. If permission is revoked partway through a hold, for example because a relationship changes or a key is taken away, the grab releases immediately and neutrally. It does not fling, snap, or leave the cloth stuck at an odd pose. That per-frame recheck is what makes consent feel like a real safety property in a shared space rather than a gate you only pass once.

Deterministic, bitwise-identical replay

Weft’s solver is deterministic: given the exact same starting state and the exact same sequence of inputs, it produces the exact same result down to the bit, every time. That means a recorded grab or touch can be replayed later and reproduces the original motion exactly, not just approximately.

This promise is intentionally scoped. It holds for the same build, the same platform, and the same solver settings as the original recording. It is not a promise that a recording made on one platform will replay identically on a different one, that is a future goal, not something Weft claims today. Within that scope, though, the guarantee is real and proven by the package’s own test suite across every major feature the solver supports, not just a simple case.

That combination, plain-language consent rules plus a genuinely reproducible replay, is what makes Weft’s touch model suitable for more than a single local player: recorded touch can be sent over a network, checked in an automated test, or driven by tooling, and it will reproduce faithfully within that same-build, same-platform scope.

Where to go next