SQUEEK – COMPLETE GAME FIX & IMPROVEMENT

Please inspect and update the existing Squeek game project. Fix all three issues below in the current codebase.

Do not rebuild the game from scratch. Preserve the existing visual style, assets, maps, combat mechanics, gameplay features and Supabase integration.

1. CHANGE LIFETIME SCORE TO PERSONAL BEST

Current problem

Lifetime Score currently accumulates points from every completed run. This is not the intended behavior.

Required behavior

Lifetime Score must represent the player's highest single-run score, NOT the sum of all runs.

Example:

• Run 1: 5,000 points
• Run 2: 8,000 points
• Run 3: 6,000 points
• Lifetime Score = 8,000 points.

Requirements:

• Only update Lifetime Score when a player achieves a new personal best.
• Lower-scoring runs must never reduce the existing personal best.
• Preserve wallet identity and existing verified player records.
• Implement this logic authoritatively on the Supabase backend, not just in the frontend.
• Review and update relevant score settlement functions, database triggers, RPCs and leaderboard queries.
• Do not simply rename total_score or change the displayed value while leaving cumulative backend logic unchanged.
• If historical run data is available, calculate the correct personal best from existing records.
• Do not arbitrarily erase existing player data.

2. REDESIGN MOBILE LEFT-HAND MOVEMENT CONTROLS

Current problem

The existing mobile joystick is uncomfortable and difficult to control. The restrictive circular control area makes mobile gameplay frustrating.

Required behavior

Implement direct-touch movement on the LEFT HALF of the mobile screen.

• Players can touch anywhere on the left half of the screen.
• The character should move smoothly in the direction of the finger.
• When the player drags their finger, the character continuously follows the finger's movement.
• Support unrestricted directional movement: up, down, left, right and diagonal directions.
• Do not require players to keep their finger inside a small circular joystick.
• Remove the restrictive fixed joystick interface if it is no longer needed.
• Movement should feel immediate, fluid and responsive, as if the character is flying along with the player's finger.
• When the finger is released, stop movement smoothly.
• Prevent accidental page scrolling, browser gestures or unwanted touch interactions while controlling the character.
• Support touch events and Pointer Events correctly, including pointer capture where appropriate.
• Handle multi-touch safely so right-side action buttons continue to work independently.
• Keep the character within valid game boundaries.

Preserve existing controls

• The RIGHT HALF of the screen must remain available for existing attack, weapon and action controls.
• Do not break combat, shooting, sword attacks or other existing interactions.
• Desktop keyboard and mouse controls must remain unchanged.

3. REMOVE LEGACY BROWSER SAVE WARNING FROM PROFILE

Completely remove the following section from the player's Profile interface:

• "Retry cloud save"
• "An older browser save is retained on this device. Its unverified totals cannot replace a verified wallet score. Download it for the project owner to review."
• "Download older browser save"

Requirements:

• Remove the entire warning section from the Profile UI.
• Remove the associated Retry cloud save and Download older browser save buttons.
• Remove unnecessary UI state, event handlers and visual elements exclusively associated with this section.
• Do not display this warning elsewhere in the game.
• Preserve verified Supabase wallet profiles, Lifetime Score, personal-best leaderboard data and legitimate cloud-save functionality.
• Do not automatically import, overwrite or delete existing player records.
• Keep the Profile layout clean and responsive on desktop and mobile.

IMPORTANT: This is a UI cleanup request. Do not disable Supabase cloud saving or remove backend legacy-data safeguards. Only remove the unwanted warning and associated UI controls.

4. TESTING AND ACCEPTANCE CRITERIA

Leaderboard testing

• A higher-scoring run replaces the previous personal best.
• A lower-scoring run does not change the personal best.
• Refreshing the page does not reset the score.
• Disconnecting and reconnecting the wallet does not reset the score.
• The leaderboard displays the correct personal best.
• Backend score validation remains authoritative.

Mobile testing

Test on an actual mobile touchscreen, not only desktop browser emulation.

• Movement works anywhere on the left half of the screen.
• The character follows continuous finger movement smoothly.
• Diagonal movement works correctly.
• Releasing the finger stops movement.
• Right-side attack buttons remain responsive during movement.
• No accidental page scrolling or stuck movement occurs.
• Test different screen sizes and orientations.

Profile testing

• Legacy browser-save warning is completely removed.
• Both associated buttons are gone.
• Profile still displays verified wallet information and correct Lifetime Score.
• Supabase cloud saving continues working.

5. IMPLEMENTATION AND DEPLOYMENT

• Inspect the existing frontend, game engine, input handling and Supabase backend before editing.
• Avoid unnecessary database migrations.
• Do not delete existing player records or leaderboard data.
• Preserve Supabase RLS policies and server-side score validation.
• Do not expose service-role keys or secrets in frontend code.
• Run build and relevant tests.
• Deploy the updated game only after successful verification.

At completion, provide:

1. Files and functions changed.
2. Explanation of the new personal-best scoring logic.
3. Explanation of the new mobile movement implementation.
4. Confirmation that the legacy browser-save warning has been removed.
5. Test results for desktop and mobile.
6. Any remaining issues or limitations.

Do not report an issue as fixed unless it has actually been tested.