While it is understandable that avel and horz came from Duke3D,
having both q16horiz and q16horz in the updated SW_PACKET struct
can be confusing, and the alternative notation is more consistent
with the original struct field names of angvel and aimvel, as well
as the differing uses of the name angvel still present in player.cpp.

test for PF_MOUSE_AIMING_ON only if PEDANTIC_MODE == FALSE

one of the players toggled mouse aiming in the middle
of a game, and it worked even worse in Master/Slave mode.
Additionally, tying input to frame rate made the problem disappear.

player is dead, and also disable horizontal aiming while on a ladder.

Mitchell Richters authored Apr 11, 2020 and NY00123 committed Apr 12, 2020

as one more step before tying input to frame rate.

will be filled by faketimerhandler with the current player's
most recent camq16ang and camq16horiz values, respectively.

for them to modify the player's camq16ang/camq16horiz field
instead of q16ang/q16horiz. Additionally, pass to them the
change in angle/horiz via a parameter, as an alternative
to direct access to the corresponding player input field.

Add the camq16ang and camq16horiz fields to the player struct.
With the exception of DoPlayerTurn and DoPlayerHorizon, whenever
code in player.cpp updates player's q16ang/q16horiz, also write
the updated values to camq16ang/camq16horiz. These variables'
preceding values are never used in these functions.

a bit later.

Note that this includes non-portable unaligned accesses, but this
already applies to surrounding code. Just add comments for now.

This uses the newly introduced PEDANTIC_MODE macro.

with q16 angle. This uses the new NORM_Q16ANGLE macro.

an amend to a change from "SW: Make all the changes compile with GCC.":
Pass q16-formatted angles to drawroomstotile.

Additionally update the commented out implementation of drawroomstotile

to q16 angle and horiz. The original SW_PACKET structure,
named OLD_SW_PACKET here, is used while accessing demo files.