parthan-military

Temitola Francis

GAME DEVELOPMENT PROMPT — MOBILE FPS Create a complete, polished 3D multiplayer mobile first-person shooter (FPS) inspired by the fast-paced gameplay and competitive feel of modern mobile military shooters such as Call of Duty Mobile. 1. GAME CONCEPT Create an original game called "STRIKE FORCE: MOBILE". The game should be designed primarily for Android phones and optimized to run smoothly on mid-range and high-end devices. The game must have: First-person shooting Fast movement Multiplayer matches Bots for offline/practice gameplay Character progression Weapon customization Multiple game modes Original maps Original characters Original weapons Original sounds Original UI Original logos and branding Do NOT copy Call of Duty Mobile's copyrighted characters, maps, weapon skins, sounds, logos, names, UI, or other assets. 2. GAMEPLAY Make the gameplay feel responsive and competitive. Player controls should include: Left virtual joystick for movement Right side touch area for camera aiming Fire button Aim/ADS button Jump Crouch Reload Weapon switch Melee Grenade Sprint Slide Add: Sprinting Sliding Jumping Crouching Prone Reload animations Weapon recoil Bullet spread Hit detection Headshots Damage indicators Kill notifications Kill feed Footstep sounds Muzzle flashes Bullet impacts Explosions 3. GAME MODES Create these modes: Team Deathmatch Two teams fight until one reaches the required score. Domination Teams capture and defend three objectives. Search & Destroy One team attacks an objective while the other defends it. Players have limited lives per round. Free For All Every player fights individually. Practice vs Bots Allow the player to practice against AI-controlled enemies. 4. MAPS Create at least 3 completely original maps. Map 1: Desert Outpost Military base Buildings Watch towers Vehicles Open roads Indoor areas Multiple routes Map 2: Urban Collapse Destroyed city Apartments Streets Shops Underground passages Rooftops Map 3: Jungle Facility Tropical environment Military research facility Bridges Small buildings Dense vegetation Multiple combat routes Maps should contain strategic areas for close-range, medium-range and long-range combat. 5. WEAPONS Create an original weapon system with fictional weapon names. Categories: Assault rifles SMGs Shotguns Sniper rifles Marksman rifles LMGs Pistols Melee weapons Every weapon should have: Damage Fire rate Magazine size Reload time Recoil Accuracy Range Movement speed ADS speed Add weapon attachments such as: Optics Magazines Grips Barrels Stocks Create an attachment/unlock system that allows players to customize their weapons. 6. PLAYER CHARACTERS Create several completely original military-style characters. Each character should have: Unique appearance Clothing Voice Animations Profile Unlockable cosmetic outfits Do not use real people or copyrighted game characters. 7. MULTIPLAYER Build an online multiplayer architecture capable of supporting competitive matches. Include: Matchmaking Game rooms Player names Teams Scoreboards Kill/death statistics Ping indicator Match results XP rewards If a dedicated multiplayer backend is required, design the game so it can connect to a suitable server/backend. The architecture should prevent simple cheating and client-side score manipulation. 8. AI BOTS Create intelligent enemy bots. Bots should: Move around the map Search for enemies Shoot Reload Take cover Capture objectives Follow teammates Retreat when damaged Use different difficulty levels Difficulty: Easy Normal Hard Expert 9. PROGRESSION Create a player progression system. Include: Player XP Player levels Weapon XP Unlockable weapons Unlockable attachments Character cosmetics Achievements Daily missions Match rewards Create a profile screen showing: Level XP Matches played Wins Kills Deaths K/D ratio Favorite weapon 10. UI Create a professional mobile FPS interface. Main menu: PLAY LOADOUT STORE PROFILE MISSIONS SETTINGS During gameplay display: Mini-map Health Ammo Current weapon Score Timer Kill feed Objective indicators Make the UI responsive for different Android screen sizes. 11. GRAPHICS Use high-quality 3D graphics while maintaining mobile performance. Include: Realistic lighting Dynamic shadows Particle effects Explosions Smoke Muzzle flashes Bullet impacts Environmental effects Weapon animations Character animations Add graphics settings: LOW MEDIUM HIGH ULTRA Also include: FPS limit settings Resolution scaling Shadow quality Texture quality Effects quality Optimize the game to target stable performance on mid-range Android devices. 12. AUDIO Create an original sound system. Include: Weapon sounds Reload sounds Footsteps Bullet impacts Explosions UI sounds Ambient environment Character voice lines Use original or properly licensed audio assets. 13. LOGIN AND ACCOUNT Create an account system supporting: Email registration Login Password reset Guest mode Player profile Store player progression securely on the backend. 14. SHOP Create an in-game store for cosmetic items. Items can include: Character outfits Weapon skins Weapon animations Emotes Calling cards Profile decorations The store should be designed so that gameplay power is not unfairly locked behind payments. 15. SETTINGS Add: Graphics settings Audio settings Sensitivity ADS sensitivity Gyroscope Control customization Language Account settings Allow players to move and resize buttons on the HUD. 16. MOBILE OPTIMIZATION The game must: Support Android Support touch controls Work in landscape orientation Have optimized textures Use object pooling Use efficient lighting Minimize unnecessary memory usage Minimize battery consumption Maintain stable FPS Target Android 11 and newer. 17. DEVELOPMENT REQUIREMENTS Use a professional game engine such as Unity or Unreal Engine, choosing the option that provides the best balance between mobile performance and development speed. Organize the project cleanly: /Assets /Characters /Weapons /Maps /Animations /Audio /UI /Materials /Scripts /Prefabs Write modular, maintainable code. Do not create a fake prototype where buttons do nothing. Every major button and gameplay system must actually work. 18. DEVELOPMENT ORDER Build the game in stages: PHASE 1: Player controller Camera Touch controls Shooting Weapon system PHASE 2: First map Enemy bots Health/damage Respawning Score system PHASE 3: Multiplayer architecture Matchmaking Teams Online matches PHASE 4: Additional maps Additional weapons Loadout system Progression PHASE 5: UI Store Missions Profiles Settings PHASE 6: Optimization Bug fixing Android testing Final build 19. FINAL REQUIREMENT Deliver a fully playable original mobile FPS, not merely a visual mockup. The player should be able to: OPEN GAME → LOGIN/GUEST → MAIN MENU → SELECT MODE → ENTER MATCH → MOVE → AIM → SHOOT → KILL ENEMIES → COMPLETE MATCH → RECEIVE XP → UNLOCK CONTENT → CUSTOMIZE LOADOUT → PLAY AGAIN. Use original intellectual property throughout the project. Make the game feel like a high-quality competitive mobile military FPS, while ensuring that its characters, maps, weapons, branding, sounds, animations and interface are independently created and not copies of Call of Duty Mobile.

