Friesland, NetherlandsMisterPost maybe you should spend a little more time interpreting CyberThunder's statement about your run. He wasn't saying you cheated, he said you could've cheated. It just so happened to be your run that had 2 picnics in it, so he used it as an example.
"All of you are against me because that's the type of people that you are, you don't even follow your own ''rules'', MisterPost's run is split up into 3 segments, each has a minute difference and he still gets accepted? " Where exactly is he calling you out as a cheater here? He is just asking why we accepted your run but not his.
Cyberthunder didn't understand the rules, so in his eyes us accepting your run but not his seemed unfair because he was unable to tell the difference between his and your picnics, so we clarified to him what the difference was.
Now everyone STFU in this thread or I will ban you, don't care who you are.
Option 1 allows you to do the last mission whenever because the credits are timed regardless of when they are.
Option 2 forces it at the end unless you wanna take the 2 minute timeloss, because you can split before the credits.
Option 3 doesnt force it at the end, but involves pausing the timer when it isn't.
Oh yeah I forgot about that :O
It states it has to be an SDA submission though but I guess I could contact them anyway. I beat the segmented WR now so that's something.
Silmaranza and K9 split because SDA (a horribly irrelevant website) told them to, MisterPost mimiced what Sil and K9 did because why not.
I'd say the potential strategies involved with including the credits are worth more than the handicap you gain from forcing to put the credits at the end.
Not even to mention that splitting on the ACTUAL gain of % makes more sense than to do it at an arbitrary point before it. What if we find a glitch to skip credits earlier? You'd get the final % quicker. What if I fall asleep, and forget to skip the credits? It'll have taken longer for the % to be rewarded.
Similar to the 5 monkeys experiment: http://www.johnstepper.com/2013/10/26/the-five-monkeys-experiment-with-a-new-lesson/ Except here we never got sprayed with water to begin with. We splitted before the credits because SDA would beat us up if we didn't. Why do we keep beating each other up if we can just split at the point where % gets rewarded, and not at an arbitrary point like last input?
Just start running any% no dupe. If enough people run it it'll turn itself into a new category. That's how mission% worked. I don't think its a good idea to make this category only to find noone running it.
Basically, show interest in the category by running it. Not by posting a forum message. Good luck.
Well there you go. I'm okay with the 5:40:26 being posted then as I see no reason to believe this run was cheated.
No problem. Now if only I could figure out who that dude was that sent me that PM.
Start time VOD1: 00:20 Start time Wsplit1: -00:03 (Timer started on entering bicycle, not gain of control.)
End time VOD1: 1:34:34 End time Wsplit1: 1:33:37 End time IGclock1: 05:40
Difference VOD1: 1:34:14 Difference Wsplit1: 1:33:40 Timers offset: 34 seconds. Cause: Paused timer, See supplement 1
Start time VOD2: -00:02 (VOD hangs at 00:00 for a while before it starts counting.) Start time Wsplit2: 1:34:35 Start time IGclock2: 06:38
Difference Wsplit2-1: 0:00:55 Difference IGclock2-1: 00:58 Timers offset: 3 seconds Cause: Visible paused timer at 1:34:34.67 (during Catalina2) wsplit time on the dead first frame of the VOD with a duration of 3 seconds + whatever loading screen may have paused the ingame clock.
End time VOD2: 41:11 End time Wsplit2: 2:15:48 End time IGclock2: 22:54
Difference VOD2: 41:13 Difference Wsplit2: 0:41:13 Timers offset: 0 seconds. Legit!
Start time VOD3: -00:02 Start time Wsplit3: 2:16:01 Start time IGclock3: 23:04
Difference Wsplit3-2: 0:00:13 Difference IGclock3-2: 00:10 Timers offset: 3 seconds Cause: Visible paused timer at 2:15:58.32 (during Jizzy) wsplit time on the dead first frame of the VOD with a duration of 3 seconds + whatever loading screen may have paused the ingame clock. Going into the Past Broadcast vod and not the highlight vod reveals a paused timer for a prolongued period of time of more than 3 seconds. There is no way of telling the amount of time passed during stream downtime.
End time VOD3: 3:19:37 End time Wsplit3: 5:35:43 (Adjusted for timer being stopped slightly too early)
Difference VOD3: 3:19:39 Difference Wsplit3: 3:19:42 Timers offset: 3 seconds. Cause: Rounding issues, Legit!
Both the game and timer were paused during stream downtime between both Vods 1-2 and 2-3. Twitch provides no timestamps for Vod creation time (only date). Timing of RTA time is impossible.
555 we tip: start swimming: 23:53 / 1:58:31 end swimming: 24:31 / 1:59:09 Total: 0:38
outrider: start swimming: 25:18 / 2:41:20 upgrade: 26:01 / 2:42:03 end swimming: 26:30 / 2:42:32 Total: 1:12
snail trail: start swimming: 28:41 / 2:44:43 upgrade: 29:35 / 2:45:38 end swimming: 29:38 / 2:45:41 Total: 0:54(u) - 0:57(e)
Total total: 164 seconds Start to upgrade: 38 + 43 = 81 seconds (should be sufficient) Upgrade to upgrade: 29 + 54 = 83 seconds (should be sufficient)
Assuming all 80 seconds were spent diving without waiting on the surface for a while, it should be sufficient unless the water was too shallow. Seems legit. Despite the run being a soft reset. Does this glitch not apply to xbox? I'd look into actual time spent UNDER water rather than IN water, but it doesn't matter anyway because the run is a reject anyway.
Issue 1 (Paused timer during Big Smoke for 35 seconds): No problem, add 35 seconds to wsplit time Issue 2 (Paused timer during Catalina2 for 3 seconds): No problem, add 3 seconds to wsplit time. Issue 3 (Paused timer during Jizzy for 3 seconds): No problem, add 3 seconds to wsplit time. New Wsplit time with inclusion of pauses: 5:35:42.42 + 0:02 + 0:01 + 0:35 + 0:03 + 0:03 = 5:36:26.42 (Onstream time + late start + early end + pause + picnic1 + picnic2) This time is NOT valid because there were more pauses than the ones listed, of which length unknown: Issue 4 (Pausing of both game and timer during picnic): No RTA timing possible. Leaderboards are RTA. Unless runner can provide proof for an RTA time, rejecting is the only option. Issue 5 (Soft reset, so lung capacity fucked): I'm a bit in the dark on this. It seems to be in order but I'd need someone more knowledgeable on the mechanics to look into this and confirm (which won't happen because of issue 4 so theres no point.)
Final decision: The run is a reject because of both the timer and game being paused during two stream outages, making RTA timing using just the vods impossible. Solution: Don't pause the timer during future runs.
Random Point VOD1A: 44:51 Random Point Wsplit1A: 43:53
Difference VOD1A to start1: 44:31 Difference Wsplit1A to start1: 43:56 Timers offset: 35 seconds --> approx. 35 sec disappeared before RP1A
Random Point VOD1B: 16:06 Random Point Wsplit1B: 15:07
Difference VOD1B to start1: 15:46 Difference Wsplit1B to start1: 15:10 Timers offset: 36 seconds --> approx. 35 sec disappeared before RP1B
VOD skimming reveals paused timer at 2:44.83 WSplit time during the end of Big Smoke from VODtime 3:08 through 3:43 (duration: 35 seconds)
tl;dr: This is all the fault of the lack of a "reason for denial" field (and the ability to appeal it.). Send me links to your VODs, and I will point out if and what is wrong with it with timestamps and clear explanations (so no youtube style 'this is bad' comment).
Long stuff: [quote]"What is S even talking about? He never messaged me with any advice, nor Tirean, if you want to tell me something, come to my stream, but you won't do that because you know that you're wrong."[/quote]
While not directly, one of your friends/viewers/someone messages me on twitch and told me he talked to you on skype or whatever and asked me what to do. I gave him advice, (and Tirean told me he did the same). He must've not passed it on in which case he is a shitty friend (or not one at all if he was lying). Ignore what I said about that advice then, I was wrong to assume he would actually relay to you what I told him.
@ misterpost's run, in case of a picnic what mamamia described works. You compare wsplit to the ingame clock and you look at the start/end of some stats. This works for short breaks like misterpost's picnics (about 30 seconds). I'm sure you (cuberthunder) would get away with a thirty second picnic if the timers match.
Things get a bit more complicated if the picnic is longer (5 minutes?) or happens around a part that sets your time to a fixed preset time, although not impossible and this still shouldnt be a problem unless you pull WR-tier performance/luck and people arent too lazy to compare the missing part to other parts from other runs and pull some logic on them.
It's a large trust based system and people don't trust you for various reasons that I am personally not fully aware of by firsthand (only heard stories) so I won't comment on them. I would verify your run myself, but someone with less patience/trust/motivation did it before I did (or they did but since the site lacks a reason for denial field i can't tell which is the case (PAC, PLEASE MAKE THE REASON FOR DENIAL THING YOUR NUMBER FUCKING ONE PRIORITY, THANKS), and currently the site lacks any feature for moderators to see rejected runs so I can't verify. So just link me the VOD(s) and I'll point out everything that is wrong with it with timestamps included and everything, so no simple "your run didn't follow the rules but I won't tell you how and when, so reject".
Edit: NVm, the rejected stuff is visible now. Didnt even see lol. Will get on it immediately.
Could still retime the run and use that time for the leaderboards, but as of now him completely ignoring advice given to him by me and Tirean via twitch PM conversations put him on the wrong side of even the people who were willing to give him a chance, so it's hard to find people motivated to retime his run.
