game-feedback-mandate-unity
Game Feedback Mandate: Unity engine mechanics (engine-specific additions)
Section titled “Game Feedback Mandate: Unity engine mechanics (engine-specific additions)”Extends the engine-agnostic rules/game-feedback-mandate.md (theonekit-designer) with the Unity mechanism this kit ships for each feedback channel.
- DOTween is banned kit-wide. LitMotion is the only approved tween library (zero-alloc tweening is mandatory) — do not reach for DOTween even if present.
- An
ISystemnever calls a tween,AudioSource,MMF_Player, or haptic API directly — all are Mono-only/main-thread, throw under Burst. Raise a feedback event from ECS; a Mono-side bridge consumes it (see the DOTS core implementer agent’s “Feedback from ISystem code” section, shipped with the optional dots-core module). - Haptics: call
MoreMountains.NiceVibrations.Haptics.Haptic(HapticTypes.X)unconditionally, never#if UNITY_IOS || UNITY_ANDROID-guarded — degradation is automatic — and fire it in the same frame as its paired visual. - Every runtime object a bridge spawns for feedback comes from
IObjectPoolManager, neverInstantiate/new GameObject. A one-shot burst isEmit(EmitParams, n)on a RESIDENTParticleSystem, ≤200 particles, not a pooled prefab (carve-outs:mono-pool-spawn-unity.md§ VFX carve-outs). - Library code (
rules/library-third-party-decoupling.md): the DOTS/Mono seam above is anI*Bridgeinterface using only platform/first-party types; a consumer without the bridge package degrades to no feedback rather than failing to build.
Full channel-to-mechanism table: t1k-unity-rendering-feel-juice § “Feedback channel → Unity mechanism”.
Full detail
Section titled “Full detail”Haptics degradation table, opt-out API, timing rationale, mobile performance budget, verification tooling: docs/game-feedback-mandate-unity.md.
Related
Section titled “Related”rules/game-feedback-mandate.md (theonekit-designer, parent) · rules/library-third-party-decoupling.md (core) · mono-pool-spawn-unity.md