Comments (0)

No comments yet. Be the first!

Page 1 of 9

System Requirements Document for parthan-military

1. Introduction

"STRIKE FORCE: MOBILE" is a 3D multiplayer mobile first-person shooter (FPS) game designed for Android devices. It aims to deliver a fast-paced, competitive gaming experience inspired by modern mobile military shooters. The game will feature original content, including maps, characters, weapons, and sounds, ensuring a unique and immersive experience for players.

2. System Overview

"STRIKE FORCE: MOBILE" is a mobile FPS game targeting Android devices, optimized for mid-range and high-end performance. It offers a variety of game modes, including multiplayer and practice against AI bots, with a focus on competitive gameplay and player progression. The game will feature original intellectual property, avoiding any copyrighted content from existing games like Call of Duty Mobile.

2a. Product Interpretation and Delivery Boundary

The game will be delivered as a fully playable mobile application, with a focus on original content and competitive gameplay. It will include a comprehensive progression system, customizable weapons, and a variety of game modes. The game will be accessible to players via a landing page, with subsequent identity establishment through login or guest mode. All backend services will ensure secure and fair gameplay, with anti-cheat measures in place.

Page 2 of 9

2b. Source Content Inventory

Not applicable as no content source directive was provided.

2c. Page Content and Component Coverage

Landing

Information/State: Introduction to "STRIKE FORCE: MOBILE," game features, and audience.
Primary Actions: Proceed to Login or Guest mode.
Components: Game overview, call-to-action buttons.
States: Loading, error handling for network issues.

Login

Information/State: User authentication and account management.
Primary Actions: Email registration, login, password reset, guest continuation.
Components: Input fields, buttons for account actions.
States: Success, error messages for invalid credentials.

PLAY

Information/State: Game mode selection.
Primary Actions: Select game mode, start match.
Components: Mode list, start button.
States: Loading, error handling for matchmaking issues.

Page 3 of 9

Match

Information/State: Live match gameplay.
Primary Actions: Control character, engage in combat.
Components: HUD, controls for movement, aiming, shooting.
States: Loading, in-game events, match completion.

Match Results

Information/State: Post-match statistics and rewards.
Primary Actions: View results, continue to progression or next match.
Components: Scoreboard, XP rewards, match summary.
States: Success, error handling for data retrieval.

LOADOUT

Information/State: Weapon and equipment customization.
Primary Actions: Customize loadout, save changes.
Components: Weapon list, attachment options.
States: Loading, success, error handling for save issues.

STORE

Information/State: Cosmetic item browsing and acquisition.
Primary Actions: Purchase items, view inventory.
Components: Item list, purchase buttons.
States: Loading, success, error handling for transactions.

Page 4 of 9

PROFILE

Information/State: Player statistics and progression.
Primary Actions: View profile, track achievements.
Components: Stats display, achievement list.
States: Loading, success, error handling for data retrieval.

MISSIONS

