…d be removed, and some others seem to have been done incorrectly.

…than that just added more comments so the code can be understood more easily later on,.

…ecks to prevent unnecessarty shifting of clients to reduce load (due to higher trail count).

Now that more trails are stored, it's unnecessary snap and clamp the trail time. the more precision and information we have the better.

Moved check that prevents clients trying to timeshift too far back (> 500ms).
Replaced IS_ACTIVE macro with function.

…ft even if it's surpassed level.time.

level.time is only incremented every 50ms (sv_fps = 20).. so high fps clients can catch up and even surpass before the next 50ms increment can happen.
if there are no clients with a trail <= than this really fast client's serverTime, then it'll just end up using server's current player states for collision detection anyways, so it's a-okay.

…it easier to read/understand (imo).