So I notice that players who normally would've gotten cfaile

[Kaysakado]

(title got cut off ffs)
d get restored.

Does this mean that if the server is running a modified version of 2.0 and the client is running unmodified, the client will, instead of being cfailed, be restored, and end up playing the modified version, though it would be laggy due to having to be restored all the time?

 

[Spazzo]

Any sort of trigger for consistency failures now results in the server 'restoring' the client by taking the information about the client from the server and sending it back, restoring consistency. This can be sidabled in the network options, too.

If two people have a wad of the same name and of a different md5sum, they will probably be triggering this "restoration" a lot. You can figure out who exactly is causing this if you do BLAMECFAIL YES in the console (host only).

 

[FuriousFox]

Different MD5 sums shouldn't even be a problem now, since the checking has been turned back on (at least I should HOPE it has been).

 

[Kopper]

Well, c-fail still happens, but it seems only when you join sometimes. And sometimes all the time. (Illegal netvar command color 0 team 0 anyone?) Also, I'd like to give a possible tip for this problem: Host a game of the same type on the same map for about two seconds, then try again. (I didn't think the tip worth it's own topic :/)

 

[Ezer'Arch]

Isn't that because people is using 2 SRB2 versions? (or just one when there are servers with 2.00 and 2.01, I've used both)

I caused some c-fails in some servers: I join and everybody else is kicked out, but player 0 remains.

 

[Spazzo]

Well, c-fail still happens, but it seems only when you join sometimes. And sometimes all the time. (Illegal netvar command color 0 team 0 anyone?) Also, I'd like to give a possible tip for this problem: Host a game of the same type on the same map for about two seconds, then try again. (I didn't think the tip worth it's own topic :/)

These are bugs, and will be fixed for 2.0.2.

 

[DarthJunior]

Isn't that because people is using 2 SRB2 versions? (or just one when there are servers with 2.00 and 2.01, I've used both)

I caused some c-fails in some servers: I join and everybody else is kicked out, but player 0 remains.

I thought player 0 was the host...

And yes I occasionally have that problem. Not too much anymore though.
If you get C-failed once, and you still want to play, I like to just count to 30 before trying again. Hopefully the server would have fixed itself by then.

 

[Ezer'Arch]

I thought player 0 was the host....

It is.

I joined a server, everyone else was kicked. Me and the host remained there.

<Host> You! You c-kicked my players!
<Ezer'Arch> O.o'

 

[Cyan Ryan]

When's 2.0.2? D:

 

[Jellybones]

When's 2.0.2? D:

When it's done.

 

[Chrispy]

Oh lawd. 2.0.1 is out and people are already starting to beg for 2.0.2

 

[Jazz]

You'll get it when enough bugs are fixed to warrant a new version.

 

[Kopper]

Well, c-fail still happens, but it seems only when you join sometimes. And sometimes all the time. (Illegal netvar command color 0 team 0 anyone?) Also, I'd like to give a possible tip for this problem: Host a game of the same type on the same map for about two seconds, then try again. (I didn't think the tip worth it's own topic :/)

These are bugs, and will be fixed for 2.0.2.

Well, that much is obvious. XP

Also, at people begging for 2.0.2:
It's a bug fix, like they said. There's no point to releasing a buggy beta of a bug fix for a buggy beta, is there?