showed a problem in DP006's battle with Paul and solved it by the Roark rematch. Same with Aipom
participating in its first contest (and a second unofficial contest not far behind), building up its love for contests.
All of this = developpement. Had the writers done some of that with the first 6 pokémon (like having Snivy distrusting Ash's orders, Tepig freezing up during a battle cause he's afraid of being released, etc.), I might consider giving them the benefit of the doubt with more. They didn't.
Do we really need to count Aipom? Because by the end of the day, that development for Aipom was setting it up for Dawn, not for Ash's benefit. Also, it's gone now so it's not like it mattered for Ash in the long run.
So then Ash having two pokemon learn new moves at the same time is not development? Nor is Ash beating his rival's evolved starter with a freshly caught pokemon (who was then said to be strong by said rival)? And of course, Ash completes his team now instead of later so doesn't that compensate things?
Also, by this time, Turtwig only appeared 9 times and was caught 2 episodes before Snivy's episode number. And do you really expect Snivy distrusting Ash after it got caught? That doesn't make sense. I thought it had its moments thinking that Ash is a worthy trainer throughout its capture episode? Then all of a sudden you want it to distrust Ash? You know, that can totally happen later down the road instead of showing up that early (besides we already have Iris
to worry about distrusting orders). And then of course Tepig learned a new move and starred in a gym so I don't know what else you want for it. Especially since it almost matches up to Oshawott's screentime.
It's storyline was done. It was a crybaby afraid to fly, by the McCann episode, it wasn't. He didn't have anything really left to prove battle wise, no rivalry with Paul's pokémon to tie up and the writers proved me right on that as Gliscor
really didn't gain anything by coming back and actually cost Ash's Torterra
a win, leaving its rivalry with Paul's Honchcrow unfinished.
Well Ash could've always taught Gliscor Stone Edge and perfect its Giga Impact. That was development that could've been seen even if its storyline was done. Ash could've perfect its flying on-screen instead of off-screen. Also development. And if it didn't leave, you wouldn't even call it cheap nor say it cost Torterra's win so it'd probably could've been best if it stayed (even though I liked Gible
Writers are concentrating on grass and bug moves for Sewaddle, they aren't going to totally overhaul its movepool with unusual moves for the hell of it. So far, they are giving Sewaddle Bug and grass moves according to its typing. Both those can be provided by other members of Ash's team.
Yet you're saying Oshawott should learn 3 bug moves? Fine, if you want bug and grass moves, here: Bug Buzz, Struggle Bug, Bug Bite, Energy Ball, and Grasswhistle. That's 5 moves (4 moves it doesn't know now) and we know the writers try to stick with 4 nowadays. And it has to have at least one non-bug or grass move so why not insert Shadow Claw or Poison Jab?
And one bug move is all you need really. Why limit Oshawott's movepool when it can learn bug moves naturally? It'd make it an asset against grass type pokémon and (with Fury Cutter or X-Scissor) gowith the whole Samurai thing, giving Oshawott's line a unique battle style.
Um, again, why the bug moves for Oshawott? I feel like you're grasping at straws to make Sewaddle look bad. If you said the writers are concentrating same typed moves for Sewaddle then surely Oshawott is the same story. So we got Shell Blade, Aqua Jet, Slash, Revenge, Water Pulse, Aqua Tail, Vengeance, Swords Dance, Hydro Pump, Hydro Cannon, Ice Beam, Megahorn, Dragon Tail, and Night Slash. It's covered with other attacks besides the bug ones you listed. If you want Oshawott to be like a samurai, give it Night Slash, Vengeance, and/or Revenge.
But it may be and look, Sewaddle is already robbing Pidove of screentime...
You do know neither Sewaddle or Pidove are seen after Sewaddle's capture. Sewaddle is not robbing anyone. And like I said, Pidove (nor Sewaddle) would need a whole lot of screentime.
As I said, I don't mind releases (or oaking though I prefer releases in the case I'm describing) to make room for a new pokémon if
the released pokémon's done developpement wise. Why? Because its return eats the screen time of other pokémon that need it more.
I mind oaking to make room for a new pokémon if
the oaked pokémon isn't don developpement wise. Why? Because its capture eats the screen time of other pokémon that need it more.
Well there are people that actually like Leavanny
and would want to see it again in battles. And I always like the possibility of seeing a pokemon again, no matter who they are. Hence why I don't like releases because we're never gonna see Butterfree
battle alongside Ash. The past releases are like a distant memory and so I would not want that to happen to our current pokemon.
Then why not release Leavanny instead of letting it eat other pokémon's screentime, pokémon who still need developpement. Your argument is that it brings less, then why have it in the first place?
Didn't you read the fact that May and Dawn got their couple of episodes by this time already and still got more? Considering Iris and Cilan don't get as much focus as Ash already, that means that there should be time for Ash to develop his team. It's all about balance. Leavanny can be focused now and get some battles here or there in the future, but then maybe an arc could be devoted to Snivy, then Tepig, then Oshawott evolves, then Scraggy vs. Axew
And it doesn't have a whole lot going for it after it evolves but its purpose for its capture can be to aid Ash in the league/vs. TP. It's to give Ash another pokemon besides his 6 because people do complain about stagnant teams. And since people don't want to see the same old 6 pokemon in the Unova League, we got a solution already. And again, once it's more or less at a good place, it's obviously on to the next pokemon for their chances to shine. My gym screentime chart sorta shows the direction where screentime can head to and it all seems pretty decent.