I'd briefly like to chime in to say that I do not appreciate being called a liar and a cheat even if I have only been named indirectly. I suspect I may be speaking for all of the people you have insulted just in these two forum threads, which is like half the PD2 community at this point. Oh and you should probably stop misgendering Luna, she doesn't like that.

I can also not stand by the unsubstantiated and quite frankly outrageous things you have said about previous and current moderators, especially Zombie.

I think you were already told plenty of times to stop doing that, but once again, stop.

I think at this point you might be beginning to understand one of the reasons the community was unhappy with the moderation.

Alright then, in an attempt to make what very likely has happened as clear as possible, let's test something that closely resembles what can be seen in the Co-Op run.

We will focus only on the lag that you can clearly see in the loading screen in davids video, where his loading screen appears frozen. In order to achieve this I use a script that sends SIGSTOP to the game thread and then waits a set amount of time before sending SIGCONT.

This is host POV with a 3s freeze in the loading screen: youtu.be/CDlHoNEJFgI

Here is the client POV: youtu.be/jmwiTnV-248

As you can see, seeker is already shooting (meaning mask up interaction, mask up animation and weapon animation complete) right as I come out of black screen at approximately 1.5s IGT, whereas I finish my mask up interaction at 2s IGT as usual. In seekers POV you can see that he is also finished with his mask up interaction at 2s on his IGT, while I am not masking up despite my mask up interaction seemingly being completed. He shoots at 4.5s local IGT, which corresponds to 1.5s host IGT because of the 3s freeze.

So let's dial back the freeze time and slow down the video, here is host POV with a 1s freeze in the loading screen: youtu.be/ucnpvL7srzE

And here is the corresponding client POV: youtu.be/eYMUPPHIiWw

You can very clearly see that seeker has just finished his mask up interaction and is in the process of masking up as I come out of black screen, he is very unsurprisingly masking up around 1s ahead of me, and naturally both our IGTs hit 2s as we finish our mask up interaction but they are desynced by about 1s. You can easily see this discrepancy by looking at the millisecond timer (RTA) that I added.

Now before you start going off about this, the reason the RTA is not exactly 1s ahead of IGT is because the RTA timer is not started exactly at the same time the IGT timer is started (as this is rather nontrivial in Payday 2 and I couldn't be bothered), but this is completely irrelevant here. Also keep in mind that there is a considerable delay between the IGT increasing and a frame actually making it out of the GPU. Frame present times are not consistent in any game, especially not in payday 2, and the most recent value for IGT might not make it into a frame as well as the need for the video capture to capture that exact frame (and let's not get into video compression and frame reordering). You can very nicely see this in action here in the slowed down video because the on screen IGT isn't very smooth, but I digress this tangent is going nowhere.

Now my question to you is, what do you not understand about this?

If this is some sort of language barrier issue feel free to answer in german, or hell, Awake can do it in french if he likes. I am genuinely open to hearing your arguments, I really am, but all you have done so far is throw a tantrum, repeat the same incorrect reasoning over and over again and bring up unrelated things.

That is not how these things work.

Plain and simple, the accusing party needs to prove, or at least provide overhelming evidence that supports, the cheating allegations. Not the other way around.

You use this https://www.zupimages.net/viewer.php?id=23/32/sfsh.png screenshot from the run as evidence, showing that a client was fully masked up before the host completed his mask up interaction, which is indeed not how things are supposed to be. Your entire argument hinged on the assumption that it is impossible for this to occur under host-client desynchronization, which was proven to be a false assumption. A compelling explanation for what could have caused the abnormalities in the run was provided.

It is not anyones job to isolate every factor that could be at play here (which is impossible for various reasons), do an empirical study, get published in a renowned journal and attempt to recreate the exact conditions to potentially prove that this could have been a natural occurence. Instead it is once again up to the accusing party to prove or provide overwhelming evidence that supports their claim, which has not happened.

Regurgitating the same fallacious arguments over and over again does not prove that anyone cheated in that run.

i think Tomax definitely cheated at the 'Mallcrasher' level

I think he probably cheated too, and the video is good evidence of that, but as people have pointed out before it is not irrefutable proof.

In COOP, all action data is sent by the host.

This is not true.

if the host's game crashes with spawn players, the client will get stuck in the blackscreen loading panel until it disconnects. This shows that if there is no host pre entering the heist, the client player will not be spawn, and therefore interaction to mask up is impossible.

While the clients do eventually disconnect, crash or hang if the connection to the host times out, this does not show what you say it does at all. Once the game is started, it starts for all players and they all have local in game timers up to re-synchronization with the host timer (and some other artifacts).

To see this in action you can take a look at the video I recorded with Zombie, where you can clearly see that I have not even finished my mask up interaction when Zombie is already taking the first bag, and that my weapon animation hasn't finished yet when the first bag triggers the secure loot objective ony my (host) side. If you don't trust any of those videos or suspect that this is a huge conspiracy where the 10 or so people that looked at this are all lying and/or cheating, feel free to test this for yourself and report the results.

Rejecting this type of run cant’t be a reason to get unmodded or banned.

First of all, no one has been reprimanded nor will anyone ever be reprimanded for rejecting the run you linked (or the Mallcrasher Co-Op run for that matter).

The run you linked (tomex Mallcrasher solo) is indeed possibly cheated, and having the opinion that it is likely cheated is reasonable in my eyes. You can't say tomex cheated with 100% certainty based on this video because (especially on old versions) very weird things can happen in Payday 2, this would by far not be the only occurence of an odd potentially time saving bug that has only ever been observed a few times with no known way of triggering it. I agree that the most plausible explanation is that tomex used an instant mask up cheat on this run, but you can not be completely certain based on this video. If you would like to dig deeper and investigate tomex for potential cheating, no one is stopping you. I don't personally feel this is urgent because he is not relevant to the leaderboards today and has not been an active Payday 2 runner for a very long time, and most importantly the rejection of this run is not tied to this. Something has happened in this run that should not have happened and that was not reproducible at the time, and for that reason the run was rejected, and that's it. No one is saying this run should be verified.

As for the run that nasuper claims is evidence of pizzayumyum being a cheater (Mallcrasher Co-Op), no one has been reprimanded for rejecting that run and everyone (including the runners themselves) agreed that the run should be rejected. What you see at the start of this run could be explained by all 3 clients but not the host having an instant mask up cheat, but the more likely explanation is simply desynchronization due to host lag (and potentially network lag). This exact scenario has been reproduced many times by various players, in fact you can see the hosts game freezing in the loading screen after the point where the timer is started for a duration that would coincide with the premature mask up of the client players as seen by the host. Many things that nasuper continues to claim, for example that it is impossible for a client to start interacting before the host has finished the mask up interaction even if the host is lagging, have been definitively proven false in testing. The run has been analyzed to death by various parties with the conclusion that any abnormalities in the run have very likely been caused by timer desynchronization due to host lag. The run was rejected because it was indeed suspicious, the runnners agreed because they did not want to set a precedent for host lag being abused, and it continues to be rejected because of rule 2 "If the host player has a lag at the start of a heist for around 1 sec or more the run will be rejected.".

Nasuper (and the other supermod at the time) did not get removed for rejecting these runs.

They got removed for a very long list of reasons that I will not detail further, and in nasupers case one aggravating factor was that he continued to publically and privately slander pizzayumyum continuously after the cheating allegations against him were proven unfounded and specifically after being told to stop doing so over and over again.

Saying that the new moderation team and ieatzomb13z in particular are inexperienced and posess inadequate knowledge of the game is simply untrue, in fact the new moderation team posesses much more in depth knowledge about how the game works under the hood compared to the previous moderators.