A common challenge in multiplayer games involves managing network data for numerous active projectiles. When projectiles are configured with physics body components and move through the environment, their Transform data is often synchronized every snapshot by default. This behavior is expected in server-authoritative setups where Transform changes occur each tick. However, when a large number of projectiles are simultaneously 'in the air', the constant transmission of their changing positions can overwhelm network bandwidth. This leads to the server occasionally skipping data for some projectiles, causing them to appear laggy or unsynchronized on client machines. Increasing the network importance of projectiles may resolve their lag but can subsequently cause other entities to suffer from similar synchronization issues. Since many projectiles do not change direction, scale, or speed after their initial launch, it is desirable for the server to only communicate their initial spawn state and subsequent destruction. Clients should be able to accurately extrapolate the projectile's movement based on this initial data. Simply reducing the snapshot frequency for projectiles is not a viable solution, as this also delays the reporting of their initial spawn, negatively impacting user experience.