Information/State: Daily missions and achievements.
Primary Actions: View missions, track progress.
Components: Mission list, progress indicators.
States: Loading, success, error handling for updates.

SETTINGS

Information/State: Game settings customization.
Primary Actions: Adjust graphics, audio, controls.
Components: Settings options, sliders, toggles.
States: Success, error handling for save issues.

Page 5 of 9

3. Functional Requirements

As a Player, I should be able to register, log in, or continue as a guest to access the game. (Provenance: explicit)
As a Player, I should be able to select and play different game modes, including Team Deathmatch, Domination, Search & Destroy, Free For All, and Practice vs Bots. (Provenance: explicit)
As a Player, I should be able to customize my loadout with different weapons and attachments. (Provenance: explicit)
As a Player, I should be able to view my profile, track my progression, and view statistics. (Provenance: explicit)
As a Player, I should be able to purchase cosmetic items from the in-game store. (Provenance: explicit)
As a Player, I should be able to adjust game settings, including graphics, audio, and controls. (Provenance: explicit)
As a Player, I should be able to receive XP and rewards after completing matches. (Provenance: explicit)
As a Player, I should be able to view match results and statistics after each game. (Provenance: explicit)

4. User Personas

Player: The primary user who logs in or uses guest mode, selects game modes, controls a character in matches, customizes loadouts, progresses through the game, shops for cosmetic items, and manages game settings.

Page 6 of 9

5. Core User Flows

Game Start and Login Flow
- Player opens the game and reaches the Landing page.
- Player chooses to log in, register, or continue as a guest.
- Upon successful login or guest continuation, the player accesses the main menu.
Game Mode Selection and Match Flow
- Player navigates to the PLAY page.
- Player selects a game mode and starts a match.
- Player engages in gameplay, utilizing controls for movement, aiming, and shooting.
- Match concludes, and the player views the Match Results page.
Loadout Customization Flow
- Player navigates to the LOADOUT page.
- Player selects weapons and attachments to customize their loadout.
- Player saves changes and returns to the main menu.
In-Game Store Flow
- Player navigates to the STORE page.
- Player browses available cosmetic items and makes purchases.
- Player views acquired items in their inventory.
Profile and Progression Flow
- Player navigates to the PROFILE page.
- Player views their statistics, achievements, and progression.
- Player tracks their favorite weapon and performance metrics.
Settings Adjustment Flow
- Player navigates to the SETTINGS page.
- Player adjusts graphics, audio, and control settings.
- Player saves changes and returns to the main menu.

Page 7 of 9

6. Visuals Colors and Theme

Muse: Gleb Kuznetsov
Palette:
- Background: #000000
- Surface: #1A1A1A
- Text: #FFFFFF
- Primary: #00FFFF
- Accent: #FF00FF
- Muted: #333333
Typography:
- Headings: Orbitron — Wide uppercase, strong contrast
- Body: Space Grotesk
- Scale: 1.414 modular, 64/45/32/22/16
Shape Language: Floating glass panels, radial layouts, thin luminous strokes
Layout: Full-bleed 3D scenes with floating UI elements
Motion: Continuous slow orbit, light sweeps, data streams
Imagery: Abstract 3D objects and particle fields

7. Signature Design Concept

A full-bleed 3D hero scene with a central holographic display surrounded by floating UI panels in electric cyan and magenta glows against a deep black background. The 3D object or scene is the dominant element, creating an immersive visual experience.

Page 8 of 9

8. Interaction Model & Motion Direction

Interaction Model: Parallax
Motion Tempo: Cinematic
Hero Dimensionality: WebGL
Landing Hero Motion Brief: The focal subject is a central 3D holographic display with floating UI panels. The transformation involves continuous slow orbit and light sweeps, resulting in an immersive visual experience. Reduced-motion state will simplify animations to static transitions.

9. Non-Functional Requirements

The game must maintain stable performance on mid-range Android devices, supporting Android 11 and newer.
All assets, including characters, maps, weapons, and sounds, must be original or properly licensed.
The game must prevent simple cheating and client-side score manipulation.
The in-game store must not lock gameplay power behind payments.

10. Tech Stack

Game Engine: Unity or Unreal Engine (selected for mobile performance and development speed)
Backend: Suitable server/backend for multiplayer support
Languages: C# (Unity) or C++ (Unreal Engine)
Tools: Modular project organization with clean code

11. Assumptions and Constraints

The game is primarily for Android devices, supporting landscape orientation and touch controls.
The project will be organized into specified subdirectories for assets and code.
The multiplayer architecture will include anti-cheat measures.

Page 9 of 9

12. Glossary

FPS: First-Person Shooter
ADS: Aim Down Sights
HUD: Heads-Up Display
XP: Experience Points
UI: User Interface
SMG: Submachine Gun
LMG: Light Machine Gun

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.

No completed page designs yet.

Completed design pages will appear here when they are ready to preview.