• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

L4D - "Server is full"

Is there any way to stop it from coming up with this message, sometimes i like to quickmatch and this happens a lot. If its full why cant it just continue searching for one that isnt full, i dont need to know every time a server its tried to join is full... Any console commands or something to alleviate this?
 
Originally posted by: nakedfrog
Maybe it didn't appear full initially, but the slot was taken by the time you connected? I don't know.

Yes, thats generally what it is, however its stil a retarded problem that has been there since day one that shouldn't be there. When you choose the option to have the program send you into any available game that is open but gives you this "error", if that happens it should just start the process over again instead of stopping and giving you that error.
 
Originally posted by: bunnyfubbles
Originally posted by: nakedfrog
Maybe it didn't appear full initially, but the slot was taken by the time you connected? I don't know.

Yes, thats generally what it is, however its stil a retarded problem that has been there since day one that shouldn't be there. When you choose the option to have the program send you into any available game that is open but gives you this "error", if that happens it should just start the process over again instead of stopping and giving you that error.

Ya, that is pretty stupid. Sounds like a pretty simple piece of code to implement too. I sometimes get the "full" message 5 times in a row.
 
"Match Making

Fixed a mismatch between lobbies and servers that will remove the "Server is full" errors when quickmatching"

Aha! Maybe someone from valve is reading this forum, that fix was released today. Awesome 🙂
 
Back
Top