Zandronum 1.0-alpha-120729-1356

[Torr Samaho]

Zandronum 1.0-alpha-120729-1356

The most notable change in this build is the player limit which has been raised to 64. So far this only received little testing, so it would be great if somebody organizes a huge playing session with at least 33 players :). Another addition in this build is the new ACS command ConsolePlayerNumber which should come in handy in CLIENTSIDE scripts.

Here is the full list of changes since the last official Zandronum beta build, i.e. 120715-1139:

Code: Select all

changeset:   3457:f126a804e7c7
user:        Torr Samaho
Changed: PlayerIsSpectator returns 1 if the player is a true spectator and 2 if the player is a dead spectator.

changeset:   3458:6f58c1540732
user:        Torr Samaho
Converted the ACS function GetTeamScore to be compatible with ZDaemon's version of this function.

changeset:   3459:65a948ecfc9a
user:        Torr Samaho
Raised the maximum number of players from 32 to 64. sv_maxclients and sv_maxplayers still default to 32 to stay compatible with existing mods.

changeset:   3460:fc168d3d94ec
user:        Torr Samaho
Added new ACS command ConsolePlayerNumber that returns the number of the local player. Returns -1 if called on the server.

changeset:   3461:8d2c6e95243d
user:        Torr Samaho
Added the possibility to leave the join queue with the spectate command.

changeset:   3462:1ace407f015c
user:        Torr Samaho
replaced a bunch of images in wadsrc by their corresponding versions from GZDoom revision 323 (making zandronum.pk3 slightly smaller and reducing the differences of Zandronum to its GZDoom base)

changeset:   3463:11362e3ff11f
user:        CrimsonDusk
Fixed: Missiles would not be deleted properly if they hit the sky or a horizon line.

changeset:   3464:c7886d40c1fc
user:        Torr Samaho
out of sequence fix backport from ZDoom revision 3620:
- Use SetOrigin() instead of P_TryMove to set the dropped item's position in AActor::DropInventory(). Also removed dropdist, since it wasn't used.

changeset:   3465:dad97f8a8ebc
user:        Torr Samaho
removed some useless code that has been hiding at least since 97c2

changeset:   3466:11f9f880a4bd
user:        Torr Samaho
Fixed: If gl_lightmode was 2 in the config file when starting the game, gl_lightmode was automatically changed to 3.

changeset:   3467:f35f5ac7c02b
tag:         tip
user:        Torr Samaho
Fixed the white space differences of decaldef.txt to its GZDoom revision 323 counterpart.

Windows
Linux x86
Linux x86_64
Mac OS X

[Disguise]

Nice! Increased player limit! Excellent work as usual!

[Ænima]

FUCK. Now I have to go back and edit the array size of all my variables to [63] instead of [31].

:P

[katZune]

:D! fuck yeah 0/, have no words

[Watermelon]

I'll try to set up 33+ players

[Queen Chrysalis]

Yo Watermelon make a post ahead of time i'm planning on attending.

[ZzZombo]

I'm now very glad I never assumed 32 players limit and always use MAXPLAYERS constant definition in ACS. Hehe. Nice work.

[Blade]

Mother of god! Somebody should set up a regular server with no huge downloads, and we could schedule a game! It will be epic.

[Ijon Tichy]

FUCK. Now I have to go back and edit the array size of all my variables to [63] instead of [31].

:P

what happens when you have player 63 (the 64th)? weird shit, that's what

also you'd do well to "#define PLAYERMAX 64" and use that in defining arrays

[Blzut3]

also you'd do well to "#define PLAYERMAX 64" and use that in defining arrays

I would use a max of 255 (or maybe even 256) and future proof the code a little. :p

[Ijon Tichy]

yeah i use 256 myself

[ZzZombo]

And all loops will have to iterate over all invalid clients? No, thanks

[Blzut3]

The problem is what exactly? The amount of CPU time wasted and additional memory usage (768 bytes) is negligible. It not like you have to worry about bandwidth utilization either since ACS calculations aren't synchronized.

[mistamontiel]

Hang on. Now a 64 player deathmatch is possible..?

Sooo many freaking slots dude.. I thought only Battlefield 1942 (debut from 2002) ever since, whole PC series was king of 64 player mayhem, like trademarked that damn number

[Ænima]

FUCK. Now I have to go back and edit the array size of all my variables to [63] instead of [31].

:P

what happens when you have player 63 (the 64th)? weird shit, that's what

I thought when defining the size of arrays, you use the maximum index number (which would be 63, right?). Or just the literal SIZE of the array in integers, starting at 1?

Shit's confusing, bro.

[Qent]

Use the actual size of the array, starting at 1. You mean you've been using off-by-one arrays... forever?! D:

[Ænima]

Pfft. As if 32 people have ever been in a SST server at one time.

[Torvald]

All out war, Who dun it, Friday night fragfest, Ghouls vs humans. Etc, there's been many times where it's maxed out :D ( got at least 20 pics of gvh alone hitting 32/32 on separate days). The great thing about this is that will spare Server clusters from having to open up two servers to compensate for max client connection.

[Llewellyn]

All out war, Who dun it, Friday night fragfest, Ghouls vs humans. Etc, there's been many times where it's maxed out :D ( got at least 20 pics of gvh alone hitting 32/32 on separate days). The great thing about this is that will spare Server clusters from having to open up two servers to compensate for max client connection.

Yo he said SST not ST. (Assuming you're replying to the post above you.)

[mistamontiel]

lol, Who dun it ? All out war ? GVH ? All too complex + dull, pffft, Who dun it, just moving the whole time, nothing else to do. Never seen em full, almost full, but not quite

FNFragfest definitely can use twice the slots. Damn spectating whores, er, well I don't know the limits maybe they had to not so sure. Just so many

Deathmatch.. CTF.. Invasion.. rules