Bot AI

To add server-side bots to fill empty seats, you initialize a BotManager module to handle the bot lifecycle, spawn bots with generated IDs, and dispatch their decisions through the same socket event flow as human players. This ensures table balance and deterministic behavior.

Multiplayer bots make game-specific decisions by routing logic to defined decision functions for games like Hearts, King, Spades, and Okey101. The system applies a consistent 1000ms action delay before executing the chosen move to simulate human timing and ensure safe interactions.

Yes, you can use server-side game bots with existing socket event handlers. The bot system uses the exact same socket event flow as human players, ensuring parity and safe interactions without requiring separate networking logic or specialized bot protocols.

The bot naming system uses a Turkish name pool to assign identities to bots, falling back to a Bot-{random} pattern if names are exhausted. It also generates specific ID patterns, allowing the game server to easily detect and manage bot players separately from human users.

The best way to manage AI bot lifecycles is using a dedicated BotManager module to add, remove, and regenerate bot IDs as needed. This approach maintains table balance and ensures deterministic behavior throughout the duration of the game play.

Yes, you need to define custom decision functions for each card game. The Bot AI system dispatches actions to specific decision logic for Hearts, King, Spades, and Okey101, requiring these functions to be defined to ensure proper and deterministic bot behavior.