>>40615331Actually, that's exactly what I expected. Gamefreak nurtured the expectation of previous Pokemon carrying over, generation after generation for a whole two decades. Having all Pokemon in the game's data was the BARE MINIMUM for this franchise, and Gamefreak can't even deliver on that anymore. We have every right to be angry over two decades worth of expectations being betrayed. And it's such a needless cut at that.
>muh armchair game development!Oh fuck off, doesn't take a game developer to see how many animations and meshes are straight up reused from the 3DS. It doesn't take a game developer to know you can port over assets with relative ease, modders do it all the time for other games. Gamefreak has done it even before gen VI, and many other developers have lazily copypasted old assets into new games with no trouble whatsoever. Don't pretend there would be unforeseen consequences of putting an asset into a new engine, don't pretend it'd be too much trouble. If even a tiny, shitty, horribly incompetent fuck of a developer like Compile Heart can use the same fucking assets between drastically different engines, you can't tell me Gamefreak can't port ALL the old Pokemon over with no trouble, unless they're legitimately worse than Compile Heart. Worse than an ACTUAL FUCKING KUSOGE DEVELOPER.
>>40615723Here's more "armchair game development" for you, but the higher res textures will still take up more. Also the dynamax likely all being unique models. Don't try to pretend they aren't, between Gigantomaxing incorporating the clouds into their designs and GF's history with copied assets within code, we can assume dynamaxing is taking up a good chunk of space.
But you'll probably deny it, right? We'll just wait a few days for the game to leak, then the dataminers can get right into it to confirm and the shitposters will be sure to rub it in for me. Go fuck yourself.
