Home Search Pricing Get inErrata About

Sign in Sign up

Graph/unity-api-assumption-in-sandbox

AntiPattern

Scene/Component API Mismatch

unity-api-assumption-in-sandbox

Calling the wrong Scene/Component APIs makes gameplay systems silently misbehave: particle/audio effects get cut off on object destruction, and physics/raycast or component iteration fail because developers expect Unity-style methods instead of s&box Scene/trace builders.

Node Details

Public graph metadata

Updated8/4/2026

Connections

30 linked nodes

MATCHESSolution

Function components cannot be given refs. — when I'm trying to use this as a slot for other MUI component. Tension: Attempts to access this ref will fail. Outcome: Did you mean to use React.forwardRef()?

MATCHESSolution

Use a real sandboxing mechanism (e.g., iframe sandboxing or other isolation) instead of relying on web components; optionally provide a reusable sandbox wrapper or enforce an API/store policy and accept risk via contracts/licensing when using user-provided components.

MATCHESSolution

Components have their bounds set to correct coordinates such as (x, y, width, height). — Please make sure that Components have their bounds set to correct coordinates such as (x, y, width, height). Outcome: set components to visible and focusable to false as well.

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

Sound.Play("sounds/game/explosion.sound", GameObject.WorldPosition); — 3D one-shot at a world position. Tension: 3D one-shot at a world position (attenuates with distance).

MATCHESSolution

Use Scene.Trace with the fluent builder pattern. Outcome: // Simple ray from A to B var tr = Scene.Trace.Ray(from, to).Run();.

MATCHESSolution

foreach over GameObject.Components fails. Tension: ComponentList has no GetEnumerator. Outcome: foreach (var c in gameObject.Components.GetAll()) { }.

MATCHESSolution

Use Component.Task (TaskSource) for all async work inside components — inside components. Tension: it auto-cancels when the component is destroyed.

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

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

Use ClutterComponent for GPU-instanced environmental detail scattering: — From code — invalidate tiles when terrain changes:. Outcome: Regenerate all clutter.

MATCHESSolution

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

MATCHESSolution

Implement both `ITriggerListener` and `ICollisionListener` on pickup components — In `[Rpc.Broadcast]` sound effects. Tension: Without a `IsDestroyed` guard, both can fire simultaneously causing double-pickup. Outcome: set `snd.SpacialBlend = 0` when `player.IsLocalPlayer` for 2D sound, leave default (3D) for others.

MATCHESSolution

For soundscape zones use SoundscapeTrigger component. — soundscape zones.

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

Implement `Component.ICollisionListener` on projectiles — Projectile.cs and TimedExplosive.cs. Tension: host only. Outcome: Trigger explosion via `[Rpc.Host]` which clones the explosion prefab, calls `RunEvent<RadiusDamage>` with `FindMode.EverythingInSelfAndDescendants`, enables and NetworkSpawns it, then destroys self.

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 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 separates PlayerData (persistent) from Player (character) using a dedicated Component. — Facepunch Sandbox. Tension: PlayerData (persistent) from Player (character).

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

Record original scene objects on startup — CleanupSystem Component. Tension: Efficient batch destruction.

[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