Yet Another Stupid Death - Revision history

Hordes: /* Adjust Your Threat Assessment */

2026-01-21T20:50:32Z

‎Adjust Your Threat Assessment

Hordes at 02:18, 22 March 2025

2025-03-22T02:18:13Z

Hordes: /* Adjust Your Threat Assessment */

2025-03-21T21:58:01Z

‎Adjust Your Threat Assessment

Hordes: /* Preventing Hubris */

2025-03-21T21:55:36Z

‎Preventing Hubris

Hordes: /* Adjust Your Threat Assessment */

2024-06-02T21:12:37Z

‎Adjust Your Threat Assessment

Hordes: /* Preventing Hubris */

2024-06-02T21:08:00Z

‎Preventing Hubris

Patrick2011b: /* Adjust Your Threat Assessment */ fix

2024-05-31T21:53:49Z

‎Adjust Your Threat Assessment: fix

Hordes: /* Play Less Quickly */

2024-01-15T12:43:32Z

‎Play Less Quickly

Hordes: /* Preventing Hubris */

2023-12-01T19:15:51Z

‎Preventing Hubris

Hordes: /* Preventing Hubris */

2023-12-01T09:34:21Z

‎Preventing Hubris

@@ Line 19: / Line 19: @@
 One way experienced players avoid YASD is experience - more specifically, the experience in knowing what is and what isn't a threat. A player might autoexplore, find a D:4 [[ogre (monster)|ogre]], and think "D:4 ogre? That's too risky to allow into melee range - it can do 37-39 damage per turn, enough to kill me in two hits". By constantly iterating this kind of thought process over time, one can play fast ''and'' consistently.
