Note: this still uses protocol 13...as it was just a fix for my mistakes in b13.
Mixing up versions is no longer as problematic as it was in the original networking protocol, but if you change stuff like reload time especially, what the server thinks is going on and what the client sees will diverge pretty drastically. Since the networking is not as complete yet as I would have liked, the client only knows everyone's positions and keypresses, and these come in somewhat jittery. So when you just hold the shoot button down and the server assumes a different reload time than your client, you will still see the rockets come out at your rate, but the server will see you shooting at different times, and possibly also in different directions if you swing your aim around. That means people may be hit by rockets that throw them back for a split second before the server notifies them again of their proper position, speed and health, and people may die unexpectedly being hit by a rocket they didn't see.
This problem also exists to a degree when the behaviour of client and server matches, due to jittery lag, but it's probably a lot worse when it doesn't. So when you change anything about how the classes behave and similar, you should change the protocol version as well.
From what I understand, your going open-source? I hope this means that players will create these features and send them to you, and we get the complite version faster.
Or does this mean you're quittin' the project and leaving it to the players? That'd make me very pissed against the modifyers then.
I'm open sourcing the project partially because you guys want a lot of changes/fixes and additions, and you want them fast, while I have very little time at the moment. If you can change the game yourself, you can get these things a lot faster than I can provide them. Also, seeing as there are already people providing these changes illegally, I don't want to disadvantage those who want to contribute but actually care about copyright, and I want to give zephro and j-factor the permission to continue with their changes.
I will continue to contribute to the game, but I don't think there will be an "official" version again as such, since I probably won't check everyone's changes. We can try to keep an "official branch" though, that may only be edited by one person at a time (as soon as you have two concurrently changed versions, you get version hell). Coordinating this should probably go into a seperate topic. If someone "checks out" the game and doesn't return the sources in a timely fashion (what this means is entirely up to the other contributors) and doesn't answer for a while, development should proceed from the currently available version.
I want to update the first post with the latest 'unofficial' version so that newcomers will be able to play these new releases, but whenever I try to start the lobby, I get the error 'Unable to connect to lobby server - might be down'.
I don't know why this would happen, and I never got this problem. When I checked the Lobby Server when I got back from work, both Lobbies were running and getting connections (There is a Lobby for the compo version and one for the versions that came afterwards, since I had to change the Lobby protocol between these). I switched the new Lobby from my eeepc to the "permanent" server (an old Thinkpad) this morning, but it shouldn't have been unreachable at any time. If this happens for more than 20 minutes at a time and your internet connection is otherwise fine, please inform me about it.