Issues with current timing method setup
3 years ago
Estonia

@Bender Any% normal would be for p1/px/p8 sorc? I guess even in these sorc categories it's just p1 sorc where the timing breaks down due to load times.

Actually one question I have is that I've heard people say "load times are inconsistent", but I haven't had that experience myself. They seem very consistent to me based on the way you play. Even TCP/IP load times are consistent and you can work around it. It's the same in-game where certain actions just make your load times longer and you can strategize it. That's what Slimo did with -ns and it's what we lost when we swapped to IGT. We lost a big portion of strategizing the sorc route which is what made it interesting in the first place.

For example I'm confident that p1 sorc can be faster with act 2 leveling with RTA (it's something I was working on), but when we swapped to IGT the Jail setup was not beatable with anything in Act 2. We made rules based on one specific strategy and inadvertently made it super optimized. This also carries over to other classes. If IGT is maintained then all classes best route in p1 is Jail leveling (I'm generalizing, but only tested assassin and necromancer), where otherwise in RTA you would be behind too much.

@Wafu It's not really ignored, it's just something we have no control over. We could wait another year for speedrun.com to provide these features, but we've waited long enough and the community is mostly fed up with the current situation.

Also when we voted on these issues I was under the impression that this is how it was going to be setup anyway. I'm sure there were others who voted on this premise, but later turned out that it's not possible and was done differently. Well, I would have voted differently and so would have other people. That's a big reason we saw quite a few runners give up and leave.

Retiming promise was another one that probably made people favor IGT, but was later decided that runs won't get retimed.

Timing method setup and retime promise were the only reasons I favored IGT to begin with, but none of that happened.

Inv1ve likes this
Switzerland

"@Bender Any% normal would be for p1/px/p8 sorc? I guess even in these sorc categories it's just p1 sorc where the timing breaks down due to load times."

I dont know, P1? Was more of a random tought to a) leave record at 327 and b ) get the dataproblem sorted. It is kind of a strange solution and would look really wierd if theres like a singled out category while everything else is sorted nicely. True bandaid solution

About loadtimes: I guess we could do some experiments and see if its the same. Like same seed+gear+actions = same loadtime on multiple systems. I agree that IGT favors strats like that (or shrinefishing) and playing around the lag is part of the game. At the same time, if a strong PC gives you a clear advantage, IGT does have its benefits in terms of fairness

Edited by the author 3 years ago
Inv1ve likes this
Estonia

I started a topic for such an experiment https://www.speedrun.com/d2lod/thread/ci3bt

I also tested out the time difference between RTA, IGT and -ns. IGT is op compared to -ns. I'm kind of surprised how little time -ns saves. -ns in p1 normal sorc run saves maybe like ~1 minute. IGT saves ~5 minutes.

If we converted to IGT so we can have a fair competition with the -ns run then that definitely didn't work out. If there could be a -ns penalty and the run retimed into IGT it would still be WR. Edit: or maybe not, I forgot my run exists.

It has created an odd situation now. I don't want to scam 327 of the WR as well with the rules that were put in place. No good solution anymore.

Edited by the author 3 years ago
Inv1ve likes this
Game stats
Followers
758
Runs
2,308
Players
291
Latest threads
Posted 3 years ago
2 replies
Posted 1 month ago
10 replies
Posted 1 month ago
Posted 11 months ago
3 replies
Posted 1 year ago
2 replies