Fix: Object trigger and pathfinder update issues

[seer-by-sentry]

Fixes CLIENT-3YS. The issue was that: Uninitialized PolygonTrigger list accessed during object placement in startNewGame causes access violation in W3DTreeBuffer::unitMoved.

• Prevent pathfinder position updates during game initialization (frame 0) to avoid crashes when W3DTreeBuffer is not yet ready.
• Add null pointer checks for pTrigger in m_triggerInfo to prevent crashes if a PolygonTrigger is deleted while still referenced.
• Skip water area polygon triggers during object entry/exit checks, as they are not intended for script trigger events.

This fix was generated by Seer in Sentry, triggered automatically. 👁️ Run ID: 11441048

Not quite right? Click here to continue debugging with Seer.