backward compatibility

[AltF4Esc]

Hey, I'm trying to set up a 2.8 b4 server, and I want @ least back to 2.7.1 to be able to join. It will not allow anything before 2.8 b3 due to "DoubleBind_Time" not at default value. I did not change this value. it sits at -10.0. Any help is appreciated.

Thanks
¬Joe

[Z-Man]

There should be no need to worry if you leave everything to default values, the server will be fully compatible back to 0.2.5.0. You only need to worry about DOUBLEBIND_TIME if you actually want to disable double binding; in that case, you'll need to forget about letting 0.2.7.1 clients play, as they don't respect that setting yet.

Reading again and finally understanding: So you run the server and it tells you it won't let in old clients because DOUBLEBIND_TIME is non-default? Hmm, that should not happen, -10.0 is the default value in both the config files and the code. Try deleting all lines with DOUBLEBIND_TIME from all your configuration files.

[AltF4Esc]

Commenting the setting out fized the problem. Thanks! Only other question atm, CYCLE_RUBBER_MINDISTANCE_RATIO now deviates from default keeping anything before 2.7.1. That is fine by me, but it did not show this message until I fixed the DOUBLEBIND_TIME. Does it display the version compatibility issues in order? (iow: If there are any other compatibility issues, will they concern clients before 2.7.1, or might it not be telling me about a more recent compatibility issue?)

Thanks,
¬Joe

[Z-Man]

You're right, only the most relevant messages are shown. For example, there should be a message about pre-0.2.5.2 clients having problems with BRAKE_DEPLETE, but it's masked. But you'd know if there were more serious problems with previous versions: if there's a setting change that causes slight problems with 0.2.7.0 (like the rubber_mindistance things) and another that causes 0.2.5.0 to be locked out, you're informed about both.

[AltF4Esc]

Awesome. That's what I needed to know. Thanks for all your help.

¬Joe