Forum posts

Forum: Desperados III

Thread: Garbage Rules

Started by: KhloëKhloë

@makvasicmakvasic: Imagine running a game where mods threaten to delete your runs if the game gets patched.

And I'm not exactly sure how you can possibly know what we did or didn't play. I've played the game and I would consider speedrunning it - that's why I'm here, duh. But I don't speedrun ILs, so I'm instantly not welcome, and the rules are unexplained and every submission contains a risk of having your run removed and bans even things that are features of the game.

And if you've read the moderation rules, it states that the mod doesn't own the leaderboards. And if people who want to run the game disagree with the rules, it's not right to ignore them.

 

Forum: Desperados III

Thread: Garbage Rules

Started by: KhloëKhloë

Also not allowing to use mechanics of the game (time acceleration) seems pretty unreasonable. It's literally what you are supposed to use during regular gameplay, so why ban it in a speedrun.

 

Forum: Desperados III

Thread: Garbage Rules

Started by: KhloëKhloë

Indeed, the rules make absolutely no sense and are not even properly listed. Rules shouldn't be in Guides but in Rules. Please fix it.

Also having rules set in such a threatening manner is very discouraging. Either split the runs into Glitchless (that doesn't allow any glitches) and Any% (which allows all glitches from all versions - And it's super easy to get old versions if you own the game) or, alternatively, have Any% Old Patch, Any% and Glitchless if it's such a big deal that someone would run on an old version.

This is so dangerous because of the fact that the devs are the ones to decide what is and isn't intended behavior of the game, so you'd have to remove runs that use anything that gets fixed. And just that makes everyone pray that they don't make a new version that fixes anything they change.

Most speedrun.com communities are primarily focused on Any%, which mostly means using the lowest difficulty and all glitches from any versions - if any of that is a problem, then it's time for a new category. But these leaderboards just seem like the exact opposite. You shouldn't be removing runs just because a new patch comes out and you shouldn't have the only difficulty be the hardest one. Obviously, non-existence of full-game leaderboards is also insensible in this case.

KhloëKhloë, HannySHannyS and 3 others like this. 

Forum: Someday You'll Return

Thread: Important: Framerate rules

Started by: WafuWafu

As of 26th June 2020, all runs should be capped to 144 FPS or lower. Framerate in this game affects way too many things and it would be unfair as people with very good PCs would be able to utilize its advantages.

You don't have to show your FPS during the run, however, it's recommended to show it via Steam, RTSS or Dxtory. If your QTEs are instant or there are any other glitches that require high FPS, your run would be invalidated.

Lowering your framerate (via game, RTSS or Dxtory) during the run is allowed to be able to simulate a weaker PC, which is on a significant advantage in some situations.

 

Forum: Someday You'll Return

Thread: Notes for new runners

Started by: WafuWafu

To use auto-splitter, rightclick LiveSplit -> Edit splits... and click the "Activate" button. Then click the "Settings" button next to it and tick ONLY the version you are using. It's set to 1.1.0 by default as it's the fastest version.

If you want to use auto-splitting, you need to have 13 splits. There's 12 chapters, but Chapter 1 is split into 2 parts, switching after you arrive at the forest with the car. If you are not using any splits and only show one time, untick the "Split" checkbox or the timer will end on chapter change.

Finally, press ok for the settings and for the splits as well, then rightclick LiveSplit -> Compare against -> Game time.

Added splits template into Resources if you don't want to make own.

Note: The timer doesn't start or end on its own. You have to start it manually when you gain control of the character and end it when the timer stops during the credits loading. Accuracy shouldn't be a problem.

 

Forum: Someday You'll Return

Thread: Notes for new runners

Started by: WafuWafu

If you're interested in running this game, there's a couple of things you might want to know.

1. You should activate the auto-splitter. It exists so that nobody is in a disadvantage. Manually re-timing your pauses will not be considered valid. Not using this makes leaderboards inaccurate.

