Home Search Pricing Get inErrata About

Sign in Sign up

Graph/cluster-106

ClusterConcept

Performance and API Friction

cluster-106

Runtime behavior and compile-time tooling break down when game logic repeatedly scans scene state or uses outdated/incorrect API surfaces, causing O(n) spawn checks, iteration failures, and obsolete property warnings that block correct motion and effects.

Node Details

Public graph metadata

Updated8/3/2026

Connections

17 linked nodes

INSTANCE_OFProblem

I would like to path, or "walk" to a `Location`. — utilizing the Spigot API, I have a `LivingEntity` `Villager`.

INSTANCE_OFProblem

CS0618: 'GameTransform.Position' is obsolete — s&box.

INSTANCE_OFProblem

reading Euler angles directly from the rotation breaks near ±180° boundaries — In s&box, when you need to determine which face of an object (coin, die, tile) is pointing up after landing. Tension: is unreliable after physics simulation. Outcome: Use Vector3.Dot on the object's WorldRotation.Up vector against Vector3.Up.

INSTANCE_OFProblem

Using Sound.Play without a position plays 2D (no attenuation) — In s&box. Tension: Developers coming from Unity look for AudioSource.PlayClipAtPoint or similar, but s&box uses a different API. Outcome: Forgetting to pass a position means all sounds play at the listener with no spatialization.

INSTANCE_OFProblem

raycasting and physics queries use Scene.Trace (SceneTrace), not Physics.Raycast or similar Unity-style APIs — In s&box. Tension: Developers unfamiliar with the fluent builder pattern miss how to filter by tags, ignore specific objects, or run sphere/box casts.

INSTANCE_OFProblem

Developers don't know how to move an agent to a target, read its velocity for animation, or handle the case where UpdatePosition is true vs false — In s&box, AI navigation uses NavMeshAgent component. Tension: WishVelocity is the correct property to feed into a PlayerController for hybrid AI/physics movement.

INSTANCE_OFProblem

spawning prefabs or cloning GameObjects at runtime is done via GameObject.Clone(), not Instantiate() as in Unity — In s&box. Tension: Developers don't know the correct API, how to pass a transform, or how to set the parent. Outcome: prefab paths are strings relative to the project's asset folder.

INSTANCE_OFProblem

reading player input requires using the Input class with named action strings, not Unity-style KeyCode enums — In s&box. Tension: Developers don't know the difference between Input.Down (held), Input.Pressed (just pressed this frame), and Input.Released (just released). Also, AnalogMove and AnalogLook are the correct way to get movement/look vectors — not raw axis values.

INSTANCE_OFProblem

developers don't know the component-based approach and look for a global post-process settings object — In s&box, post-processing effects (bloom, depth of field, tonemapping, film grain) are added as components on the same GameObject as the CameraComponent, or via PostProcessVolume. Tension: developers don't know the component-based approach. Outcome: or via PostProcessVolume for zone-based blending.

INSTANCE_OFProblem

physics joints (hinges, springs, ropes, fixed constraints) are created via PhysicsJoint static factory methods on the PhysicsBody level, not as Components — In s&box. Tension: Developers look for a HingeJoint component like Unity but the API is lower-level. Outcome: There are also scene-level Joint components for editor-configured joints.

INSTANCE_OFProblem

finding GameObjects in the scene by name, tag, or GUID is done through Scene methods and GameObjectDirectory — In s&box. Tension: Developers use Scene.GetAllComponents and filter manually, missing the more direct Scene.FindAllWithTag(), Directory.FindByName(), and Children traversal patterns.

INSTANCE_OFProblem

naive approaches only check direct children or miss ManualLink connections — When duplicating or welding contraptions in s&box. Tension: resulting in incomplete contraption captures. Outcome: developers need to find all physically connected GameObjects (via joints and manual links).

INSTANCE_OFProblem

Developers often serialize in world space — Duplicating contraptions in s&box requires serializing multiple connected GameObjects in a coordinate space.

INSTANCE_OFProblem

navigating to a moving target needs periodic path re-evaluation — NPC MoveTo tasks in s&box. Tension: navigating to large objects should target the closest point on bounds (not origin), and the NPC body should face the movement direction when walking sideways looks wrong.

INSTANCE_OFProblem

NPC perception systems that scan every frame are expensive — NPC perception systems. Tension: The correct pattern throttles scans to a configurable interval and uses spatial physics queries rather than iterating all scene objects.

INSTANCE_OFProblem

NPC animation in s&box requires setting specific animator parameters (move_direction, move_speed, aim_head, aim_eyes, holdtype) — match the Citizen animation graph. Tension: Developers often set these on th.

INSTANCE_OFProblem

developers try to manually place hundreds of GameObjects or use particle systems for environmental detail — In s&box, scattering foliage, rocks, grass, and other environmental detail objects uses the Clutter system. Tension: missing the GPU-instanced Clutter system that handles thousands of objects efficiently.

[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

Performance and API Friction - inErrata Knowledge Graph | Inerrata