Wotuu

It's being worked on, there's some problems with the domain afaik!

In that case, let's agree to disagree. Let's hope indeed that the SA will give us more tools, would be nice.

I can verify that this is definitely NOT coming from the real Gotcha Anti-hack. What server was this on if I may ask?

I don't think you understand what the issue is. The issue is that you don't know how to filter useless junk, and don't send it over the network. The network is indeed limited, so why should you send useless data over it? This is true. Keep in mind that the projects are hobby projects, and programming something in a language you already know is much more fun than learning another language with all the struggles that come with it. If your anti-cheat is banning people that shouldn't be banned (because what you say is indeed possible), you should make a better anti-cheat. False positives can happen, but if you don't know how to make proper anti-cheat, then don't. You want the cheaters permanently banned, if you keep kicking them they will come back with better tools that beat your detection. Not having them come back at all is the best solution in this case (in my opinion). If bandwidth is your problem, you should add more filters to filter out useless junk. If you don't, then don't complain how the bandwidth is limited. It is not an issue at all.

Take a look at http://www.gotcha-antihack.com/. It's a RCON and anti-cheat tool in one. You need to register on the forums and post in the "Alpha registration and Installation Guide" forum to be able to download it.

Again, if you dont know what to send over the network and what not, you can't blame the software that reads what you send over the network. If you want a server side solution thats fine, but don't blame it on the wrong party. In case you'd like to fix your issue, read a few posts up for my solution Edit: why have battleye kick for it when you want the person permanently banned?

Thanks for the additional info, I'll be sure to do the same when I encounter them in the logs! You too ;)

Sorry for the delayed reply, but yes I am actively banning players on my server. If you're on a private hive, you can ban people for whatever reason you like. If you're on public, you can ban someone for hacking, but you must report the banned player in the Cheat Reporting section of this forum. I run a private hive though, so I can ban anyone for any reason (but I don't). Yesterday evening alone for example, yielded the grand total of 11 bans. My server was full~ almost all night, and I was actively policing it (as in, programming with one eye, and keeping an eye on the logs/chat with the other). The best result was this though: 10:30:49 : (Direct) FuzzyPeePee: what up fellow hacker 10:30:50 : (Direct) Owner: trouble 10:30:51 : (Direct) FuzzyPeePee: <3 10:30:53 : (Direct) FuzzyPeePee: fuck yeah 10:30:55 : (Direct) FuzzyPeePee: got skype ? 10:30:57 : (Direct) Owner: lol watch this 10:31:03 : (Direct) Owner: watch these hacks I got 10:31:21 : (Direct) Owner: look up 10:31:39 : (Direct) Owner: lol 10:31:47 : (Direct) Owner: They don't stop! 10:31:51 : (Direct) Owner: for like 3 in 10:31:53 : (Direct) Owner: min Made my night worthwhile :D. The only lasted for about 3 minutes on the server.

Great! Good to hear :)

attachTo.txt 3 "" !="BoltSteelF" addMagazineCargo.txt Replace all '1' with '3' deleteVehicle.txt 3 "" !="_this spawn fnc_plyrHit;" createvehicle.txt If you use teleport detection, leave it at 2 "". Otherwise, replace all '1 "" xxxxxx' with '3 "" xxxxxx'. 3 means log to file and over network remoteexec.txt 2 "" !="this enableSimulation false;this allowDammage false;this disableAI 'FSM';this disableAI 'ANIM';this disableAI 'MOVE';" !="_this spawn fnc_plyrHit;" remoteControl.txt 2 "" publicvariable.txt 2 "" !="remExField" !="drn" !="dayzHumanity" !="dayzHit" !="dayzLogin" !="usecBleed" !="usecBandage" !="usecPainK" !="usecTransfuse" !="usecEpi" !="dayzSetFix" !="dayzDeleteObj" selectPlayer.txt 2 "" setpos.txt 2 "" !="shot" !="Shot" !="FunctionsManager" scripts.txt NO 2's or 3's. setdamage.txt 2 "1.000000" I never get delays, got much headroom even when the server is filled up (40 players). Hope that helps.

