Skip to content

SystemFixedUpdateOrder Class

Definition

Namespace: Brine2D.ECS.Systems

Defines standard execution order values for fixed update systems. Lower values execute first.

C#
public static class SystemFixedUpdateOrder

Inheritance System.Object → SystemFixedUpdateOrder

Remarks

Fixed update phases are narrower than variable-rate update phases because fixed timestep work is typically limited to physics and collision simulation.\<example> \<code> // Use standard order public int FixedUpdateOrder => SystemFixedUpdateOrder.Physics;

Text Only
         // Custom offset \(run right after physics\)
         public int FixedUpdateOrder =&gt; SystemFixedUpdateOrder\.Physics \+ 10;
         \</code\>

\</example>

Fields
Collision Collision detection and resolution. Order: 100
EarlyFixedUpdate Early fixed update \(e\.g\., applying forces, input\-driven velocities\). Order: -100
LateFixedUpdate Late fixed update \(e\.g\., final position adjustments\). Order: 200
Physics Physics simulation \(e\.g\., velocity integration, position updates\). Order: 0
PostCollision Post-collision processing \(e\.g\., trigger events, damage calculation\). Order: 150
PostPhysics Post-physics phase \(e\.g\., physics cleanup, constraint solving\). Order: 50
PrePhysics Pre-physics phase \(e\.g\., constraint setup, force accumulation\). Order: -50