Cosa è cambiato in EDuke32, build per build

Can be changed with the cvar cl_keybindorder. Settings the value to 0 restores the original classic keybind order, 1 uses the modern ordering. Either mode is overridden by custom keybind orders.

List the gamefunc names (or corresponding indices) separated by whitespace. This will define the order of gamefuncs on the keyboard configuration menu. Any omitted gamefuncs will not be listed in the menu. Usage: ``` keyconfig { gamefunc_Move_Forward gamefunc_Move_Backward gamefunc_Strafe_Left gamefunc_Strafe_Right ... } ```

Within EVENT_GETBONUSTILE, you can now set ud.return[0] to ud.return[4] to change each frame of the bonus screen animation separately.

The RETURN value will be set to the current base bonusscreen tile, and changing it will change the tiles displayed in the bonusscreen.

This fixes a bug in World Tour where trying to switch to the flamethrower while the current weapon is the freezer, and you have flamethrower ammo but not the actual weapon itself, then this instead locks the weapon key, preventing you from switching back to the freezer from other weapons. This bug also affected the Shrinker, but only if CON code changes the 'gotweapon 11' value to 0 after the player obtains the weapon.

This was a bandaid that prevented repeatedly loading the same mapart when loading savegames. This meant having to constantly update the buffer whenever clearing mapart, which is undesirable. Fixes mapart not reloading after quitting to title, or ending an episode and then loading a savegame.

Previously, only sprites with statnum 0 would have their per-actor variables reset to the default on map load. This meant that sprites with statnums that were pre-defined in the map would inherit the actor var values of the sprites with corresponding spriteNums from the previous map. Additionally, the per-actor var reset is now performed before EVENT_PRELEVEL, meaning that any changes to actorvar that occur in this event will now persist. Previously, altering actor vars for sprites with statnum 0 in this event would not have any effect, as they would be reset to their defaults afterwards.

* Scripts no longer compile if a hex constant is malformed (e.g. 0x, 0xz) * Compiler will now warn if a decimal or hex constant isn't terminated in a sane manner. (example: digit is followed by letters: "100ab") * Compiler will now warn if a label starts with digits. This is done to prevent ambiguity between integer constants and actual labels.

`userdef[].folsvel` represents the strafe velocity.

Values range from -128 to 127. The former defines the distance of the actor from all floors, the latter applies additively to the hardcoded offset applied when on lotag 1 sectors. Positive values lift the actor off the ground, negative values move the actor into the floor. The default values for both struct members is 0. To achieve a net zero displacement, htfloorzoffset needs to be set to -1, and htwaterzoffset must be set to 24. Also note that internally, the offset is multiplied by 256 to receive the actual z coordinates (like `iffloordistl`).

This prevents accidentally overwriting the wrong map slot.

Usage: ``` getngcflags <var> <idx1> [<idx2>...] setngcflags <const/var> <idx1> [<idx2>...] ``` Gets/sets the flags for the newgamechoices entries at the specified indices. The index list is variable-sized, up to a maximum of 3. This can be used to enable/disable the MEF_Hidden and MEF_Locked state. Supersedes the userdef struct members: `m_newgamecustomopen` and `m_newgamecustomsubopen`.

Also permit usercontent flag on subentries.

These events trigger once every frame and provide access to the input struct value updates of each frame. This makes it possible to alter input.q16avel and input.q16horz again, even with smooth mouse aiming. Addresses terminx/eduke32#132

Allows FURY compiled mapster32 to launch fury.exe

Changes: - Passing struct members and player vars as argument now works. - If struct members are accessed without specifying the index, the command will display which index was used by the CON VM. - Enable use of constant values for array indexing in addlogvar - Enable logging of integer constants with addlogvar - General refactoring and code improvement.

These variables include: * `tempxpanning` * `tempypanning` * `tempxvel` * `tempyvel` * `tempzvel` * `tempstatnum` * `tempblend` * `tempsectnum`

This fixes a bug where stale blend values could be transferred over from a previously loaded map.