[AtomicStryker]

My argument stands.

[noodleboy347]

Originally Posted by AtomicStryker My argument stands.

Did you ignore what retsam said? You shouldn't code to support listen servers.

[Monkeys]

A lot of the functions simply don't support the 0 client index.
Nothing we can do about it. All we can do is prevent the plugin from crashing if a 0 client occurs. We can't tell the function to "DO IT ANYWAY". They're lazy like that.

[p3tsin]

Originally Posted by Monkeys A lot of the functions simply don't support the 0 client index. Nothing we can do about it. All we can do is prevent the plugin from crashing if a 0 client occurs. We can't tell the function to "DO IT ANYWAY". They're lazy like that.

0 isn't a client index, it means the command originated from server console (like with dedicated servers). The host usually has a client index of 1. Though I've ran into having a higher client index when bots were configured to join before human players, but can't reproduce it since the OB update. Maybe it was fixed.

Just throwing this out there: would it be completely disastrous if SourceMod changed all "client 0" indexes internally to the host index if the server was a listen one?

[Monkeys]

Originally Posted by p3tsin 0 isn't a client index, it means the command originated from server console (like with dedicated servers). The host usually has a client index of 1. Though I've ran into having a higher client index when bots were configured to join before human players, but can't reproduce it since the OB update. Maybe it was fixed. Just throwing this out there: would it be completely disastrous if SourceMod changed all "client 0" indexes internally to the host index if the server was a listen one?

I know it's not a client index, but the functions treat whatever we give as if it's a client index. Even if we give 'em 0.

I'm sure the devs have a reason for not doing it. Be it safety, be it anything, nothing much we can do.

[AtomicStryker]

Originally Posted by noodleboy347 Did you ignore what retsam said? You shouldn't code to support listen servers.

Originally Posted by myself Because if you don't, people will keep reporting "bugs" related to 0 client errors.

[dirka_dirka]

you code it to tell the player "client 0 is bad, quit using listen servers and download srcds."

[mi123645]

AtomicStryker is right. It's not like listenservers rape your dog and maul your cat, just have the plugin ignore client 0.

0 isn't a client index, it means the command originated from server console (like with dedicated servers). The host usually has a client index of 1. Though I've ran into having a higher client index when bots were configured to join before human players, but can't reproduce it since the OB update. Maybe it was fixed. Just throwing this out there: would it be completely disastrous if SourceMod changed all "client 0" indexes internally to the host index if the server was a listen one?

Sounds like a good idea.

[retsam]

Well, I dont run listen servers, but I always thought the host was client "0" on listens, if its not, then its a moot point.. The point was, if you run a type of server where client 0 is actually in game, you will have serious problems with most plugins. Client 0 should always be filtered.

[FaTony]

No, on listen server host has client index of 1 but his console has index of 0.