I've began the process of creating new categories. The first batch of individual levels are up, the remaining levels and pet dungeon category to be created in the following days, so hop it evil keepers and smash out those times!
I've decided to ban the use of /console for new runs beyond this point. I am sure there are quality keepers willing to earn their rank of master who can surpass the two hour mark for a full run.
I've also had the idea of "waiving crash time" - since DK2 crashes a lot and this might alienate full game runners. How would you feel about this?
Good luck evil ones!
Good moves all around, having a waiving crash time is a good move for older games, although the GOG version is reasonably stable thankfully!
Hey guys!
What is the current decision about how to deal with game crashes? I just had a run which most likely would have been a sub 2 hours run, but my game crashed 2 times.
I feel like I might be able to beat the 2 hours in the future, but starting a run and knowing it could crash anytime actually makes me feel very anxious.
I don't know what the odds are of it crashing during a run, but I consider it "distinctively likely".
Although it is unheard of for actual crashes to be mitigated into the final time for any speedrun game, I need to take into account the general stability, age and compatibility as well as to bring a modern realistic approach so that people can speedrun this game and have as much fun as possible.
Therefore I will permit pause or reductions in final time due to crashes, provided that...
-
You have a timer running (livesplit) separately so I can see its the same run.
-
An analysis is made to ensure you're not trying to splice or intentionally crashing the game.
-
In the accompanying game description you timestamp clearly where the crashes are and allow the mods to calculate it instead of pausing or reducing the end time yourself.
Only time from the crash itself will be count, not the level progress you crashed on, you must save often and frequently.
All hail 90s games!
