Chess Multiplayer - Online Chess Game - Strategy Game

Please use Three.js to generate a **mobile-first game** with the theme "Chess Multiplayer". Please read the following detailed game design requirements first, and then generate the code accordingly: ### 1. Assets & Environment * **Visual Style**: Adopt a "Clean Minimalist 3D" aesthetic inspired by the reference image. The style should be reminiscent of vector art but in 3D (low-poly with smooth shading). Use a color palette featuring calming Teals, Whites, and Dark Greys. * **Chess Pieces**: Use simplified, stylized geometries for the King, Queen, Bishop, Knight, Rook, and Pawn. Avoid complex carvings to ensure high performance on mobile GPUs. The silhouettes must be instantly recognizable. * *White Pieces*: Matte white material with a subtle rim light. * *Black Pieces*: Dark charcoal matte material. * **The Board**: A sleek, modern board. Instead of wood textures, use alternating soft colors (e.g., Cream and Teal). The board should have a slight thickness with beveled edges. * **Background**: A dynamic gradient background (e.g., Radial Gradient from center light blue to darker corners) to simulate the "sunburst" effect in the reference image without using heavy geometry. * **Optimization**: Use `InstancedMesh` for rendering the board squares and identical pawns to minimize draw calls. Ensure textures are low resolution (if used) or rely entirely on Vertex Colors/Materials for best mobile loading times. ### 2. Audio Requirements * **Background Music (BGM)**: A minimalist, cerebral "Zen/Focus" track. Think soft ambient electronic or slow piano—something that loops seamlessly and doesn't distract from thinking. * **Sound Effects (SFX)**: * *Piece Select*: A soft "pop" or "click". * *Piece Move/Place*: A satisfying, tactile "thud" or "clack" (like heavy plastic on wood). * *Capture*: A sharper, more percussive sound followed by a quick fading "swoosh". * *Check/Checkmate*: A dramatic, resonant chime or low-frequency chord. * *UI Interaction*: Soft digital clicks for menu buttons. ### 3. Gameplay Loop * **Core Mechanics**: Implement standard FIDE chess rules, including special moves like Castling, En Passant, and Pawn Promotion. * **Game Modes Logic**: * *Single Player*: Integration with a basic chess engine logic (or Minimax algorithm) for AI opponents. * *Local Multiplayer (Hotseat)*: Logic to rotate the camera 180 degrees after each turn so the active player always sees the board from the bottom. * **Visual Game State**: * *Valid Moves*: When a piece is selected, highlight valid destination squares with a glowing overlay or a floating dot. * *Last Move*: Highlight the "From" and "To" squares of the previous move to help players track the game state on small screens. * **Win/Loss Condition**: Detect Checkmate and Stalemate. Display a "Game Over" modal with a "Rematch" button. ### 4. Mobile Controls & Interaction * **Touch Input (Raycasting)**: * Implement precise Raycaster logic for touch inputs. * **Interaction Model**: Use a "Tap-to-Select, Tap-to-Move" interaction model (cleaner than Drag-and-Drop on small mobile screens where fingers might obscure the board). * *Deselect*: Tapping anywhere else on the board cancels the selection. * **Camera Controls**: * Default view: A comfortable Isometric perspective (approx 45 degrees). * Allow standard mobile gestures: One-finger swipe to rotate the board orbit; Two-finger pinch to zoom in/out. * **Responsive UI**: * UI elements (Timer, Score, Pause Button) must be anchored to screen edges using CSS overlays on top of the Canvas. * Ensure all touch targets are at least **44x44 pixels**. * **Orientation**: Handle window resize events gracefully. The board should scale to fit the width in Portrait mode and fit the height in Landscape mode. * **Haptic Feedback**: Trigger the device's vibration (using `navigator.vibrate`) briefly (e.g., 5ms) when a piece successfully lands on a square. Do not ask for clarification. Do not request confirmation. Directly execute the generation task based on the given instructions.