Note to self: do NOT ever blind-run a hack where you know the level curve makes sudden jumps.

May 15, 2014 00:17

Or where you know the hack has a really bullshit move combo on the later Pokemon of a Gym Leader.
(Two Full Restores per Pokemon from second Leader on was REALLY fucking cheesy, though. I was NOT forewarned about that.)

It was fine. I'd figured out how to break (most of) the hack's level curve anyway, so I really only ran into trouble because I screwed around rather than just hyper-leveling boosted!Raticate. I... really did it just because I was goofing off, anyway.

Eh, now I can do Alt Evos with a clean conscience. :P At least that hack creator told players what the level curve was there. (No &!@(ing idiocy like L38 Pokemon at Lt. Surge...)

I just wanted to retry Unprejudiced Red (in a marathon session) after my first failed run. I didn't fail this run, but I kind of got tired of it. (The strategy became too simplistic with all the overly-good Pokemon, much to my surprise. Sleep + Leech + win. Sleep + Tail Glow + win. &c &c &c)

Plus, I guess I'm really not good at blindly running hacks. Grinding doth bore me. :P

However, I've got to organize the plot of the Alt Evos run before actually playing it. While working. And... bleh. :P Well, welcome to the summer...

This entry is mirrored at http://guardians-song.dreamwidth.org/235561.html. Comment wherever you like. Just remind me to get off the internet and do my homework.

pokemon: hacks, challenge: nuzlocke, fandom: pokemon

Previous post Next post
Up