Fixes for ghost beacons

[Rainyan]

Description

Fix a problem with spectators seeing the spectated ghoster's beacons instantly, instead of after the delay specified by the cvar neo_ghost_delay_secs. For the default case, we can derive the ghost equip time from its m_flNextPrimaryAttack, but for the neo_ctg_ghost_beacons_when_inactive mode I also had to add a new time variable (m_flPickupTime) for tracking when the ghost was initially picked up.

Also fixes an inaccuracy for the ghost beacons maximum visible distance.

Toolchain

• Windows MSVC VS2022

Linked Issues

• fixes Spectators can see ghost markers before the ghost carrier does #1426
• fixes Ghost beacon max distance is incorrect #1441

[Agiel]

Good work!

[Rainyan]

Well, this PR grew a bit larger than I expected. There's now more logic on whether to network enemies to the ghoster based on ghost activation time, distance etc. This is toggleable with a new cvar sv_neo_serverside_beacons (default value 1, i.e. enabled), where turning it off will make the server instantly network enemies instead of waiting for the sv_neo_ghost_delay_secs duration.

Since the ghoster needs to know the distance to nearest enemy for the beacon sound effect's playback interval (it would be a bit unreliable timing-wise to send them from server->client), there's a new m_flNearestEnemyDist networked property on the ghost, so that we can share this with the ghoster without needing to expose all the enemies' locations before they're allowed to know it. In the sv_neo_serverside_beacons 0 mode, the client just calculates it from the networked enemy locations like before, instead of the server, since they have all the info.

Here's an example of the timed beacons networking, tested with r_novis 1; mat_wireframe 2;

beacons.webm