GRIM REAPERS CHEATING AT SATAL Today I'm gonna share with you information that involves the Grim Reapers Competitive team in SATAL cheating (“Spected not gonna lie”). As you all know BEAR (“Grim Reapers competitive Leader”) is also an admin from SATAL, having access to everything involved in the tournament (“Server administration, Scripts…”). This is public info so you all can search it if you are interested. The following info i'm gonna show you all has been filtered by Sean B (Ex SATAL admin, and EX Grim Reapers pilot) he got kicked after this. Sean B was the main programmer from SATAL, he made almost 90% of SATAL script´s code. Bear has been manipulating the script´s from satal in order to get advantage, the follow pictures and text explanations has been written by Sean B: SEAN B FILTRATION My statement regarding code entered into the SATAL scripting by Bear. I'm going to try to be very clear in relation to what is fact, and what is my opinion. So, lets begin: How did I come to realize Bear had put this code in the SATAL script?: Fact - On 01/29/2022 I was messaged on discord by OGC Munted stating the U.S. server had frozen during their scrim against NZA ( discord message log attached ). When I logged into the server I found the DCS process in an error state with a lua error window up, showing the error and code line references ( screenshot of error attached ). Tracking the error down in the SATAL script is how I found this code Bear had put in: if e.id == 2 then local tgt = e.target:getTypeName() if tgt == 'FA-18C_hornet' or tgt == 'JF-17' or tgt == 'F-14B' then local wpn = e.weapon:getDesc() local mName = wpn.displayName if mName == 'AIM-120C-5' or mName == 'AIM-9M' then local tPoint = e.target:getPoint() if tPoint then trigger.action.explosion(tPoint,200) end end end end This code is flawed, and caused a server freezing error when an F18 took a hit during the scrim between OGC and NZA. What does the code do?: Upon the game registering a hit event, it gets the name of the jet type which has been hit and compares that type name to F18, JF17, and F14. If the type of aircraft matches one of those three it then compares the weapon name that was used against AIM120 and AIM9M, and if the weapon matches one of those two it then creates an explosion at the same point in 3D space that the target which had been hit is currently located. This would cause an F18/JF17/F14 that has registered a hit from a 120 or 9M but had not been killed to immediately explode. Bear does not deny that he authored this code, but has stated to myself, Moltar, and likely others that it was a test. That he was attempting to find a solution to lag/desync or any other term you want to use causing hit-no kills that, according to him, should have been kills. Is there any possible way this code could target hit-no kill events caused by a network related anomaly?: Fact - NO! I cannot overstate that this is not an opinion, not a guess, this is a fact. No part of that code makes any attempt to determine if the hit-no kill was the result of DCS's physics, probability, and other related code functioning as intended, or if a network anomaly had not only occured, but had been a causal factor in the hit not resulting in a kill. Could this be an oversight? Could Bear have simply overlooked coding anything that had to do with targeting lag/desync, the primary goal of his so called test? ( very hard not to consider this a fact, but.. ) Opinion - No. Bear has more than enough experience with coding to know that if such a determination could be made programmatically, problems related to network issues in games would be non ( or very close to non ) existent. As the developers of DCS, and any other game that uses a network connection, would have coded their games to DO SO ALREADY! If fixing the effects of network anomalies with even expertly coded algorithms created by highly experienced, highly paid teams of developers was even somewhat viable, let alone accomplished with a handful of generic API code, the holy grail of a "netcode" fix would already be upon us. If being a genuine, benefits all players attempt at fixing hit-no kills caused by lag/desync is something that is obviously nonsense, why would he say that? Opinion - What else could he say? With not coding it using things that stand out ( such as exempting GRC tags, or specific player names from its effects ), even though I wrote 90% of the main SATAL script, and all of the logic and control it uses, the script is just shy of 2000 lines of code. The likelihood that I would have ever realized it was there without specifically looking for it is extremely low. The fact the code caused an error on my U.S server is the only reason I discovered it, and confronting Bear with it surely caught him by surprise. The only way what he stated makes any kind of sense, is if it was done so under the context of a knee-jerk on the spot panic grab for an excuse. If Bear put this code in, and not YOU, how come the U.S. servers were running it? Fact I created a VPN link between the U.S. server and the EU server, through which command and control of the U.S. server could be handled by the same setup server you all use to set passwords for the EU server. As well as sync a mirror copy file share of the code base on the EU servers to the U.S. servers, so the servers are running the exact same missions/scripts etc at all times. If anything changes on the EU side, the U.S. side changes as well. Ok, maybe the reason he gave is BS, but what evidence do you have that he consciously did it to cheat, or made a clear decision to do something ethically wrong? Fact - Not only does the code in no way target lag/desync, part of it only exists for the sole purpose of exempting the F16 from his so called "test for a fix", the jet he exclusively flys, and strongly urges his team to only fly, even at times directly ordering team members not to fly a different jet when they had wanted to. Myself, and I'm sure many others can attest to how frequently Bear would state other jets/weapons/systems were overpowered, operated at a higher level of performance than they should, and should simply be banned. If anyone can provide a feasable reason why one would exempt the jet they fly from a good intentioned innocent fix for lag/desync, I will stand corrected on this being an opinion rather than fact. The fact this "test" was carried out on the live SATAL script, ran by all DCSWE competitive servers, goes completely against the best practices and general guidelines we've established for how we operate, not to mention common sense. Testing is carried out on our own local servers, and even when testing is complete and code is ready to go live, Bear himself is adimate that changes only get added at the end of a block, even when those changes are simply adding in functionality that should have already been there ( having the script track and enforce teams only flying the same jet type in rounds 2 and 3 of a match that they did in the 1st round came late, as we were behind the 8 ball on time ). And while he put this code in prior to a scrim rather than an official match, it's worth noting that the other team was not informed of this "test", and by Bears own statements when I called him out on the code, he was expecting that team to fly jets that would be affected by it. Even if one is to say that sense he exempted F16s and didn't limit it to just ones flown by him or his team, this couldn't have been done to gain an unfair advantage while ignoring the fact that limiting it to tags or player names would be a massive jump in risk, and that tacviews of GRC matches will show quite a few cases of hit-no kills, all of which according to Bear must have been caused by some outside, non intended factor. You still end up with a DCSWE Admin, unilaterally and secretly adding code which during events that decide whether a player lives or dies takes control of the outcome away from the game and places it squarely under his control. Opinion - The fact he is still an admin of DCSWE, should be of serious concern to everyone that flies in its events, and raise the question of why things as trivial as not exporting a display to your primary monitor can be labeled a cheat or exploit, but yet blatantly unethical, if not clearly cheating, steps to alter events in the game without anyone being aware and only exposed before it affected a match by pure luck ( or bad luck, from Bears perspective ) by an Admin seem to be... no big deal... ?????? I could talk till I'm blue in the face regarding how clearly this was not a test. But at this point I feel I'd be beating a dead horse. If there are any questions about these events, or if I can provide clarification, I'm willing to respond to such requests. SCREENSHOT FROM DISCORD [GRC] SeanB — 01/29/2022 if e.id == 2 then local tgt = e.target:getTypeName() if tgt == 'FA-18C_hornet' or tgt == 'JF-17' or tgt == 'F-14B' then local wpn = e.weapon:getDesc() local mName = wpn.displayName if mName == 'AIM-120C-5' or mName == 'AIM-9M' then local tPoint = e.target:getPoint() if tPoint then trigger.action.explosion(tPoint,200) end end end end ? [GR] Bear — 01/29/2022 Wanted to see if if causes problems in scrims [GRC] SeanB — 01/29/2022 Code that ensures anyone that isn't flying F16s, like we do, will explode if hit? [GR] Bear — 01/29/2022 correct, its coming out [GRC] SeanB — 01/29/2022 That's well out of grey area and into full out cheating. [GR] Bear — 01/29/2022 I put it in for a scrim, to test, it'll be out scrim was all f16 [GRC] SeanB — 01/29/2022 What part of it were you testing if you had no planes to shoot at that would trigger it? [GR] Bear — 01/29/2022 was expecting an f14, but they didnt bring one [GRC] SeanB — 01/29/2022 So "they" were another team, and they were not aware of this test? [GR] Bear — 01/29/2022 what are you getting at? [GRC] SeanB — 01/29/2022 2 + 2 usually = 4, what you're saying currently adds up to something like 6 FYI, that code doesn't work. It through an error on the US servers during a scrim of OCG vs NZA. [GR] Bear — 01/29/2022 the code is out, I am still going to test it, I want to get around hit no damage not testing in matches [GRC] SeanB — 01/29/2022 You're smarter than that. Please don't talk to me like I'm not. You don't test code to solve a bug in a game that only solves it for us. I realize you want to win, but I suggest you do a risk vs reward analysis. [GR] Bear — 01/29/2022 Well, if I wanted to solve it only for us, I'd put not string.find([GRC]) in it. I put it in before scrim vs WDF. I had every intention to take it out, plus, if you bothered to show up to practice, youd find out that most are flying different aircraft now as f16 is broken. Including JF17 [GRC] SeanB — 01/29/2022 Except for that fact limiting it to only GRC names would be a trail to the cause. While F16's could be a bug Cmon man LUA ERROR FROM THE SERVER WHICH CAUSED SEANB TO LOOK AT THE SCRIPTS Burnie "Munted" — 01/29/2022 Hey mate, server's playing up. Most people are just seeing fronzen planes Sean B. — 01/29/2022 Want me to restart it? Or did it straighten out? Burnie "Munted" — 01/29/2022 Nah, we're going to scrim on our own servers tonight Sean B. — 01/29/2022 Rgr Burnie "Munted" — 01/29/2022 Can you get it restarted anyway tho, as we have our match later [12:46 AM] Is server 1 or 2 better? or the same? Sean B. — 01/29/2022 Same. [12:46 AM] Ill reset the servers. Burnie "Munted" — 01/29/2022 ok, thanks So as you can see satal is corrupted right now, bear cheated and no one knows what as been able to do all over this years, player disconnections from the server, other type of scripting? ¿ No one should trust right now in this competition and less in Grim reapers Competitive.