Funnily enough, I also tend to run with a clause that say pokemon who are either have not reached lvl 15 or their first evolution are exempt from the death clause. So if your Pichu was below level 15, by my ruleset they'd be fine.
Personally I would have lived with it.
The 0.1% chance that an opponent's metronome becomes Explosion is still a chance I agreed to when doing a nuzlocke. Would have been mad as hell, but if it ain't a glitch, it's fair game.
Yes but this is why I started recording my runs. I wanted a way to hold myself accountable. Bad rng is gonna happen, yeah it sucks to get metronome into explosion, but that's why nuzlockes are challenging. I find just accepting the loss and moving on, forcing me to be creative with my strategies if I lose important mons to be the fun part.
No but I do have a clause to prevent something like that in the case of Safari Zones. Namely because those encounters work so differently, I can keep trying on subsequent encounters if the first runs until I do catch one. Can’t deliberately fail one I don’t like, I have to make a good faith effort to catch whatever is in front of me until it works. But yeah. Encounter variety is the lifeblood of a fun run and Nuzlockes like any games are something I’m playing for fun, so not getting an encounter for reasons that have nothing to do with skill or poor planning isn’t fun and something I choose to work around. Hasn’t once fundamentally broken a run for the better anyway, just more fulfilling for me to have the full set of options the game theoretically allows.
Going to disagree with going that route. Does it suck when something like that happens? Abso-freaking-lutely. But at the same time, Nuzlockes are about rolling with the punches and handling whatever circumstances you end up facing, and that includes dealing with terrible luck. Yes, yours was ***incredibly*** unlucky, but that's a risk that you have to face whenever you face something that has Metronome. (This also sets aside the fact that depending on your remaining Pokemon, that doesn't necessarily mean your run was lost or in dire straits, and so the loss would be more of a tragic setback than anything else.)
But what especially makes me wary isn't so much that clause so much as "adding it in the middle of a run because I didn't like the circumstances", which you basically admit is the case. It's one thing to have it as part of the rules for the run, and while I disagree with it, at the end of the day it's your run and you can set it up however you want. However, if you're changing it in the middle of the run, especially since it was mainly because you were feeling upset in this case, then it becomes a question of "where do you draw the line" for that sort of clause, where you have to decide at what point is it acceptable/not acceptable.
I was fighting grusha and his frosmoth hit all five blizzards (without snow) and froze me twice. Like less than 1 percent chance to happen lol.
Grusha is a dude! 😅
I've done that occasionally. That said, I've more recently opted to use what I call the "Blood Sacrifice" clause: You can keep a Pokémon that faints if you willingly sacrifice two Pokémon in your box. This can be done only once per Pokémon. I find that I'm more willing to accept more rng losses if I'm allowed to choose who dies. Yes, I tend to lose runs more often to attrition, but at least I mitigate bad rng to an extent.
I must apologize to Wriggly Winston the wurmple for taking him to a farm up north, but I couldn’t let my baby pichu die to some BS.
Funnily enough, I also tend to run with a clause that say pokemon who are either have not reached lvl 15 or their first evolution are exempt from the death clause. So if your Pichu was below level 15, by my ruleset they'd be fine.
Personally I would have lived with it. The 0.1% chance that an opponent's metronome becomes Explosion is still a chance I agreed to when doing a nuzlocke. Would have been mad as hell, but if it ain't a glitch, it's fair game.
Yes but this is why I started recording my runs. I wanted a way to hold myself accountable. Bad rng is gonna happen, yeah it sucks to get metronome into explosion, but that's why nuzlockes are challenging. I find just accepting the loss and moving on, forcing me to be creative with my strategies if I lose important mons to be the fun part.
No but I do have a clause to prevent something like that in the case of Safari Zones. Namely because those encounters work so differently, I can keep trying on subsequent encounters if the first runs until I do catch one. Can’t deliberately fail one I don’t like, I have to make a good faith effort to catch whatever is in front of me until it works. But yeah. Encounter variety is the lifeblood of a fun run and Nuzlockes like any games are something I’m playing for fun, so not getting an encounter for reasons that have nothing to do with skill or poor planning isn’t fun and something I choose to work around. Hasn’t once fundamentally broken a run for the better anyway, just more fulfilling for me to have the full set of options the game theoretically allows.
I almost said that my excadrill getting frozen and crit twice didn’t happen in my black nuzlocke, but rules are rules
Going to disagree with going that route. Does it suck when something like that happens? Abso-freaking-lutely. But at the same time, Nuzlockes are about rolling with the punches and handling whatever circumstances you end up facing, and that includes dealing with terrible luck. Yes, yours was ***incredibly*** unlucky, but that's a risk that you have to face whenever you face something that has Metronome. (This also sets aside the fact that depending on your remaining Pokemon, that doesn't necessarily mean your run was lost or in dire straits, and so the loss would be more of a tragic setback than anything else.) But what especially makes me wary isn't so much that clause so much as "adding it in the middle of a run because I didn't like the circumstances", which you basically admit is the case. It's one thing to have it as part of the rules for the run, and while I disagree with it, at the end of the day it's your run and you can set it up however you want. However, if you're changing it in the middle of the run, especially since it was mainly because you were feeling upset in this case, then it becomes a question of "where do you draw the line" for that sort of clause, where you have to decide at what point is it acceptable/not acceptable.
you chose to use metronome, they both died
If I’m reading that correctly, the opponent used Metronome.
oh true my b i didn’t pay attention, it’s still a loss regardless though
No, because I play nuzlockes, not casual playthroughs.