ARMA 2 : OA beta build 84391

[F2k Sel]

The Clear button resets the filters. Perhaps issue with browser/cache/cookie? Or perhaps Back/Forward navigation?

There is aready a field "First affected build", this can be used for the actual build number.
Yet this field by itself is inadequate for the requirements specified by Maruk.

Same in all my browsers.
I can work around it by selecting due tickets and then view all.
Clear only works sometimes, it was the same on my previous PC.
Using View All does take it back to the issues layout but it's different.



Of course there is a field "First affected build" and I've been using it Cheers.

[NoBrainer]

[84388] New: New entry requiredBuild=xxxxx; in server.cfg preventing obsolete clients to connect. Not reliable until 1.60, clients are still able to connect.

How do you use this?
Can't find any info on the wiki about this.

Is it as easy as:
requiredBuild=1.59.84391;

Or is it more to it.
Do people have to have that "correct" version to connect?

[Dwarden]

into server.cfg add this line

requiredBuild=84391;

it's just about the build number not full version number ...
to connect You then need to have same or higher build

[NoBrainer]

ah, great!

Thanks!

Testing later I hope

Works like a charm.
Can connect and start a mission, but get kicked out after a while if build version is lower than recuired.
Nice feature!


BTW, I don't like how you have solved this, regarding messages:

console message:
11:50:20 Player xxxx: Signature check timed out

Server rpt:
No message at all

It's hard to find out what is missing for a client with no hint at all to why he / her get kicked out.
Is there a possibility to get a "readable" message for the reason?
Both in server.rpt and console message and preferrable in game.