ziellos2k

New version coming next week(ish). :lol:

Can we have some sort of alert filters? Like if someone says admin in chat it'll start flashing in the taskbar. :lol:

It was a direct git clone. I'm afraid I don't have the logs anymore though.

Dwarden, the current filters are kicking everyone with 'str' in their name (i.e. Streichos, Stryder, etc).

Quivers being removed when you fire an arrow has (partly) been fixed. Should be in the next update. :)

That seems like a BattlEye issue to me. But I'll take a look soon, just set up a server again so at least I can test without asking others for rcon access. :lol:

Ok, that's not going to work it seems. The console doesn't really work well with Cyrillic according to others. If I send UTF8 encoded strings the entire connection fails. Converting UTF8 to ASCII didn't seem to work either. You might want to ask DomiStyle if he knows anything, iirc he asked for UTF8 support.

I'll take a look later today. :)

Well receiving seemed to work if I recall correctly.

Not sure, back in early dec 2012 I've added UTF-8 support but I guess that only worked for receiving. Not sure. EDIT: You can try changing this to UTF-8 but it could possibly break the entire thing, no idea. ^_^

:lol:

You can try setting the sleep to 1000 instead of 500 in BattlEyeClient.cs line 337. Other than that, no idea. I remember someone else having the same problem in the past but I thought it was fixed. Haven't gotten any reports of it with 1.2.1 though so I don't know. It's been a while since I've touched BattleNET's code. ^^

I have written the code for it like 3 months ago. Unfortunately it still hasn't been accepted into DayZ. :(

Could be because of the packet resending timer, which is currently set at 500ms. Try increasing that DomiStyle. I've already changed it to 1 second in the develop branch. Line 337 in BattleNET/BattlEyeClient.cs

Have you ever checked the engine where dayz is based on?

Not possible. :)

:)

I've always assumed that gotcha did most of it's work server side? No, I've never used it. :P

A2 scripting commands: http://www.ofpec.com/COMREF/ and http://community.bistudio.com/wiki/Category:Scripting_Commands_ArmA2 I'm not fully sure of how things are currently as I haven't ran a server for a few months but this is what I used to do back then. Step 1: Unpack all DayZ pbo's with cPBO Step 2: Grab a random script log from the log files Step 3: Check if it originates from DayZ's code Step 3.a: Open a command console (cmd.exe) in the folder where you unpacked all PBO's Step 3.b: run findstr /snip "<your search string>" * in the command console Step 3.c: check findstr's output Step 4: Did findstr output anything that matches your string? If yes, go to Step 4.a else go to Step 4.b. Step 4.a: Most likely something where you shouldn't worry about. Step 4.b: Most likely something that shouldn't happen. But be careful, it could also be something which is being ran by A2 itself!! + the post above :)

Learn some common ArmA script commands, check whether the scripts ran in the logs are originating from DayZ, if not, ban. :D

Well it does fix the 'sometimes failing ban list', didn't test with the crashing one though.

Hotfix 1.2.1 is available now, http://ziellos2k.net/battlenet/. :)

I can confirm the crash but that's on their end. The unable to request one can be fixed on my end.

@DomiStyle, can you get me a few ban lists that seem to be failing?

I'll pass. :) Let's just hope it's not the same method as mine.. that would suck.. :P