Cosa è cambiato in EDuke32, build per build

This appeared to fix a long-standing issue, where a relatively high ping between two players (say, about 750ms) could start increasing over time due to accumulated messages not being sent sufficiently fast.

This also permanently enables weapon auto-switching for PedanticMode. The idea here is that outside of pedantic mode, within multiplayer games, a new bit or more of the inspected player's Flags2 field will be set for the weapon. Afterwards, only for player no. myconnectindex, the function getinput will set loc->bits as if a matching key was pressed for selecting the weapon. loc->bits should be properly synced. Note that each player's structure, including Flags2, is reset within InitNewGame, but not from InitLevel as far as I may tell.

Segue

6e6b82d — Use a tspr->clipdist bit to specify legacy voxels instead of tspr->cstat 48 (Build 10380)

Adds a failsafe for when multiple SE12, SE3 or SE4 are in a single sector by only accounting for the first one (Lowest sprite #ID) This prevents the lighting preview from causing permanent shade changes to a map as it can only store the original map state for one SE sprite per sector.

EVENT_OPERATEACTIVATORS is run against each STAT_ACTIVATOR with a matching lotag when a typical Duke3D button/touchplate is triggered. Current sprite will be stored in THISACTOR and setting RETURN -1 will skip the normal processing of any remaining activator logic. This does not work with Masterswitches as they use a completely different logic instead.

Risolve

terminx/eduke32#323