2. Version 1.1 (manifest ID 8534491501929628930) is the fastest for Any% runs.

3. Purifying a heart is slower than destroying them, not to mention you have to craft the potion.

4. Beast ending is the fastest.

You can always contact me on Discord with any issues / glitches / questions.

 

Forum: Diablo II: Lord of Destruction

Thread: What constitutes a "load"?

Started by: DrClicheDrCliche

@DrClicheDrCliche There can still be changes as to what actually counts as a load. The load removal may still be changed if issues are found, so it's a bit hard to tell exactly right now.

The question is, are you interested in doing this work? Because if not, then it's pointless for me to give you the explanation, because I know how to make the script, it's just not really needed that much from what was told to me.

But anyway, there's 2 things that we count as a load:

1. When player selects a character, it seems to be from the first frame where the doors start opening (not the frames when the doors are closed). If you'd check the frames where the doors are closed, you'd include the TCP/IP loads, which are only supposed to count as a load after the doors start opening, otherwise there's no punishment.

2. When player clicks save & exit, you should check if this part of the screen is stuck (basically the center of the pentagram): https://prnt.sc/ss0pva (that happens after clicking the button) once you're in the menu, the timer should continue again.

 

Forum: Diablo II: Lord of Destruction

Thread: LiveSplit Setup guide

Started by: Teo-Teo-

If there is any problem with the timer, you should report it to me via Discord DMs. That way we'll be able to figure out why something doesn't work for you.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@327327 Oh, no, I didn't mean that. What I mean is that if you splice a run, you want it to look real. If someone streams the runs, they instantly gain one layer of credibility (because many people will think "oh it's live, this can't be spliced, they already reset 4 times and it's not prerecorded because they talk to the chat"). This has been done in speedrunning and it's easy if you don't have to play the audio.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@stasyszystasyszy You don't necessarily have to restart the leaderboards, there are ways around this.

