Made with Nano Banana 2 Lite · CC0 · 9 Oct 2026

Chunky low-poly

Generated from: a scene from a small video game about: # MASTER PROMPT — BUILD SLING LEGACY COMPLETE ANDROID GAME Act as a senior Godot game developer, Android game engineer, 3D gameplay programmer, UI/UX designer, and software testing engineer. Your task is to CREATE THE ACTUAL COMPLETE PROJECT FILES for my football game. Do not just explain how to build it. Do not return only source-code snippets, a plan, a mockup, or a report claiming that files were created. ## 1. Game identity - Game title: SLING LEGACY - Subtitle: A Real Football Career - Creator credit: Maelainin Assari - Stadium name: الملعب الكبير — دوار اللوح - Target platform: Android APK - Engine: Godot 4.2.x - Renderer: Compatibility (OpenGL) - Orientation: Landscape - Interface: Arabic RTL by default - Visual identity: Dark navy blue, vivid green, white, realistic football stadium lighting - Reference image: Use the attached image as a visual guide, not as a requirement to copy every detail exactly. ## 2. Core gameplay Create a lightweight, playable 3D football game with 6 players per team, including the goalkeeper. Required features: - Six players per side on the pitch, including goalkeepers. - Direct control of one outfield player at a time. - Automatically switch the controlled player to a suitable teammate when possession or play changes. - Touchscreen virtual joystick. - Pass, shoot, sprint, tackle/dribble, and player-switch buttons. - Responsive controls suitable for Android phones. - Basic but believable teammate AI and opponent AI. - Goalkeepers that can move and save shots. - Ball physics, passing, shooting, possession, goals, throw-ins or simple restart rules, and match timer. - Match start, pause, resume, restart, final score, and return-to-menu functions. - Offline matches must work without an internet connection. - Do not fake gameplay by merely calculating a score and displaying an animation. The player must be able to control a real playable match. ## 3. Career mode Build a working career mode containing: - Player profile and position. - Fictional clubs and fictional players. - Club selection. - Match schedule and results. - Training sessions that improve player attributes. - Player progression and experience. - Basic fitness and manager trust. - League table, points, wins, draws, and losses. - Goals and assists statistics. - Saved career data that persists after closing the game. - New career, continue career, and delete/reset career options with confirmation. Career mode must be connected to the match system. Playing a match should affect the career results and statistics. ## 4. Additional screens Implement functional screens for: - Main menu. - New career and player creation. - Club selection. - Career dashboard. - Match setup and gameplay. - Pause menu. - Match result. - Training. - League standings. - Statistics. - Settings. - About and credits. - Multiplayer/friends screen, only if a genuinely working implementation is feasible. Do not pretend online multiplayer works if it does not. If real online multiplayer requires a server or credentials, clearly document that limitation and prioritize a fully working offline game. ## 5. Art, audio, and content - Use simple, lightweight 3D models suitable for medium-powered Android phones. - Players must have no visible faces. Use faceless models. - Create distinct fictional team kits and colors. - Add a football, pitch markings, goals, stadium, crowd ambience, and appropriate visual effects. - Create a clean SLING LEGACY logo and Android icon. - Add original, lightweight sound effects for kicks, passes, goals, whistles, and crowd reactions. - Music must be OFF by default, with a settings toggle if music is included. - No copyrighted club logos, copyrighted player likenesses, or unlicensed music. - Use Arabic text that renders correctly. Include appropriate Arabic fonts and verify RTL layouts. - Keep performance, memory usage, and APK size in mind. ## 6. Required reminder Before gameplay, show this short reminder once per session: "لا تلهك الألعاب عن الصلاة وذكر الله." Do not add prayer times, a prayer-city system, or unnecessary religious screens. Keep the reminder brief and respectful. ## 7. Technical requirements - Use Godot 4.2.x and the Compatibility renderer. - Include every required scene, script, resource, font, texture, audio file, configuration file, and Android export preset. - Use clean, organized, maintainable GDScript. - Avoid missing resource references, invalid node paths, unsupported APIs, syntax errors, and broken buttons. - Ensure project.godot is at the root of the project. - Include the correct Android package ID: com.maelainin.slinglegacy - Configure landscape orientation. - Add Android export settings and explain any required signing configuration. - Do not require me to install Godot locally if a reliable cloud build is possible. - Provide a GitHub Actions workflow that installs or uses compatible Godot 4.2.x and Android export templates, exports a debug APK, and uploads it as a downloadable artifact. - Verify that the workflow uses real, compatible tool versions and correct commands. Do not invent action names or assume an export template is installed when it is not. ## 8. Deliver actual files Create this project structure: SLING-LEGACY/ project.godot icon.png export_presets.cfg README.md LICENSE scenes/ scripts/ assets/ fonts/ textures/ audio/ icons/ tests/ .github/ workflows/ android.yml You may add any additional files required by the game. IMPORTANT DELIVERABLES: 1. Create every project file with real contents. 2. Put project.godot at the project root. 3. Package the complete project into SLING-LEGACY-v1.0.zip. 4. Attach the ZIP as an actual downloadable file in your response. 5. Include README instructions for importing the project, building the APK through GitHub Actions, downloading the APK artifact, and installing it on Android. 6. Include a checklist of features implemented and features not implemented. 7. Run all available checks and tests. Report actual results only. 8. If you cannot build the APK in your environment, say so explicitly. Do not claim that it was built or tested. 9. If you cannot create or attach a ZIP, explain that limitation instead of pretending a download link exists. ## 9. Acceptance criteria The project is not finished merely because the files exist. Check that: - The main menu opens. - New career works. - Career data saves and loads. - Club selection works. - The match starts. - The joystick and gameplay buttons work. - Players move and switch correctly. - Passing, shooting, goals, and match restart work. - The pause and result screens work. - Arabic text displays correctly. - The project opens in the specified Godot version. - The Android export workflow is valid. Start by creating the actual project files, then validate them, package them, and provide the real downloadable archive. Prioritize a small, stable, playable game over ambitious features that are broken. Never substitute a report or a design image for the actual project., as an in-game screenshot in chunky low-poly 3D with flat shaded materials. Palette: dusk violet #2b2d42, stone #8d99ae, player coral #ef8354, threat teal #2a9d8f, accent gold #f4d35e. Everything is original: never draw or resemble characters, places or logos from existing games, films or brands (no red-capped plumbers, no famous mascots), even when the idea names one. Keep the pictures honest: they promise what a small first version of this game, made in a game engine in a few days, can look like. Simple readable shapes, clear silhouettes, few flat materials, the in-game camera view. Never film stills, photoreal renders, AAA key art, detailed textures, cinematic lighting, or anything that looks like a big-studio game. No text, UI, HUD, logos or editor screens inside any image.