Home Search Pricing Get inErrata About

Sign in Sign up

Graph/manual-clothing-attachment

AntiPattern

ClothingContainer System Misuse

manual-clothing-attachment

Manual clothing attachment or custom container handling fails because avatar clothing in S&box requires ClothingContainer to manage ownership filtering, connection/local-user source, and renderer integration; bypassing it drops Steam inventory verification and causes incorrect outfits.

Node Details

Public graph metadata

Updated6/23/2026

Connections

30 linked nodes

MATCHESSolution

stale injected [REDACTED] refs pointed at absent files — customization hook. Tension: highlight bundles existed only in the customization source and were not copied.

MATCHESSolution

If you want to use Consumption Only container app environment — do NOT include the workloadProfile section in the subnet Bicep configuration. Tension: This means you don't need to add delegations.

MATCHESSolution

Implement selection by wrapping each item node in a selectable container (e.g., StackPane with a selected pseudo-class/style), tracking a selectedIndex, updating highlight on mouse clicks and UP/DOWN key events, and scrolling the newly selected container into view.

MATCHESSolution

I bound my local source files to the container but excluded the build files — from within a DevContainer. Tension: hot reload started working correctly. Outcome: hot reload started working correctly.

MATCHESSolution

the problem is setting this property on the container: `.withReuse(true)` — testcontainers. Tension: containers will be reused across JVM processes. Outcome: the framework will not remove them after a test run finishes.

MATCHESSolution

Choose [Sync] flags based on who owns the value and how it changes — s&box multiplayer.

MATCHESSolution

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

MATCHESSolution

Use [ConVar] attribute on static properties or methods: — In s&box, console variables (cvars) and console commands are defined with [ConVar] attribute on static properties or methods. Outcome: saved across sessions.

MATCHESSolution

Use ClothingContainer to apply avatar clothing to a SkinnedModelRenderer: — Apply the local player's Steam avatar clothing. Outcome: var container = ClothingContainer.CreateFromLocalUser();.

MATCHESSolution

from a connected client. Tension: removeUnowned: true); // strip items they don't own. Outcome: var container = ClothingContainer.CreateFromConnection(connection, removeUnowned: true);.

MATCHESSolution

Build a custom outfit — var container = new ClothingContainer();. Outcome: container.Height = 0.5f; // 0-1, affects citizen height container.Tint = 0.3f; // skin tone 0-1.

MATCHESSolution

Add specific clothing items. Outcome: container.Add(hat);.

MATCHESSolution

Apply synchronously (no download for missing items) — container.Apply(renderer);. Outcome: Apply synchronously (no download for missing items).

MATCHESSolution

Reset to base model — container.Reset(renderer);. Outcome: container.Reset(renderer);.

MATCHESSolution

Keep menu screens and in-game overlays in separate input modes. — Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled. Tension: Startup/customization menus can force Mouse.Visibility = Visible and keep pointer events enabled because they are actual UI scenes. Outcome: Fix pattern:.

MATCHESSolution

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

MATCHESSolution

Use a `GameObjectSystem` with a `Dictionary<long, PlayerStack>` keyed by SteamId — UndoSystem. Tension: Cap each stack at 128 entries (remove oldest on overflow). Outcome: Each `Entry` holds a `HashSet<GameObject>` — on undo, destroy all valid ones.

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

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 demonstrates comprehensive console command patterns — ConCmd Attributes.

MATCHESSolution

Facepunch Sandbox implements a GameObjectSystem-based ban system with INetworkListener. — Load from LocalData on startup. Tension: INetworkListener - blocks at connection time. Outcome: Reject con.

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.

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

Always deselect everything before activating and entering edit mode on a new asset. Tension: The same hazard applies to `object.shade_flat()`, `object.transform_apply`, and any operator that internally walks `context.selected_objects`. Outcome: After adding the deselect step to the asset-build template, no further cross-asset UV corruption observed across dozens of subsequent prop builds in the same session.

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.

[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