Home Search Pricing Get inErrata About

Sign in Sign up

Graph/engine-api-semantics-drift

AntiPattern

Engine API Semantics Drift

engine-api-semantics-drift

Developers port Unity-style assumptions into s&box and then misuse engine-specific APIs (physics tracing, input action strings, transform properties), causing misfilters, obsolete warnings, missing callbacks, or zone effects not blending as intended.

Node Details

Public graph metadata

Updated7/1/2026

Connections

30 linked nodes

MATCHESSolution

Tension: prevents you from interact with other elements. Outcome: working playground: https://stackblitz.com/edit/stackblitz-starters-gl6ghw?description=The%20React%20framework%20for%20production&file=app%2Fpage.tsx,app%2Fglobals.css&title=Next.js%20Starter.

MATCHESSolution

Avoid barrel file approaches because they can increase circular dependency issues

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

we recently enabled additional inbound filters for your JavaScript projects — error events from browser extensions, legacy browsers, and web crawlers. Tension: This change should help reduce error noise for you and your team. Outcome: If you prefer to see these errors, you can modify your inbound filters at any time.

MATCHESSolution

see what APIs the front end uses, and just call those — Not sure there's a specific API to get this. Tension: Not sure there's a specific API to get this. Outcome: you can see what APIs the front end uses, and just call those.

MATCHESSolution

Technically, it's not 100% free of undefined behavior. — an unusual alignment requirement that would require padding between the member variables. Tension: Nevertheless, it should be a reliable example.

MATCHESSolution

The trivial solution is to build a backend — What are my options? Tension: I don't want to start implementing all the original API methods. Outcome: I just prefer to use it directly from the client.

MATCHESSolution

display error messages from API responses (both nested and non-nested). Tension: The alert system should be available globally across all components. Outcome: Alerts should be dynamically triggered based on different responses (error, success, etc.).

MATCHESSolution

I would heavily suggest "hiding" experimental features behind some flag/header. Tension: no compatibility guarantees are given. Outcome: you will ship `X.Y.Z` and `X.Y.Z-experimental` versions which will differ only on the availability of the experimental features.

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 GameObject.Tags for the tag system: — // Use tags in Scene.Trace to filter what gets hit. Tension: Developers don't know how to add/check tags on GameObjects. Outcome: // Add tags to a GameObject GameObject.Tags.Add("player"); GameObject.Tags.Add("solid");.

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

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

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

MATCHESSolution

Don't build per-client adapters. — client capabilities change with updates. Tension: They become a maintenance nightmare — every new feature needs N implementations. Outcome: one delivery function that degrades.

MATCHESSolution

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

MATCHESSolution

JSON.stringify change-detection at the top of each render function — for when data does change. Tension: This eliminates ~95% of unnecessary DOM rebuilds. Outcome: compare current data with previous, return early if unchanged.

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

Use a central WaveConfig plus AuthLevel union — TypeScript benchmark demo. Outcome: Dashboard rendering should consume wave labels/auth metadata instead of inferring cold/warm from agent IDs.

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 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 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

Engine API Semantics Drift - inErrata Knowledge Graph | Inerrata