$able

Check your server console/log for popular "warez" PIDs like 76561197960270647 (there are others of course).

It's not exactly a "huge" issue, but believe me, I'm trying to solve all issues regardless of whether only one person has it or many. And yes, this has been investigated thoroughly. The problem is that this is unfixable because it's hardware-related. If your hardware has problems dealing with the amount of network packets in this game, unfortunately there is nothing I can do to fix this. Your modem/router is indeed the problem here. If this was a BE-related problem you would get kicked in the lobby as well, but you don't. The fact that you only get kicked when joining the game shows that this is related to the great amount of packets being sent and received (post-lobby) causing the game's connection to lock up. Yes, your ISP fixed the problem in the past, but now it seems to have returned. I can't tell if it's an issue on their side or a problem with your router (or both), but something is definitely wrong and only they can fix this.

Could you please tell me what those issues are that haven't been fixed for years? Just to clarify, BE is compatible with all hardware, the problem is that certain routers can't handle ArmA's unusually great amount of network traffic and hence "lock up" (due to some sort of flood protection/prevention), which eventually causes the BE kick. So BE isn't actually at fault here. Again, could you tell me what sort of routers/modems you are using? Also, are you kicked even when just staying in the lobby?

Do you know anyone that gets this error? If not then read my previous post.

Why would you want to block them in your scripts when the game server itself already does that for you? ;)

It's obvious this happens to those using illegal/cracked copies of the game, so it doesn't seem to be a bug at all. And yes, it appears there are a lot of players using cracked copies and trying to play online with them. I have seen this countless of times on my own local server and most of the time they show up to be having the same PID, which proves that they are using identical copies.

Except that VAC hardly does anything and is quite ineffective. The vast majority of users do not have any problems with BE at all. Anyway, do you seriously expect any help after coming here and just throwing insults around? If you do please tell me what sort of router you are using.

Did you ask them? The fact is that you all use the same router/ISP, so it's obvious that this is a connection problem. You can stay in the lobby just fine, which proves that this is not a BE-related issue (BE is running all the time, regardless of whether you are in the lobby or the actual game). The only network-related difference between being in the lobby and being in-game is the amount of traffic, so it's clear that this is where the problem lies.

If that's the case then it's your ISP temporarily blocking your connection due to some sort of flood protection. The reason this doesn't happen in other games is that ArmA's network usage is unusually high and Altis likely causes the amount of traffic to increase even more. I'm sorry, but as I said via email before, this problem is in no way caused by BE (the kick is only the result of the above) and therefore I can't do much about it. Please try to contact your ISP regarding this.

Check your BEServer.cfg for a "maxCreateVehiclePerInterval" or similar setting.

The BE files only need to be present in the install folder (which is as easy as it could get). Of course they are also automatically copied to the BE working directory. Anyway, that's definitely not the problem in your case, BE seems to be running fine on your server. I'm not sure what the cause of the FPS problems is, but "Client not responding" kicks can happen from time to time due to game crashes, network timeouts, etc..

May I ask what your exact problem is? As long as BE loads fine and you don't get any errors there is nothing to worry about. BE simply needs to be present in the BE install folder ("Expansion\BattlEye" if you start your server via the OA executable). It will then be automatically updated in the BE working directory and no, it doesn't have to be updated in the install folder.

I don't think so. Are you sure the A3 server started on the same port both times?

Thanks for letting me know, I'm sorry for that. This kick/violation should be fixed now. Feel free to send the server admin a link to this post so that he will hopefully unban you. Of course he is not globally banned.

That definitely didn't fix anything (the problem is not related to your BEClient.dll), your issue just coincidentally went away at the same time.

Could you find the crash information at the end of your .RPT file or in the Windows Event Viewer and post it here?

What OS are you guys using?

You need to have a separate BE working directory (which can be changed via -BEpath or -profiles) for every server instance, otherwise they block each other from updating the BEServer.dll.

That's a funny argument. You are saying that because BE might not detect 100% of all hacks it sucks. Well, then obviously any anti-cheat sucks. Plus what you are talking about is a bypass, so of course BE's anti-script features would not work at that very moment. But I guess the fact that you will likely get banned a few hours/days later when using such a bypass doesn't count, right? ---------- Post added at 00:42 ---------- Previous post was at 00:30 ---------- "Millions" sounds like quite a lot. Did you ever check the player count on the DayZ website? According to that number nearly 150,000 global bans are not that bad I would say (but who am I to judge this?), considering that the vast majority of cheaters plays DayZ. Btw, in case you haven't read my previous posts, I always said myself that BE is totally ineffective in OA since cheaters hardly care about getting constantly banned because of the unlimited supply of cheap stolen cd-keys. Fortunately that's no longer the case in Arma 3.

I was talking about the DayZ community (which is still part of the overall ArmA community) because that's where most of the hate is coming from. I don't feel like the majority of the more informed ArmA community hates BE.

If you want actual proof go get it. Sign up on popular private hack sites and see the constant complaints about global bans for yourself. Then compare it to other games. That might cost you money though, so I guess it's not an option for you. But obviously there is no "easy" way to get actual proof.

I'm not sure what you mean, you can test RCon without having to restart the server? The default ports (client-side and server-side) have been the same for a long time, maybe even since OFP.

Of course I don't listen to such people, but to be honest sometimes it's quite annoying when it feels like the majority of the DayZ community hates BE, not only because it can't fully prevent all the ridiculous script hacks, but also because so many supposedly get banned by BE "for no reason" (posted everywhere on the internet), which is even more beneficial for its reputation.

Here we go again! Another one who hasn't yet understood that this game engine is so much different from any other that's out there. But right, it's 100% the anti-cheat's fault. Maybe I should listen to people like you and simply quit? BE's reputation is totally ruined anyway, regardless of it being so much better than VAC or PB. Bottom line, if you think that BE sucks please ask some cheaters (private hack users) how they love their daily bans.

The BE Server always listens on the game server's port (2302 and 3302 in your case), not on 2304. 2304 is merely the port being used locally by clients, so it has nothing to do with the server. Other than that, are you sure that everything is set up correctly and your A3 server actually runs on port 3302? Did you try to connect to RCon yourself?