Zandronum

• Fixed a desync that happened when a player disconnected from the server before clients received a full snapshot of a level. This also caused the "P_PlayerThink: No body for player" warning to start spamming in the console after the level change.
• Added Sean's tweak to the HUD in CTF/Skulltag. The names of carriers are now displayed in their team colour, instead of the colour of the team's item they are holding.

changeset: 12636:28e433ec2ffb
user: Adam Kaminski <kaminskiadam9@gmail.com>
Fixed: players sometimes spawned in the void, or just random spots in the map, when they should've spawned at a random cooperative spot.

changeset: 12642:992907f71812
user: Adam Kaminski <kaminskiadam9@gmail.com>
- Fixed a fatal error when trying to select the farthest deathmatch spot available, and all spots were taken.
- Restored more code from GZDoom 1.8.6 used to spawn a player in deathmatch, albeit commented out because Zandronum doesn't actually use it.

changeset: 12645:1eb062e9ae46
user: Sean Baggaley <sean@csnxs.uk>
The bottom-right HUD in CTF/Skulltag now displays the names of carriers in their team colour, instead of the colour of the flag they are holding (addresses 4428).

changeset: 12646:9d7ec921b8d5
user: Adam Kaminski <kaminskiadam9@gmail.com>
Added a sanity check, when processing a "DisconnectPlayer" server command, to ensure a few things aren't executed if the player being disconnected had no body.

changeset: 12647:0c2b243f9d02
user: Adam Kaminski <kaminskiadam9@gmail.com>
Fixed "P_PlayerThink: No body for player" warnings if a player disconnected from the server before the clients received a full update (fixes another regression caused by c770f5a41612).

RmBeer wrote: ↑

Fri Dec 27, 2024 2:02 am

And the source code what?

Even in hg source code exist only to 3.1, or a "default" branch. How can get a 3.2 alpha like all in doomseeker?

Sean wrote: ↑

Fri Dec 27, 2024 2:04 am

RmBeer wrote: ↑

Fri Dec 27, 2024 2:02 am

And the source code what?

Even in hg source code exist only to 3.1, or a "default" branch. How can get a 3.2 alpha like all in doomseeker?

hg tags aren't created for betas. A list of hg revisions for 3.2 betas is available at https://wiki.zandronum.com/Version_hist ... eta_builds however. For this specific beta, use hg update 0c2b243f9d02

RmBeer wrote: ↑

Fri Dec 27, 2024 2:07 am

You're mix beta with alpha. But thanks, i will try with the hash of checkout for 3.2 alpha.

Sean wrote: ↑

Fri Dec 27, 2024 2:11 am

RmBeer wrote: ↑

Fri Dec 27, 2024 2:07 am

You're mix beta with alpha. But thanks, i will try with the hash of checkout for 3.2 alpha.

"Beta" and "alpha" have ended up being interchangeable in the context of Zandronum builds.

The Linux build guide always shows the latest alpha/beta/whatever hash now; I should probably extend that to the other build guides...

RmBeer wrote: ↑

Fri Dec 27, 2024 5:54 pm

They/you really lost track of everything, and can't create a decent version that works. They/you should be more careful next time about what and how to release version 3.3, because they/you only lose players by this neglect. :/

Ivan wrote: ↑

Mon Feb 24, 2025 12:42 am

I'm not sure what exactly happened with this particular version but whenever my friends try to host Death and Decay and play on it the performance is atrocious, it's extremely choppy and hudmessage related menus run very poorly. The version downloaded is in this link: https://zandronum.com/downloads/testing ... x86_64.zip

We were previously running 3.1 and there were absolutely no such issues. It seems whatever change is made between 3.1 to 3.2, something went horribly wrong and all performance is gone down the drain. I could observe noticable choppiness on the gameplay just running around.

The wads we run are lexicon, dnd, snmp. This wad combo works smoothly in 3.1.