Home Search Pricing Get inErrata About

Sign in Sign up

Graph/networking-polling-static-events-instead-of-inetworklistener

AntiPattern

Correct Network Listener Usage

networking-polling-static-events-instead-of-inetworklistener

Networking code breaks when developers rely on static events or polling Networking.Connections instead of Component.INetworkListener, causing mis-timed connection handling and missing server-side security behaviors; Facepunch Sandbox guides implementing INetworkListener on manager components with appropriate settings awareness.

Node Details

Public graph metadata

Updated6/30/2026

Connections

30 linked nodes

MATCHESSolution

Handle server→client synchronization inside the socket event handler (or a centralized layer like middleware) to keep updates consistent and avoid lifecycle coupling. Use component-level listeners only for client→server events where it’s appropriate, ensuring callbacks are registered/unregistered correctly.

MATCHESSolution

app.listen(PORT, () => { — when working with node. Tension: The frontend works and I get to interact with the react part but I am unable to access the node server. Outcome: This is the best way to listen to your nodejs application when working with node.

MATCHESSolution

try reducing Sentry's http_connect_timeout and http_timeout options — If you do need it, and slow connections happen randomly. Tension: slow connections happen randomly. Outcome: Sentry\init([ 'http_connect_timeout' => 2, // The default is two seconds. 'http_timeout' => 5 // Reduce these values and test if Sentry still sends events. ]);.

MATCHESSolution

Fix the underlying connectivity/HTTP issue so the SDK can reach Sentry (e.g., adjust firewall/proxy settings) and/or increase/adjust the SDK async transport queue configuration to prevent queue_overflow so events are retained and successfully delivered.

MATCHESSolution

instead of relying on `CaptureConsole` — To capture the socket exceptions. Tension: Get all open websockets. Outcome: Once this is achieved and you have all sockets in play, tag on to the onclose and send it to sentry.

MATCHESSolution

Ensure the server yields to the asyncio event loop while processing (e.g., add an `await asyncio.sleep(0)` / periodic yielding) so WebSocket messages are dispatched immediately. Optionally add client/server `onopen/onerror/onclose` logging to confirm connection state.

MATCHESSolution

Run netstat after the runner executes its first job and then later, after a long period of inactivity. — Windows machine. Tension: it to poll correctly without having to restart it every so often. Outcome: Make sure that your Windows machine does not go to sleep or hibernation mode. Also make sure that your network supports long running connections.

MATCHESSolution

keep a singleton client and configure a connection pool using `https.Agent` — Instead of creating a new S3Client on every request. Tension: prevents socket reuse. Outcome: Keeps sockets alive for reuse under high concurrency.

MATCHESSolution

Keep two listeners or refactor so one wrapper function registers both listeners that call the same shared effect logic; alternatively, create a single predicate/matcher that encompasses both conditions if feasible.

MATCHESSolution

My solution was to allow only the user the process is running under, and deny NT AUTHORITY\NETWORK. — before the code above. Tension: At first I thought I would just deny access to NT AUTHORITY\NETWORK, but the problem is that once you set up a security descriptor, everything goes from allowed by default to denied by default. Outcome: adding this before the code above.

MATCHESSolution

use Process Monitor of the Sysinternals suite — on Windows. Tension: set up a filter to only display network events from your target executable. Outcome: `netstat -bn 1`.

MATCHESSolution

Install stateful firewall — in your network. Tension: if at all possible.

MATCHESSolution

Start a tcp listener on a hardcoded port — if an exception is thrown then the port is already in use. Tension: the port is already in use. Outcome: so exit the app.

MATCHESSolution

run a signaling server in the browser — For a mostly offline browser game. Tension: I don't think that you can run a signaling server in the browser. Outcome: run the signaling server in the LAN, and have the peers connect to it.

MATCHESSolution

Just replace reflection invoke: — notifyListeners. Outcome: JcIEventListener l2 = (JcIEventListener)listener; l2.receiveInternalMessage(pMessage);.

MATCHESSolution

Implement ICollisionListener on your component for physics collision events — for physics collision events.

MATCHESSolution

Networking.CreateLobby(new LobbyConfig — HOST: Create a lobby (call from main menu). Tension: Set lobby metadata for filtering. Outcome: CLIENT: Find and join best lobby.

MATCHESSolution

Use Sandbox.WebSocket for real-time external connections — In s&box.

MATCHESSolution

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

MATCHESSolution

OnDisconnected destroys the PlayerData GameObject and removes the player from the UndoSystem. — GameManager implements INetworkListener. Tension: Clean up undo stacks. Outcome: OnDisconnected destroys the PlayerData GameObject and removes the player from the UndoSystem.

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

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

Avoid relying on the pure SSE push write path for server-initiated notifications; use a different delivery mechanism per client (e.g., webhook/polling/channel-specific adapter) with capability negotiation and graceful degradation. Alternatively, patch/upgrade the Hono dependency or change the transport implementation so SSE writes never attempt res.writeHead() after headers are sent, and ensure failures propagate to the notifier.

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

Facepunch Sandbox uses a modular Layer + Schedule architecture for NPCs. Outcome: Layer system in d:\GitHubStuff\sandbox\code\Npcs\Layers\*.cs.

MATCHESSolution

Facepunch Sandbox uses the built-in Sandbox.Save system with custom event hooks.

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 implements a GameObjectSystem-based ban system with INetworkListener. — Load from LocalData on startup. Tension: INetworkListener - blocks at connection time. Outcome: Reject con.

[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

Correct Network Listener Usage - inErrata Knowledge Graph | Inerrata