>>56415024>You know what's more awkward? Pokemon not even existing in the overworld.It's worked for fucking decades in every other JRPG since DQ1, abstraction has always been important when dealing with limited hardware. And the DS is probably the last console that it was really difficult to implement stuff like that, as DQ9 showed it was possible if not perfect. You could do it on the 3DS much easier, if you want to blame a game for being lazy I'd blame XY more than BW (but XY made more work for itself with the awful overworld art style).
>No you haven't.Okay, list a couple other games, and we'll see if they meet the qualification of making Pokemon easy to catch in a short amount of time. Especially since there's so many monster collecting games, which only started to drop off after the DS. Got any examples from the Digimon Story games on the DS? I haven't played those yet, if you must know.
>It is laziness when the "design decision" is objectively worse and only exists because it's easier to implement.So the EXP All thing in modern games, Switch being campaign only and Set being multiplayer only, the general removal of player options, the future proofed 3D models being tri'd way too high poly from the base quad models making the 3DS lag extremely easily, not scaling lower level Pokemon up for the Battle Maison/Tree, copy-pasting dialogue from the Battle Subway, not fixing the AI so it doesn't get fucked by certain strategies, and a bunch of other things I don't want to list. Compared to the thing that if implemented could consistently inconvenience the player or make the base performance of the game worse if implemented poorly. I see you have your priorities in order.
>Then make a game without the problem.You know, that's a brilliant idea. I say give it a shot, you seem to understand the requirements here. Whip up something in RPG Maker or Unity or something, I genuinely want a good solution. Once that's prototyped we can try implementing it on the DS after.
