Swedennot sure how you skip dialogue like that either. both players spamming does not make this happen. seems dodgy unless you can explain how to do this tbh. i mean its literally all your speedgain compared to the other runs, im pretty sure the #2 run is faster if it werent for the dialogue skipping lol.
not sure why wookies changed time. i submitted as 28.100 because i made sure to check the frames. while 300ms doesnt really matter its more the fact he changed it from 28.1 to 28.4 that feels silly to me imo.
first sub 30, played for maybe 20 minutes or so and got a couple of tries just around 30. realistically if you play this for a few hours im pretty sure sub20 is doable, somewhere in the 15s range is likely the fastest possible, but would also likely require 24h+ of grind.
i had an extremely fast 3x too (5-0, 5-0, 5-1) but got it on my first attempt at 3x/5x and didnt save it, thinking it was easy, that was a mistake. didnt bother trying. the 5x version of that 3x was kinda meh since the 2 additional games wasnt super fast, it was still WR by several minutes though and the 3x was probably sub 2m. dont think ill bother with those categories but realistically you'd get WR in both within an hour of playing.
i reckon this run would be beaten within 1h of playing too. its very far from being hard to beat yet.
i suggest gumper either fully explain how he calculates this magical loading time and shares it with the rest of us, or (more reasonably) stops inventing random time to call loadtime and allow the timer to actually be the timer.
to be clear the time it takes to go from the end of one level to the transitional level is 3 seconds flat, this is the same for all submitted runs, its clearly not loading time. the transition level itself is also not a loading time, its a weird transitional level. the fade from transition level to the next level is consistent across all runs too.
yet gumper removes entirely random amount of time from each run and calls it "loading times". all runs need to be retimed to the actual timer.
tldr #2 run is 3 seconds faster than #1 run. gumpers timing method makes no sense.
"load removed" is so weird because there is no loading being removed he just decided between level time is loading times? and he decided that time is removed entirely differently from different runs?
wtf????
what the heck do you mean by removing load time? the #1 run clearly removed all the between level time, which isnt loading time, but that must be what they cut.
however the #2 verified run did not get that removed, so somehow it is #2 instead of #1? where is the consistency here? the run took less time, but its ranked #2 because the first run just randomly gets to remove a minute worth of time?
?????
gumper how comes you rate this as the 2nd fastest run when its the fastest? why did you count the 1 minute worth of "between level time" on this run but not on the #1 run?
that whole "load remove" makes no sense to begin with, because it isnt a load time to begin with so i am not sure why its "removed", however wheres the consistency? why is it "removed" on other runs but not this?
this run is clearly 3 seconds faster than current #1.
How does level 7 repeat a third time when dying twice instead of it looping back to level 8?
fun game, still room to go faster though. without deaths i would guess you can do sub 8m, wild guess is that around 7m40s is about as fast as you could optimize it.
this game was a pain. so much RNG required to beat the standing WR. Even with a consistent time save of around 8 minutes on the non-rng levels it was easily eaten up entirely by the previous WR good RNG on the large map levels.
The rules need to be clarified, I suggest making these additions to the ruleset for Co-Op:
Friendly fire settings: Any (I interpret this as the current rule, but this way it is written out)
Auto aim settings: Any (Once again, I interpret this as the current rule, but it needs to be written, of course auto-aim could also (probably should?) be against the ruleset as it takes away from the skill of the runner)
Reconnect needs clarification. According to a forum post you can stack team buffs by reconnecting constantly, meaning it provides an advantage via a glitch. However there are also bugs (unable to respawn etc) that can only be fixed via reconnect. As such it should be decided on what the official rules are regarding use of reconnecting in coop runs. Personally I would say reconnect is only allowed if you do not pick team-buffing skills, however this is of course just my opinion on it.
And just to be very clear I think controller ruleset can be specified too, as in
Input method: Any allowed, if using controller you can also use auto-aim
Of course if people think auto aim should be allowed for mouse and keyboard too that description would have to be updated.