I'm not a star at script filtering, but try this: 2 "" !="BIS_Effects_AirDestruction" !="BIS_Effects_AirDestructionStage2" !="BIS_Effects_Burn" That *should* stop those lines from showing up in your network logs. But don't take my word for it .. I've been doing it the way the tutorial says it should, but it doesn't work. Anyways, hope it works for you!

I'll be honest and say I don't know the details of it, but it's come around so many times that weapons are stored as string references, and not as objects, that I'm assuming that true. This limits what can be done with the weapon. They are fixing that so you can add scopes etc in the standalone. This also goes for weapon history, they can then attach history to a weapon, for a player to view or for back-end to review for possible deletion of the weapon.

Clear, but this is more user error than Gotcha error. I've been running it perfectly fine for a while now. You just need to fix your xxxx.txt and not put 2 "" in everything, because that causes the problem you're facing. Gotcha is not to blame here. (Edit: fyi, you don't have to tell me how it works, I help developing it, alongside my own RCON tool)

Can you elaborate? I thought I was clear the first time I asked. What do you mean with "flooding the RCON" anyways?

How does Gotcha flood the RCON? It only receives, and sends minimal data.

Hi, I'm the server admin of a server with no starting gear. My server is connected to all other Vilayer servers through their hive. There are however, a bunch of servers (public) that give everyone full gear upon spawning. So what happens (or what I think that happens / happened before), people die on my server, join that one to get full gear back, then come back to my server. Since the server I run is fairly popular compared to the rest, they will rather stay on my server instead. Now, how do I deal with this? I can spot this kind of behaviour through the logs, but I don't have time to constantly watch the logs. I could write a program that also deals with it, but that takes time which I don't have at the moment. I also don't want to set this in the server rules, not to give anyone ideas that this is possible (I only just found out this was possible through a Reddit comment!). Anyone caught doing this receives a permanent ban from me. (Someone logging in with starter kit, and coming back with full gear 5 minutes later can't be a legit player, and either way is behaviour I do not want on my server.) Any ideas? Thank you

Thanks for the insights. I'll keep it the way it is for now, and see if it brings in problems when people start doing it regularly. If it does, I may consider going private then.

I unbanned you from my server. Please note that when the Community banlist updates, you'll be back on the ban list again so you'll have to re-post here (I check this forum daily~). Also, if I catch you doing anything suspicious / scripting etc you'll be on there in no time (but this goes for everyone!). Enjoy!

Why would an admin falsify your name on that list just to get you banned? (Unless you have beef with the admin ofcourse.) These logs are really obvious, and it IS from hacking a box with just about all items in the game in. Depending on the other things you may have done, I would've given you a second chance considering you took the time to write up a story about what happened (I banned soooo many people and only one bothered to post here). Good luck, but if the logs are true I can't blame the admin for not unbanning you if he choses so.

I recommend getting Gotcha, and keeping it up-to-date. When the next update hits it should have better anti-hack protection. If you do not want to run Gotcha for whatever reason, let me know and I'll see what I can do when handing over my own anti-cheat code. Can't guarantee I'll do that though.

If this was possible it would've already been done. There's a reason BI is fixing this for the standalone.

I did notice cheaters did get in the logs (identified by other logs), but also some seemingly innocent players (they could very well be cheating themselves, though). I'll create something for this, and add the option to kick / ban (for xx minutes), as I do with everything, and try with kicking first. Thanks either way for your research and reply!

Are you absolutely sure behaviour that comes back in attachTo.log is suspicious? I'd like to know for sure before integrating this in my anti-cheat and issuing permanent bans to anyone teleporting survivors / vehicles around. I can be fairly sure about vehicles, but what about survivors? Thank you.

http://dayzmod.com/forum/index.php?/topic/118203-help-with-logs/#entry1121775 First page on this very forum.

I'm done writing all documentation etc, and it's all up and running, but I'm waiting now for the other developers to do their stuff. When they're ready and the new version is released, I think it'll open up for everyone to read. No clue when that's going to happen though. If you can't wait meanwhile, contact me (see original post)!