that is what I understood. But it is not an option because 90% of the players use the regular release and to not patch their clients to the available beta. Even I do not patch to beta.
Originally Posted by Focher
Why BI can not release a hotfix for that major issue... but anyway they are always slow with this.
---------- Post added at 08:56 AM ---------- Previous post was at 08:40 AM ----------
You need the latest OA beta for your clients to avoid this BUG.
Originally Posted by Jedra
That's as well my case, because the normal gamers do not know about it ... they just ignore your server after get kicked very often.
BI is very slow, we waiting since 4 Month for a minor fix of the Linux server and as well for such problems they are more nonreactive.
The latest OA beta only fixes PMC and BAF issues with signatures and is only needed on the client. Probably had to do with the encryption.
A new official patch is probably imminent, lot's of patch activity lately.
Updated linux server will probably be released around the same time, while Eddie is currently trying to whip up a workaround for the yellow-dot problem..
v2 signatures should work just fine. But not all mods have v2 signatures, as you pointed out Jedra.
And you're correct, ~500 byte bisigns for v2, and ~250 byte bisigns for v1.
.bikey files have nothing to do with it. You can create v1 and v2 signatures with the same (old) bikey.
Best contact mod authors to deliver v2 signs. Perhaps some already have but didn't make a new official release, just made the bisigns available in some thread (in that case let me know and i'll add em on SU).
I suppose I could also add a six_... bikey and v2 signs per modfolder that currently doesn't have v2.
Create a ticket if you want me to look into that.
Also it's best to drop the bi.bikey file, as it's superseeded by bi2.bikey.
Last edited by Sickboy; Aug 17 2011 at 10:27.
Thanks Sickboy - as I suspected. It would be great if Six provided a temporary V2 signature where one was not available. This would be especially useful for mods that are no longer updated. I will raise a ticket in DH today.
Originally Posted by Sickboy
EDIT ----> Ticket #23523 created!
Last edited by Jedra; Aug 17 2011 at 10:42.
Thanks Jedi Ra! I shall try making it before the end of the week
What really amazes me is that there are still so many public servers out there who have just enabled Battleye (or even worse nothing at all).
Just enabling Battleye means, people can connect to such a server with whatever addon they want (and those are not always nice addons).
Battleye doesn't check addons!
Wake up server admins, enable v2 signature checking too. It's a 1 minute job.
You should be in control what addons can be used on your server, not the user who connects!
well if you have no problem with people using any addon they want, so why not
especially if you are lucky not to be visited by game destroying cheaters
Because generally speaking "Allowing any addon people want" means big chance of issues in MP, besides the hack-possibilities.
Originally Posted by PvPscene
Given, that's up to server admins, but at least you know what is the probably cause for issues you're experiencing, if you do not deploy signatures together with BE
dedicated server v1.60, with hotfix 4 - build 87662.
verifySignatures = 2;
When people connect with V1 signatures, why don't the RPT show this?
Or the console?
It makes it hard to know what went wrong and to help the ones with problems.
Or do I have to do something special for these messages to show in ether console or RPT or both?
ok, thanks for this discussion it was very helpful for me ^^
hey ive just installed the game on linux using latest patch. has this issue been fixed in the patch?