-Like before, if you play 1000 games and don't learn anything from them, being "experienced" won't be of much help.
+Like before, it is best to learn and play with a purpose in mind. If you play 1000 games and don't learn anything from them, being "experienced" won't be of much help.
 *One way to help is to look back at your deaths. If you play online, you might be able to download "ttyrecs" and play them with [https://github.com/Rytisgit/DCSSReplay external software]. It is recommended to go turn-by-turn: try to find the moment where you go from "you can escape with 0% chance of death (even if you need items to do so)", to "you have a chance of dying, no matter what". Then, go back and see what you could've done a turn before to prevent it, 5 turns before to prevent it, etc.
 *Then, apply what you learned. This sounds simple - because it is - but this step is important to A. make sure your theory works in practice, and B. reinforce good habits. You may think of an idea after a post-YASD analysis, then that idea doesn't hold up in actual gameplay.
-*Also, look for advice, whether on the wiki or from other players. They can provide a shortcut towards experience, e.g. give tips on what is a threat.
+*Also, look for advice, whether on the wiki or from other players. They can provide valuable tips, correct misguided info, etc.
 ==External Links==

@@ Line 21: / Line 21: @@
 Like before, if you play 1000 games and don't learn anything from them, being "experienced" won't be of much help.
 *One way to help is to look back at your deaths. If you play online, you might be able to download "ttyrecs" and play them with [https://github.com/Rytisgit/DCSSReplay external software]. It is recommended to go turn-by-turn: try to find the moment where you go from "you can escape with 0% chance of death (even if you need items to do so)", to "you have a chance of dying, no matter what". Then, go back and see what you could've done a turn before to prevent it, 5 turns before to prevent it, etc.
-*Then, apply what you learned. This sounds simple - because it is - but this step is important to A. make sure your theory works in practice, and B. reenforce good habits. You may think of an idea after a post-YASD analysis, then that idea doesn't hold up in actual gameplay.
+*Then, apply what you learned. This sounds simple - because it is - but this step is important to A. make sure your theory works in practice, and B. reinforce good habits. You may think of an idea after a post-YASD analysis, then that idea doesn't hold up in actual gameplay.
 *Also, look for advice, whether on the wiki or from other players. They can provide a shortcut towards experience, e.g. give tips on what is a threat.

@@ Line 21: / Line 21: @@
 Like before, if you play 1000 games and don't learn anything from them, being "experienced" won't be of much help.
 *One way to help is to look back at your deaths. If you play online, you might be able to download "ttyrecs" and play them with [https://github.com/Rytisgit/DCSSReplay external software]. It is recommended to go turn-by-turn: try to find the moment where you go from "you can escape with 0% chance of death (even if you need items to do so)", to "you have a chance of dying, no matter what". Then, go back and see what you could've done a turn before to prevent it, 5 turns before to prevent it, etc.
-*Then, apply what you learned. Sounds simple, since it is. But make sure your theory applies in practice. You may think of an idea after a post-YASD analysis, then that idea doesn't hold up in actual gameplay.
+*Then, apply what you learned. This sounds simple - because it is - but this step is important to A. make sure your theory works in practice, and B. reenforce good habits. You may think of an idea after a post-YASD analysis, then that idea doesn't hold up in actual gameplay.
 *Also, look for advice, whether on the wiki or from other players. They can provide a shortcut towards experience, e.g. give tips on what is a threat.

@@ Line 5: / Line 5: @@
 ==Preventing Hubris==
 {{Advice}}
-Due to ''Crawl'''s gameplay loop, it's easy to experience hubris. By the mid-game, you will constantly encounter, and subsequently mow down, enemies who are trivial to fight. This encourages you to play fast, this makes players feel strong. And for a while, mindlessly [[autoexplore|autoexploring]] and [[tab|autofighting]] ''does'' work. But it's only a matter of time before bad RNG kicks in, or you see a monster that's too difficult. If (and only if) you continue to fight recklessly, you will die.
+Due to ''Crawl'''s gameplay loop, it's easy to experience hubris. By the mid-game, you will constantly encounter, and subsequently mow down, enemies who are trivial to fight. This encourages you to play fast, this makes players feel strong. And for a while, mindlessly [[autoexplore|autoexploring]] and [[tab|autofighting]] ''will'' work. But it's only a matter of time before bad RNG kicks in, or you see a monster that's too difficult. If (and only if) you continue to fight recklessly, you will die.
 ===Play Less Quickly===
-A common advice is to "play slower". This can work - and often does - but not without caveats. If you play slower without knowing ''why'' you are playing slower, you've done nothing productive. Also, playing slower can make you impatient down the line, causing the opposite effect.
+A common piece of advice is to "play slower". This can work - and often does - but not without caveats. If you play slower without knowing ''why'' you are playing slower, you've done nothing productive. Also, playing slower can make you impatient down the line, causing the opposite effect.
 If you do decide to engage in slow play, it should be methodical. You should be thinking about (at least) two things:

@@ Line 20: / Line 20: @@
 Like before, if you play 1000 games and don't learn anything from them, being "experienced" won't be of much help.
-*One way to help is to look back at your deaths. If you play online, you might be able to download "ttyrecs" and play them with [https://github.com/Rytisgit/DCSSReplay external software]. It is recommended to go turn-by-turn: try to find the moment where you go from "you can always escape (even if you need items)", to "you have a chance of dying, no matter what". Then, go back and see what you could've done a turn before to prevent it, 5 turns before to prevent it, etc.
+*One way to help is to look back at your deaths. If you play online, you might be able to download "ttyrecs" and play them with [https://github.com/Rytisgit/DCSSReplay external software]. It is recommended to go turn-by-turn: try to find the moment where you go from "you can escape with 0% chance of death (even if you need items to do so)", to "you have a chance of dying, no matter what". Then, go back and see what you could've done a turn before to prevent it, 5 turns before to prevent it, etc.
 *Then, apply what you learned. Sounds simple, since it is. But make sure your theory applies in practice. You may think of an idea after a post-YASD analysis, then that idea doesn't hold up in actual gameplay.
 *Also, look for advice, whether on the wiki or from other players. They can provide a shortcut towards experience, e.g. give tips on what is a threat.

@@ Line 17: / Line 17: @@
 ===Adjust Your Threat Assessment===
-One way experienced players avoid YASD... is experience. More specifically, the experience in "knowing what is and what isn't a threat". A player might autoexplore, find a D:4 [[ogre (monster)|ogre]], and think "D:4 ogre? That's too risky to allow into melee range - it can do 37-39 damage per turn, enough to kill me in two hits". By constantly iterating this kind of thought process over time, one can play fast ''and'' consistently.
+One way experienced players avoid YASD is experience - more specifically, the experience in knowing what is and what isn't a threat. A player might autoexplore, find a D:4 [[ogre (monster)|ogre]], and think "D:4 ogre? That's too risky to allow into melee range - it can do 37-39 damage per turn, enough to kill me in two hits". By constantly iterating this kind of thought process over time, one can play fast ''and'' consistently.
 Like before, if you play 1000 games and don't learn anything from them, being "experienced" won't be of much help.

@@ Line 14: / Line 14: @@
 # What options do you have? If you spot trouble early, you may want an effective-but-cheap option. If you're at 1 HP, you probably want to use a [[scroll of blinking]].
-Also, you may want to adjust your [[rcfile]]. If you make autofight slower, you may catch mistakes you otherwise would've missed. There are two options of note: <code>autofight_stop = X</code>, which is the % HP where autofight cannot be used, and <code>autofight_warning = X</code>, a delay (in milliseconds) between autofight commands.
+In addition you may want to adjust your [[rcfile]]. If you make autofight slower, you may catch mistakes you otherwise would've missed. There are two options of note: <code>autofight_stop = X</code>, which is the % HP where autofight cannot be used, and <code>autofight_warning = X</code>, a delay (in milliseconds) between autofight commands.
 ===Adjust Your Threat Assessment===

@@ Line 11: / Line 11: @@
 If you do decide to engage in slow play, it should be methodical. You should be thinking about (at least) two things:
-# What can monsters do to you 1 turn, or 2 turns, from now? Can they kill you if they do maximum damage? Think about effects that change your position, any [[status effect]]s monsters can inflict on you, as well as the max damage you can take. ('''N.B.''' In the late-game: when fighting many monsters, especially with high [[AC]], the chance of taking max damage is incredibly small. The chance of taking max damage twice, even less likely. Thus you may find it acceptable to continue fighting even in "potential one-turn death range".)
+# What can monsters do to you 1 turn, or 2 turns, from now? Can they kill you if they do maximum damage? Also, think about effects that change your position, and any [[status effect]]s monsters can inflict on you.<br>('''N.B.''' In the late-game: when fighting many monsters, especially with high [[AC]], the chance of taking max damage is incredibly small. The chance of taking max damage twice, even less likely. Thus you may find it acceptable to continue fighting even in "potential one-turn death range".)
 # What options do you have? If you spot trouble early, you may want an effective-but-cheap option. If you're at 1 HP, you probably want to use a [[scroll of blinking]].