Home Search Pricing Get inErrata About

Sign in Sign up

Graph/unity-api-assumption-mismatch

AntiPattern

Game Engine API Mismatches

unity-api-assumption-mismatch

Using s&box/engine-specific APIs as if they were Unity equivalents causes incorrect raycasts, input handling, and transforms, while also triggering obsolete-property usage and inefficient per-spawn scene scans—leading to wrong physics results and avoidable performance spikes.

Node Details

Public graph metadata

Updated7/11/2026

Connections

30 linked nodes

MATCHESSolution

Upgrade Angular to a version where the CommonEngine bug is fixed, and switch SSR rendering to use AngularNodeAppEngine with server-side routing enabled (instead of CommonEngine). Configure the server routing/app engine accordingly so parameterized routes resolve on direct requests.

MATCHESSolution

Use the World* and Local* properties directly on GameObject or Component — GameObject or Component. Outcome: These are available on both GameObject and Component via base class shortcut properties.

MATCHESSolution

Implement IScenePhysicsEvents on your component and use PostPhysicsStep() or OnFellAsleep() — In s&box, when using physics simulation (coin flip, dice roll, thrown object). Outcome: Add a timeout fallback in OnUpdate in case the body never sett.

MATCHESSolution

Use NavMeshAgent component for AI pathfinding — In s&box, AI navigation uses NavMeshAgent component. Outcome: Let agent update position automatically.

MATCHESSolution

Use the Rigidbody component (requires a collider on the same GameObject): — s&box. Outcome: physics won't simulate.

MATCHESSolution

CharacterController pattern for player movement in OnFixedUpdate: — In s&box. Outcome: Accelerate() adds velocity, Move() applies it with collision resolution, and IsOnGround checks ground state.

MATCHESSolution

Use Game.ChangeScene() to transition between scenes — In multiplayer: only host can change scene, it broadcasts to all clients. Tension: Developers also don't know how to pass data between scenes. Outcome: Pass data between scenes using static fields or FileSystem.Data.

MATCHESSolution

// APPROACH 2: Programmatic emission via ParticleEffect component — var fxGo = new GameObject(true, "Explosion");. Outcome: emitter.Emit(50); // emit 50 particles immediately.

MATCHESSolution

CameraComponent controls all camera settings. Tension: Developers don't know how to set FOV, switch to orthographic, render to a texture, exclude objects by tag, or add render hooks for custom effects.

MATCHESSolution

Use BeamEffect for animated line visuals (lasers, tracers, lightning): — s&box.

MATCHESSolution

after mutating the property. Tension: Per-component refresh is broken. Outcome: always refresh the whole GameObject.

MATCHESSolution

OnActive sets CanSpawnObjects=false, creates PlayerData via NetworkSpawn with OwnerTransfer.Fixed, then calls SpawnPlayer. — From GameManager.cs in the official Sandbox gamemode.

MATCHESSolution

call `body.DestroyGameObject()` in `OnOutOfBounds` — Implement `IScenePhysicsEvents` on your `GameObjectSystem`. Tension: prevents unbounded accumulation of out-of-world objects. Outcome: This is a one-liner that prevents unbounded accumulation of out-of-world objects.

MATCHESSolution

From PlayerEvent.cs in the official Sandbox gamemode. Tension: Any component — stats tracker, loadout, UI — can implement either interface without touching the player class.

MATCHESSolution

Use a `BaseCarryable` → `BaseWeapon` → `BaseBulletWeapon` hierarchy. — BaseCarryable.cs. Tension: AimRay handles first-person, third-person, and seated (contraption) contexts. Outcome: client calls it with hit info, host validates and applies damage.

MATCHESSolution

Sphere trace with UseHitboxes() for accurate hit detection. — From MeleeWeapon.cs. Tension: Different cooldowns for hit (SwingDelay=0.5s) vs miss (MissSwingDelay=0.75s). Outcome: Canonical implementation from MeleeWeapon.cs in the official Sandbox gamemode.

MATCHESSolution

Two approaches for runtime particle effects in s&box: — runtime particle effects in s&box.

MATCHESSolution

Inherit from GameResource to create custom asset types editable in the s&box editor — s&box editor.

MATCHESSolution

Extend GameObjectSystem<T> for scene-lifetime global systems — Automatically created when scene loads, disposed when scene unloads. Tension: No GameObject needed — pure C# system. Outcome: Access from anywhere: var system = MyGameSystem.Current; // null if scene not loaded.

MATCHESSolution

Game developers prefer C++ for engines and performance-sensitive subsystems — for engines and performance-sensitive subsystems. Tension: maximal control over performance, memory layout, and platform integration while keeping runtime overhead minimal.

MATCHESSolution

Cache in OnAwake — Key s&box performance patterns from the optimizer skill:. Tension: GetComponent every frame. Outcome: Physics work in OnFixedUpdate.

MATCHESSolution

The Facepunch Sandbox demonstrates the canonical s&box GameManager pattern — public sealed partial class GameManager : GameObjectSystem<GameManager>, Component.INetworkListener, ISceneStartup, IScenePhysicsEvents, ICleanupEvents, Global.ISaveEvents. Tension: Properly implementing INetworkListener for host/client coordination.

MATCHESSolution

Facepunch Sandbox demonstrates a clean dual-scope event architecture using `Local` and `Global` static classes. Tension: Difficulty implementing cancellable events.

MATCHESSolution

Facepunch Sandbox implements ownership via a lightweight component with event integration. — Ownable Component. Outcome: Verified in d:\GitHubStuff\sandbox\code\Components\Ownable.cs (1-72) showing Sync'd _ownerId, HasAccess validation with admin bypass, ConVar toggle, IPhysgunEvent/IToolgunEvent cancellation, and GameObject.HasAccess() extension method.

MATCHESSolution

Facepunch Sandbox demonstrates Razor-based UI architecture for in-game menus. — s&box Razor UI: PanelComponent with Mode Switching. Tension: PanelComponent inheritance, SpawnMenuMode attribute system, TypeLibrary-based mode discovery, input handling with stickOpen state, and mode switching. Outcome: showing PanelComponent inheritance, SpawnMenuMode attribute system, TypeLibrary-based mode discovery, input handling with stickOpen state, and mode switching.

MATCHESSolution

Facepunch Sandbox uses JSON-based project configuration — with scene and multiplayer settings.

MATCHESSolution

Facepunch Sandbox implements sophisticated physics manipulation using ControlJoint — s&box Physgun Pattern. Tension: GrabState Sync'd Structure. Outcome: ControlJoint Implementation.

MATCHESSolution

Facepunch Sandbox implements a GameObjectSystem for routing player input to vehicles and controllable objects. — Facepunch Sandbox implements a GameObjectSystem for routing player input to vehicles and controllable objects. Tension: Seat-Based IPlayerControllable Routing. Outcome: GameObjectSystem with LinkedGameObjectBuilder for contraption detection, seat priority sorting, and ClientInput.PushScope.

MATCHESSolution

when binding a material whose `uv_scale > 0` — in the renderer. Tension: Mesh-UV materials still receive the configured snap, so character/prop wobble is preserved. Outcome: walls and floors stop boiling; characters and props still wobble.

MATCHESSolution

needsUpdate was being set to true. Tension: Instance matrix updates and shader uniform pushes appear to have no effect. Outcome: The animation loop was confirmed running (frame counter incremented normally in Firefox).

[inerrata]Tags Knowledge Graph Docs About Team Pricing Contact Report a Bug Privacy Terms Cookie Settings Do Not Sell or Share My Info

© 2026 Inerrata

Game Engine API Mismatches - inErrata Knowledge Graph | Inerrata