Cosa è cambiato in EDuke32, build per build

There are unfortunate duplications of the shared string, but such occurrences don't seem to be that common so far.

Trailing '\n' characters have been removed again.

These are done using TerminateWithMsg, except for a few instances in which the strings were meant to be printed without formatting, where TerminateWithSimpleMsg is used instead. Trailing '\n' characters have been removed from input strings. For code previously using printf and not wm_msgbox or loguru, this should resolve instances in which the program would abort without relevant logs, at least under specific platforms. Note that printf had its usage under DOS.

TerminateWithMsg is going to be used instead of separate sets of calls to TerminateGame, printf/wm_msgbox and exit. It'll use wm_msgbox, not printf (originally used under DOS), and also go through LOG_F. This is an inline function definition using a variadic template, allowing the use of LOG_F and also matching loguru::log. TerminateWithSimpleMsg is a wrapper that allows printing a string without formatting.

The addition of the "bob_z" field to the PREDICT struct might be unnecessary, technically speaking, but it probably won't hurt to ensure values are synced.

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.

Allows adjustable Y-offset for in-game quotes from CON. Input expects higher precision coordinates similar to rotatesprite16.

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

Segue

4f58b06 — engine: fix RELEASE=0 build with GCC 14.x (Build 10600)