Client connecting during intermission

[Cobalt]

as stated in the QC comments - "can cause problems".

I have experimented with this and it seems for some reason the client is being set to .team = 1 ? Not sure if thats something happening in my specific QC, but I am looking for that in ClientConnect () then passing him directly to PlayerPrethink () where it will see the intermission running and do the Intermissionthink, but instead blacken the screen and do a

WriteByte (MSG_ONE, SVC_FINALE);

Plus

WriteString(MSG_ONE, "Some cute text - blah");
...and some cute CD music.


So this works fine only when the next leve l loads, the (4) Runes that spawn at framecount 140, dont have models and their special precache sounds dont play. Is this something to do with the sign on packet?

[Spike]

the problems the qc comment aludes to are:
1) svc_intermission won't be shown for late joiners (qc would need to send it).
2) a delayed svc_intermission will show the wrong end time (there's no sane way for qc to work around this, although I suspect generating a manual svc_time would do it, but would probably break things at the same time).
3) qc doesn't track which svc_finale message was displayed (again, logically this is the qc's job).
4) oldone.qc/end.bsp sets intermission_exittime to something really high. a new player joining the game is the only way for a dedicated coop server to progress.
5) qc doesn't move the player to an intermission spot when they join mid-intermission

these things could be fixed satisfactorily via qc, but its somewhat rare and much easier to just move to the next map. besides, in deathmatch, moving to the next map helps you wake up when someone new joins.


the server isn't aware of intermission at all, the qc does all intermission-related serving.
the client is aware of intermission, but only cares as far as the hud/scoreboard/finale is concerned.

.team is set according to the player's lower colours, as the server is unaware of intermissions, there is no reason for me to believe that there is anything wrong here. 1 is a valid value if your lower colour is 0 (or white).
the client will send a "color" command just before it sends the "spawn" command, so the .team field is guarenteed to be set correctly before ClientConnect+PutClientInServer are called.

makestatic/staticsound builtins write their data to the MSG_INIT buffer. as a result, clients only see these if they join AFTER the builtin was called. its possible for a server to also send it to current clients, but this can potentially result in duplicates if not handled correctly.

[r00k]

look at the runequake source he handles sending new clients the sv _intermission and origin placement

[Cobalt]

[Spike]

[Cobalt]

Thank Spike. Decided to precache the rune stuff in worldspawn , problem seems to be fixed.

[r00k]

yes, things that are not map entities should be precached in world.qc; ie not in weapons.qc.

i thought this thread was about putting clients into the intermission when they connect after an intermission had started.

[Cobalt]