@327327 Allowing no sound in a game with competition (let's be honest, D2 is relatively large) is a risky step. You can effortlessly splice a run without sound, create a few sample runs, run a stream on Twitch, stream those sample runs, then switch to the spliced run and everything you have to do is talk to the chat and act like you react to what happened in the run. It might sound complicated but no, people have done that. And people have spliced even runs with audio, they put in the effort to actually align the audio perfectly. That takes insane amount of effort. Having no audio makes this super easy.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@BokserKabatyBokserKabaty I understand where you're coming from. The thing is, you save and quitting for shrines etc. will always be a time loss. You cannot do that over and over regardless of the loads being removed. But what can, on the other hand happen is this: You wanna farm for a shrine, the game save & quits nearly instantly, wonderful. Or you will save & quit and the game will hang for 8 seconds.

If you just look at the leaderboards, there are people with times 1:09:44 and 1:09:45. So whose run is really better? The loads they had in the run may have been for example 1 minute and 30 seconds. Just something I can imagine for a run of this length. So depending on their hardware (and game randomly deciding to get stuck in loads), the difference between these runners can be even tens of seconds. And what if we imagine this scenario: One person decides: "Oh, I'd really like an experience shrine there", they get it on the second try, get a level faster and save 20 seconds over someone who was in the same situation, but didn't choose to try the shrine. But the game decided to get stuck on both of the loads, so what's the issue here? The player, who made the superior decision might get worse time because the game decided to.

You might argue that "it's just RNG", but this is the kind of RNG that shouldn't be a part of the run.

And as for the only appropriate and enjoyable way of speedrunning the game. Sure, you might have your unique view on this, but I might tell you that this is not what all people will agree on with you. There's many games where IGT allows for more creativity and overall more sensible gameplay. Such as Fallout 4 (https://youtu.be/53ShoXezSzM?t=634 - Here's a clip of one player stacking an item on themselves to achieve more speed, this was btw. run on the last GDQ and I'd say it's one of the most loved runs there and I haven't seen a single complaint about them being in a load screen for a relatively long amount of time)

DrClicheDrCliche and BokserKabatyBokserKabaty like this. 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@Bender_Bender_ Actually, there are games that require sound to play and it's very reasonable. It makes splicing runs much harder. Especially in a game such as Diablo 2, where splicing is super easy, it wouldn't be so unreasonable to require sound.

@RyuQuezacotlRyuQuezacotl I personally don't like pausing the game for breaks. Surely, if the game is extremely long, then it's reasonable to include some time you can spend afk. But in general, the only reason why games remove the time when the game is closed is because of a crash.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@MrLlamaSCMrLlamaSC If LiveSplit crashes, I think it should be possible for you to start it again and press your start run key again. It would still remove the times, so you'd only have to append the time it took you to start LiveSplit again. That's how most of the games with IGT LiveSplit solve this problem.

And as you mentioned, it solves TCP/IP loading but it also does solve loading differences between different hardware setups.

And I can absolutely agree, refreshing the leaderboards would suck. Retiming the runs semi-automatically might however be possible.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@327327 You might be right, I'm definitely willing to expand on the script's functionality if it's possible of course. The question is, how much time over a run do these things take, because some times might be negligible. But again, I'm willing to do changes if something is considered unfair.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

Addition to my last post: Actually did it, my script removes the loading and saving times, but not the menuing required to continue playing. Is there anyone who'd be willing to test this? Just message me on Discord if you can (Wafu#7264)

Edit:
Got input from Indrek and blazer-flamewing, seemed to be sufficient enough. So if there's interest, I'll polish it so that it works with commonly used versions and I could push it directly to LiveSplit so that it requires just a one-click setup.

WraithulekWraithulek, HCGilboaHCGilboa and 2 others like this. 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@Teo-Teo- Yeah, that's why I was saying the only thing people would need is LiveSplit. I already found a way to remove the loading screen loads, but the issue is that clicking the "Save and exit" is inconsistent between -ns and no -ns, so I'd have to figure that out.

Edit: Another question is: Is the menuing part of the run? I assume you'd count that in, right?

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

@LaVLaV Yeah sure, but again, most people who speedrun regularly use LiveSplit. And from my experience, if a run had fairness issues due to inconsistent loads, the only option was to remove those loads unless it's a console run. That's just the truth of it.

I understand you might have an idea of speedrunning requiring as little tools as possible and there's nothing wrong about that. But sometimes, you gotta live with the fact that even though D2 is an old game, RTA simply won't be fair for everyone.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

Regarding the preparation, I think almost everyone, if not everyone uses LiveSplit. So the preparation needed for switching from RTA to IGT would be like a couple of clicks, I don't think that preparation is much of an argument here.

 

Forum: Diablo II: Lord of Destruction

Thread: We need to address -ns

Started by: IndrekIndrek

A similar thing is in The Elder Scrolls: Arena, where the game just overall runs faster with sound disabled. For me personally, I'd like to see it allowed, although yeah, it's weird to have soundless runs (and it makes splicing a bit easier)

But there's one thing I'm gonna ask, why time by RTA if the loads clearly are inconsistent? It's also not a thing that takes long time to implement.

 

Forum: Diablo II: Lord of Destruction

Thread: Scripts

Started by: 327327

Nobody breaks basic rules. It's just you who doesn't understand the rules and accuses other of breaking them.

As Teo said, some people can't play the game without glide wrapper - that is an external tool and it's not even worthy questioning whether it's allowed or not. This macro that Indrek uses is: 1. Not a modification of the game, 2. Isn't even used during the speedrun. It's so obvious that this should be allowed that there's no point in making a rule about it. And if you want to pointlessly nitpick about equal conditions, there's couple of hints: Operating system is an external tool that controls the game, we don't all have the same version of the OS, we don't all have the same CPU, GPU, HDD/SSD, Memory etc. Yet it's never discussed or even mentioned - because it doesn't matter for the run.