Similarities

slimedemon is w coast and he gets 160ms, you'll be fine. the korean on the other hand, 400ms gamer go.

idk man it could be legit. 119-2 seems fairly legitimate to me, maybe you're just bad? i mean...i could do that with my eyes closed bro. just get better at the game LOL?? btw getting similar KDs isn't necessarily hard, especially with the PMG, it's not 73-15 or whatever but it's near that KDR, if the image is from EU then i know who it is and the guy is cheating, but not everyone that does decent-well in FC is cheating.

Did this already with the cheat this guy is talking about. Also gave him information on how to detect the cheat using their own measures. It's now just a matter of time waiting for the team to implement and test the methods I gave to Matt, it's coming, just be patient.

Probably related to him having a rank on the forum, for example, if someone tried to block a moderator the same thing would most likely occur. Don't think it's intended behavior.

Looks to me like the switch on your mouse is dying, when you hold RMB it's actuating several times. There IS a bug where you unmarksman randomly, but that's not what's happening to you here.

Wow, even I'd forgotten about the in-game video recorder. I still had some videos from when that was in the game a while ago, but most of them were just there because I misclicked the button. Fun times though.

Shit talk my coywolf again and we're gonna fight.

That's actually a half-truth, putting the entire binary in something similar to VMP is a terrible idea, the reasoning being that adding a virtual machine adds overhead. Period. PUBG saw a notable performance decrease when running through a VM due to the nature of VMs, and outside of a VM, you can't really do much to "encrypt" things, you could encrypt pointers, but that's not necessarily hard to figure out, Black Ops has done this for years and it hasn't stopped cheaters, as for the public SDK generator, it's going to break every update because the UObject struct changes every update, a lot of things change every update, but that doesn't stop people from using signature scanning methods, as for linear aimbot detection, it's something I've done in 10 lines in a Source Engine game. It's incredibly simple, but it's something one must have an understanding of to implement properly. EDIT: Please make it easier to merge posts btw, it's incredibly unfriendly toward users currently.

As someone who has been providing input on the anti-cheat solutions and how to better them over the past months, EAC is no better than BE and vice versa, it all depends on implementation, I've seen them do a lot in the way of anti-cheating measures, not only regarding their own internal methods, but also going as far as hardening the existing implementations.

Yeah, that's a yikes, good luck you two.

Nice one sided form brubber duck, anyway, stuff is coming down the pipeline to deal with cheaters, that's about all I can say.

Thank you for reiterating what has been said literally a post above genius, and no, that's definitely not the case lol. The first shot the object near the opponent didn't render, every other shot clearly went through the opponent and did not hit the railing or any other object.

First video is bloom related, second vid first shot the object probably didn't render, but all of the other shots were not the railing, you can slow it down to 0.5x or 0.25x and see that I am not shooting near the railing, rather over it or under it.

yeah, that's gonna be a no from me dog.

lol

Your usual BE sucks and everyone is cheating thread. (BE does suck though.)

yea bro give me the skin too, i never participated but i deserve something too

Once again, this makes zero sense, there is one engine flaw that is used by cheaters and the rest is just not the engine's fault but straight up BattlEye failing at what it does, as it stands the variant of BE in the game is garbage. The speedhack exploit people use is a result of the engine, everything else, whether it be aimbot, ESP, triggerbot, whatever has nothing to do with the engine and does not impede on BattlEye's ability to do its job. The anti-cheat implementation is not the fault of the engine, it is down to the developer to do things correctly, not the engine, the engine is just a system of libraries that the game is built on top of, I've already given Matt Scott some tips for detecting cheats, including proof-of-concept code, I won't speak too much for obvious reasons, but things will be changing in the near future if internal testing goes well.

It never stopped cheaters after week one to be completely honest with you, all it did was make it slightly more difficult to hack the game because you couldn't access game memory as easily anymore, as soon as people started using exploits to get around that it was free game, even if you continue to update the anti-cheat with newer versions, BattlEye is so publicly used and documented that anyone can find information on it and how it detects cheats with a mere Google search. Rainbow Six Siege and PUBG both use the "best" variant of BE and both of them still have terrible problems with cheaters, I believe it was a mistake for the community to put so much on an anti-cheat that has proven itself in the past to not be effective. I've already spoken with Matt about the cheating issue and the route that should be taken to remedy it, but with how swamped the development team is currently, it could take months before things start going that way.

I enjoy it, I'm already nearly max level (that content promotes, seeing as you can level beyond 50), it's just buggy.

If it starts at 5PM PDT and you push it forward 5 hours, that'd be 12PM PDT, 3PM EST, people who work and attend school basically wouldn't be able to attend the event on any day except weekends, push it back to 10PM PDT and it's not 1AM EST, most people will be asleep and the night shift employees will be at work.

That's just flat out wrong, game's age doesn't have a direct impact on the ability to change graphical fidelity, nor does the age of the engine. CS:S had bloom and HDR added in 2010, along with Bethesda going from creating games that looked like garbage even for the time, to games that look a lot less garbage but still garbage...for the time, and they used the same engine the entire time. The games weren't rebuilt from scratch either, FO4 has code in it from Skyrim and looks far better than Skyrim, and FO76 has a bunch of placeholders from Skyrim and code from both FO4 and Skyrim, but still looks far better than Skyrim and FO4. Same engine, FO76 is even reusing assets from FO4, but once again, looks far better than FO4, from Skyrim to FO4 (reminder, FO4 is using a lot of code from Skyrim), they added light rays and many other improvements to graphics. This is all coming from a developer that refuses to update their old Gamebryo-based engine to not rely on an FPS cap, because if your FPS is above 60, the physics freak out and you run like the flash (well, this is kind of a fib because FO76 just released a patch to fix that.)

Thank you captain obvious, did you bother to read my statement? I said I'm not taking either side, I'm simply stating that TTK is not the only thing to factor in when making an argument for or against a weapon.

I'm not saying it's imbalanced per se, just that TTK is not the only thing to think about in this scenario. Not making a statement on whether or not the RFP is OP or not.