Ludicolo / Tropius are mandatory I guess for HM !
Ludicolo is exclusive to AS, not ORLudicolo / Tropius are mandatory I guess for HM !
I’m about to start a grass-only run of Omega Ruby. Are there any grass types that people still have questions on? Otherwise, I’ll just stick to whatever catches my eye.
HM Slaves maybeSo how you will handle Surf on OR ? :(
I’m fine with HM slaves. I’d have prefered to use Ludicolo, but a Grass-only run of Sapphire would feel incredibly cheap, so HM slaves have to be allowed.So how you will handle Surf on OR ? :(
Also, wow Seedot sucks early game. No offensive moves until 14 is really painful.
The initial babying period isn't quite as bad, true, but it still hits a lull period before evolving into Gardevoir. (going off my very fuzzy memory) Still, its best STAB moves are available as soon as it evolves, with Psychic coming at level 30 and Moonblast being a heart scale away.Bump but figure it's worth something.
There has been extensive discussion and agreeing back in the original tier list of Ruby/Sapphire/Emerald of Ralts moving to S tier. I think Ralts has a really strong case for S tier, given that the babying period for it has been overblown and Kirlia is by no means a dead weight Pokemon. But I'd imagine in ORAS, Ralts is even better because it has access to disarming voice at level 11 (and it bypasses accuracy checks so sand attack and double team is a lot more manageable), as well as losing its dark weakness (thus alleviating some of the Poochynea spam early game). Having an early access fairy type is very useful for team building too, as it'll help against the future dragon users massively
I once did a playthrough a few years ago with Exp. Share on and only fighting mandatory trainers (and the odd optional). When I got to the Pokémon League, I was very underlevelled with a team of 5/6 (like Lv40-42 low) and needed to grind to a more sane level to take on the league. Considering this, I don't see turning on Exp. Share to have any significant downsides from an objectivity standpoint (I would want to see what fighting more optionals would do for this, particularly in the lategame where there are so many optionals).
As for Shift/Set, it does not really matter. From a pure time perspective (e.g. speedruns) you want to do Set to avoid all the "X is about to use Y" textboxes, but from a turn perspective, Shift is better for instantly switching when needed. But in general, Shift vs. Set does not really matter as most entries for these things tend to look at the Pokémon in a vacuum of sorts (How does it individually handle a team or a specific Pokémon?).