Can someone tell me why the runs "Any% (Glitchess, HC)" says no glitchess are permited but ppl are doing that? I saw Krzysiek using Mana Shield and hiting hiself with firewall at caves... The demons seems to had they hit power much lowerd at all.

Is there another legit mode besides "Any% (Glitchess)" here?

Thanks.

As I understand it, the low hp + mana shield trick is more of an exploit than a glitch.

It doesnt reduce the power of enemy hits it just prevents you from being able to be stunlocked. You still take the full amount of damage that the enemy deals if they hit you.

For comparison, duping any items is not allowed in the run which is a straight up glitch.

It would be nice if the rules were better written to specify these things but it seems like the moderators haven't been active in a while.

That feels like just an emotional categorization. Low HP + mana exploits a glitch where the game thinks you are dead for less then a frame and there for does not apply stun to you, then the mana shield refunds you the HP and revives you before the frame ends.

Duping exploits a glitch where the game uses the same buffer for memorizing items being transferred from one location to the next and there are two items being transferred during the same frame, resulting in one item overwriting the other one.

From a technical perspective it's hard to see how there is any meaning full difference between the two. Both involve multiple things happening during a single frame then the developers had originally considered.

If they have to be categorized it's probably better to do so in terms of how much they spoil the fun of watching the run, or maybe how much it spoils the fun of competing.

To be honest if you want to play Glitchless you should be aiming towards DevX. It is non possible to play the game and not accidently double-cast or something like that :D

@AJenbo You're absolutely right. It is an "emotional categorization".

Frankly, the category shouldn't be called "Glitchless" .. The run is pretty well defined as what it is, and doesnt need any rules changed. If you understand how it plays its a solid run and it makes sense. The idea was obviously to remove duping so that the run doesn't devolve into "Dupe gold" -> "Roll Adria for god gear" -> "Go".

Removing Duping, but allowing "any other glitch" makes the run play out far more interestingly, requiring you to PLAY the game and deal with the RNG as it comes to you, as opposed to forcing your way in with Duping.

I still have no idea why this community is so stuck in the old days of thinking everything is either "Glitchless" or "any%". Literally every other community has adapted to modern naming schemes such as "No Major Glitches" ... or in this case probably just "No Dupe" would suffice.

My understanding (someone can correct me if I'm wrong) is that the name "Glitchless" is an homage to Super Metroid. On the deertier website, SM has categories for Major Glitches and No Major Glitches, but there is an "Any%" under both of these categories.

I agree the category shouldn't be called "Glitchless," if for no other reason than the fact that no where is it stated what is considered a glitch or an exploit. It's like going into a stream that just says "Follow the rules" while never telling you what said rules are, so how do you know you broke one until you get banned for it? It should not fall to the runner to have to ask around in order to figure out what those rules are. They should be clearly defined somewhere, and updated as questions and needed clarification arise. Furthermore, majority of the Diablo community accepts low-hp-MS as being a glitch, and many even consider it to be a major glitch right after duping.

There are so few runners for this game, I don't see anything ever changing, and I think that's probably the main reason for it. Just look at the discussion attempt over "free casting." It basically went nowhere because there was hardly any input. And honestly, I didn't expect it would go anywhere.

I agree with a state that definition of "glitch" — is a something that dramatically changes the gameplay. Like this: "Dupe gold -> Roll Adria -> Go". Other things like free casting, double casting as for me are not considered as glitch, because they are very situational.

My teammate asked me recently why low-hp-MS is not considered a glitch, because you can just run through monsters and do not fight, and skip large part of the game. So I even vote for dividing categories to: Any%, No Dupe (allowing low-hp-MS) and Glitchless (a run which allow to use bugs like spell queue and disallow to use low-hp-MS).

Also I have no idea why people play (preferably) HC runs, since it's a speedrunning and save/load is a thing that can decrease your time.

To be honest killing Diablo with Fire Wall also makes game boring, because no matter what class do you play, you are looking for FW and use it in final fight. So "No Fire Wall" category is also have a right to exist :)

So let's decide what to do and I will create categories and rules for all your preferences.

Yep, probably it would be better to separate runs allowing low-hp-MS and not. Because its very ridiculous when rogue or warrior uses low-hp-MS feature with fire wall, but for mage its ok.

Low-HP-MS is not a glitch.

This statement has been provided by Funk, who referred to the conversation he had with David Brevik himself.

Category name discussions were heated back in the day. Glitch/exploit/rules discussions were heated back in the day. Some of the discussions related to:

• name of the category: Glitchless vs Legit% vs No Dupe No Load (was there "Dupeless" too?)
• allowance of death before Diablo died
• low-HP
• 4-tile, horizontal walk, elemental bow, firewall
• spell buffering
• v1.09 Diablo version

Recently we're having discussions related to:

• name of the category
• free casting
• low-HP
• overpowered spells
• playing game modifications

We all have our perspectives.

Speedrunning Diablo is genuinely fun. To keep it fun, we strip ourselves of overpowered exploits. We also choose HC over SC to give additional thrill. Classic speedrunners of course stick with Any%.