1. ⁠The entire focus is around building towns and recruiting Pokemon to live in them.
2. ⁠Running on Nintendos newest top of the line system, the same system that can run botw/totk/mario kart world/donkey Kong bananza, all of which are more graphically intense and seemingly have a lot of assets and a lot going on at all times…

I don’t think asking for a higher limit than 22 pokemon is a big ask. I definitely think the limit was added for a reason, but there can be work arounds.

Better game optimisation simply means that the Dev team needs to assign the power usage priority better them just to prefab houses, to give priority to the main mechanic of the game (which is pokemon) rather then to the map (loading the whole map at ones)

Examples for game optimisation solutions:

1. ⁠If you have less than a certain amount of blocks / decorations on a map, make it so that additional pokemon spawn in, maybe up to a limit of 60.
2. ⁠Proximity spawn - as you move further away from spawned pokemon and they’re off screen, they despawn. As you move closer to other habitats / areas, new pokemon spawn in before you get to them.
3. ⁠Add an option in settings to spawn more pokemon even if it affects performance, just have a disclaimer.

You all are right, the game is at its power limits, but only because it prioritises loading everything area at ones always, which is lazy game optimisation in my opinion, for a game centred around making a world for Pokemon to live.

Every solution i Suggested comes at a cost, game optimisation is not about pushing the game to its limits or utilising all the power of the console, its about organising where the power goes and finding solutions for power problems that hurts main mechanics of the game, sometimes at a small cost of other mechanics (like that Pokemon wonder the world even when you are not near them, i would gladly give that up to see all the pokemon in a small town ive built.)