[quakenet] <minus> i can see why that'd be the case; you don't have much ground contact in teeworlds if you play well, so slopes probably don't bring anything helpful to the table
14:09
[quakenet] <Dune> I heard something like that yeah
[quakenet] <heinrich5991> minus: the version server says 0.7.1 is out but 0.7.2 is already out
14:23
[quakenet] <Dune> best not to update
14:23
[quakenet] <Dune> people would think there is suddenly a new version, try it out, see nothing changed
14:23
[quakenet] <Dune> wait for the next :)
14:24
[quakenet] <heinrich5991> it's just confusing, when opening a 0.6.x client
14:24
[quakenet] <heinrich5991> we should probably have an array of allowed "newest versions", like e.g. the tor network has
14:31
[quakenet] <Dune> I dont see the problem
14:32
[quakenet] <heinrich5991> I open 0.6.5, I see "0.7.1 is out, go download it at teeworlds.com"
14:32
[quakenet] <heinrich5991> I go to teeworlds.com and it says "download 0.7.2"
14:33
[quakenet] <Dune> okay, but that doesn't sound as bad to me as broadcasting to everyone a new version that happened months ago and will disappoint them. just wait a bit and there'll be 0.7.3
14:36
[quakenet] <heinrich5991> yes, hence the proposed solution: [15:24:31] <@heinrich5991> we should probably have an array of allowed "newest versions", like e.g. the tor network has
14:37
[quakenet] <heinrich5991> then we put 0.7.2 and 0.7.3 in there (we obviously can't for these versions anymore because they're out already), and 0.7.2 doesn't get a message but everyone not on these versions gets "0.7.3 is out!"
14:39
[quakenet] <Dune> I don't understand why 0.7.2 shouldn't get a message when 0.7.3 is out?
14:39
[quakenet] <heinrich5991> eh. *put 0.7.1 and 0.7.2 in there
14:42
[quakenet] <heinrich5991> (to make the version server say exactly the thing you want to say: if you're on 0.7.1, that's fine, 0.7.2 is fine, too)
