I see the problem. The state route is trying to fetch from the parent route using an internal fetch with an incorrect URL construction. The issue is that internal API calls within the same server should not use fetch() - they should directly access the data. Let me fix the state route to export the game state data directly instead of trying to fetch it:

The issue is that the state route is trying to fetch internally which is causing SSL errors. The simplest fix is to replace the state route with a direct implementation that mimics what the game route returns. Let me rewrite the state route to be independent:

Actually, the real issue is that the Game component is polling the state route, but the state route can't communicate back with the main game route properly. The better solution is to refactor so the Game component polls the main /api/game route directly instead of using the state route. Let me update the Game component:

Now I can delete the problematic state route file since it's no longer needed:

I've fixed the SSL error by removing the problematic state route that was trying to internally fetch from the game route, which caused SSL packet length errors. The Game component now polls directly from /api/game for state updates, which is simpler and avoids the internal fetch issue. The game should now work correctly for all modes including AI vs AI.

I'll add a feature to let the AI play as the second player in multiplayer mode, so players don't have to wait for another human. Let me first check the current Lobby and Game logic:

I'll add a "Create Game with AI" option for multiplayer mode. Let me update the Lobby to add this feature:

Now let me update the page.tsx to handle the aiSecondPlayer flag:

Now let me update the Game component to pass this flag to the API:

Now let me update the API route to handle the aiSecondPlayer mode:

Now let me find and update the GET handler:

Now let me find the game start logic and add aiSecondPlayer handling:

Now let me update the game loop to handle AI second player as well:

I've successfully added the AI second player feature to the multiplayer mode. Here's what I implemented:

AI Second Player Feature:

• Added a new "Create Game (vs AI)" button in the multiplayer mode that lets the human player battle an AI opponent instead of waiting for another human player
• The AI automatically joins as player 2 when the game starts, immediately beginning the battle
• The AI uses the same intelligent behavior as other AI opponents - tracking the player, aiming, and shooting strategically
• Players can still choose to create a regular multiplayer game and wait for another human player if preferred

The implementation flows through the Lobby → page.tsx → Game component → API route, with the aiSecondPlayer flag controlling whether AI fills the second player slot. This gives players flexible multiplayer options without needing to wait for others to join.