Unable to join team mid-round

[Phaze]

Hi there.

Firstly I’d just like to thank you guys for the amazing work done from GG 4 to 5.1. There really has been a substantial amount of effort put in, and it is definitely showing
I have a small issue though with 5.1 that I am unable to figure out.

I'm running GG 5.1 rev 440.
I have turbo deathmatch enabled on my server, with the respawn delay set to 0.1. In GG 5 anyone who joined into the game mid round would simply choose a team spawn and start playing. Now I find that with 5.1, players are unable to join mid way through a round and sit as spectators until the round has ended and restarts (that is if they are lucky enough for an entire team to be eliminated at once!).

I have taken a look through all changes made to gg_deathmatch.py and the only clue I can find is that it has something to do with a change made in r435
* Fixed joinclass being stopped at times

Either this, something totally not related, or I’m missing a simple configuration parameter somewhere
I have made sure that my gg_deathmatch.py file contains all latest fixes specifically from r435 and r441.

Any help on this issue would be greatly appreciated and will stop my colleagues from throwing fits of anger when they can't join a game!
Thanks!

[satoon101]

I'm running GG 5.1 rev 440.

I have made sure that my gg_deathmatch.py file contains all latest fixes specifically from r435 and r441.

First you say you are running 440, then say you have the fixes from 435 to 441. This post outlines an issue (with gg_deathmatch which disrupted respawning) that was not fixed until 441, so make sure you are running the latest.

Satoon

[Phaze]

Hi satoon.

Thanks for the reply. What i meant was that i installed rev 440 and fixed deathmatch.py with the latest fixes.

My problem is not with spawning during normal deathmatch game play...when the player can actually join the round:
If we are say +- 5 minutes into a round, and a new player wants to join, as soon as they select the team to join, they remain in spectator mode until the round is re-started.

I'll install the full rev 444 tomorrow and give it a spin, perhaps there's something I did miss.mmm..
Anyway, thanks for the assistance, i'll let you know if 444 has sorted out my issue.

[satoon101]

Yeah, I realized after I posted, that that probably wouldn't fix your overall issue. Do you get any errors? Posting them would be beneficial to us helping you.

Satoon

[Phaze]

Nope, no error messages (both in the GunGame log directory and the cstrike logs).

I'll dig around tomorrow and see if anything catches my eye when this happens.

[Warren]

Can you fill out an issue report?

[Warren]

Actually, try r448 first. If it is fixed, let us know. Otherwise, please fill out an issue report.

[Phaze]

Right, will test it this eve and let you know.

[Phaze]

Unfortunately we had only six players today, and by the time they all joined, the round's had restarted a number of times so its difficult to tell if the fix was a success or not -= at least no one complained! =-
Being friday tomorrow there usually is a bigger turnout of players so I'll join in a round late to see if the prob has been resolved.

[Warren]

Alright, let us know.

By the way, I assumed you had gg_dm_respawn_delay 0 set when asking you to try the latest revision. If this is not the case, then the latest revision wouldn't address this issue.

[Phaze]

Hi Warren,

My respawn delay was set to 0.1, i think its now currently sitting on 0.5.
I ran a few tests on Friday (sorry for the late response been really busy around here) and it appears to work perfectly now.
If the prob comes up again I'll fill out an issue report.

Thanks for the assistance