[DispenserGUM]

I was gathering some info on servers that have 33-34 max players.
Top of the list was SourceOP.

So I typed: connect 67.228.59.146:27015;wait 200;status;wait 100;disconnect

I was promptly disconnected with this message
Disconnect: Cannot run commands before entering game.

What sort of exploit is this trying to prevent?

This is purely out of curiosity.

[Hell-met]

a server-crashing command, what else?

derp

[DispenserGUM]

a server-crashing command, what else?

derp

Didn't know there was such thing. Surprising not more servers have this protection.

Oh, maybe a sourceop specific command, okay.

[Hell-met]

you can effectively run commands during the "Loading" time before you actually joined the server

[DispenserGUM]

you can effectively run commands during the "Loading" time before you actually joined the server

\

I know, but I dont see how that would allow crashing a server only between the time your connecting, and the time you receive the server CVARs

But okay that still answers my original question.

Thanks!

[Drunken F00l]

There are commands that expect the person running them to have a player entity. When you are loading, the player entity comes up null and these commands crash the server.

Also if you use the "say" command while loading, it will appear as if the message came from "Console" (the server console). So kicking players running commands while loading is also to prevent that.

Also, any server showing 34 max players is lieing as the maximum supported by the game DLLs is 33.

[glouch]

yeah that happens sometimes when I type something and hit enter just as the map changes.

[Drunken F00l]

Ya, and I was thinking of relaxing it during map changes because of that.

[DispenserGUM]

There are commands that expect the person running them to have a player entity. When you are loading, the player entity comes up null and these commands crash the server.

Also if you use the "say" command while loading, it will appear as if the message came from "Console" (the server console). So kicking players running commands while loading is also to prevent that.

Okay, thanks.

Also, any server showing 34 max players is lieing as the maximum supported by the game DLLs is 33.

I was just trying to see what would be reported in the console at connection, and when using the "status" command. I was working on the tool used to gather information for Fireflash's server blacklists.

[Snarf]

Ya, and I was thinking of relaxing it during map changes because of that.

that would be nice ive gotten booted for it many many times.