You added your first event, we're sure it won't be the last!

First event

You used a behavior for the first time, things are way simpler with them don't you think?

First behavior

Previewing your game is the first step towards a complete game!

First preview

Amazing, you just exported your first game! It's truly the quickest way to share it.

First web export

Want to improve your game graphics? Select as many effects as you want from our list!

First effect

Was it an unexpected animation, or were you just curious? Anyway, congrats on using the debugger for the first time!

First debug

Extensions will speed up your project, so use as many as you can!

First extension

If 10 people played your game, it has to mean something right?

Insert a coin

Wow! 100 people played your game, that's amazing, congratulations!

Into Space

1000 people played your game, you're on a whole new level. What is your secret?

Millenium Falcon

Can you imagine if 10k people came to visit you? They probably wouldn't all fit in your living room!

It's over 9000!

50k people playing your game must feel really rewarding, all of the time you put in to making it is paying off.

Fits in your house?

100k people had a good time playing your games, isn't it the best feeling in the world? You must have come a long way to achieve that.

Fits in your yard?

{user} got 100,000 plays on all their games

A second game with 10 players? Is it the same genre as the first?

Solid Snake

{user} got 10 plays on two different games

3 games that each had 100 players! Have you found a name for your game studio?

Eevee

{user} got 100 plays on three different games

You put a star for GDevelop on GitHub - thank you!

Open-source love

{user} starred GDevelop's source code on GitHub

Thank you for representing GDevelop in a major event!

Marketer

{user} represented GDevelop in a major event

You follow GDevelop on TikTok - thank you!

TikTok fan

{user} subscribed to GDevelop's account on TikTok

X follower

{user} follows GDevelop's account on "X" (Twitter)

Youtube subscriber

{user} subscribed to GDevelop's YouTube channel

Congrats on finishing the GDevelop Essentials course!

GDevelop Essentials course graduate

{user} completed the GDevelop Essentials course

Congrats on finishing the UI/UX Essentials course!

UI/UX Essentials course graduate

{user} completed the UI/UX Essentials course

 Game is still bugy but is new .
POCKET MAYHEM

Build it. Battle it. Break it.


---

🚨 CRITICAL DEVELOPMENT RULES

These rules apply to the entire project.

1. BUILD REAL FEATURES

Every feature requested in this document must be implemented as actual working gameplay whenever technically possible.

Do NOT create:

- Fake buttons
- Decorative buttons that do nothing
- Fake menus
- Fake shops
- Fake inventories
- Fake battles
- Fake AI
- Fake physics
- Fake vehicles
- Fake missions
- Fake save systems
- Fake progression
- Fake account systems
- Fake mini games
- Fake creator tools
- Fake world maps
- Placeholder interactions pretending to be finished features

If a button exists, it must perform its intended action.

If a feature cannot reliably be implemented, replace it with a smaller working version rather than creating a fake version.

2. WORKING GAMEPLAY > FEATURE COUNT

A smaller game with genuinely working systems is better than a huge game filled with non-functional features.

Prioritise:

1. Playability
2. Reliability
3. Fun
4. Performance
5. Good UX
6. Visual polish
7. Feature quantity

3. TEST EVERYTHING

After implementing a feature, test it.

Do not assume generated code or events work correctly.

Check:

- Object references
- Variables
- Collisions
- Physics
- AI
- Controls
- UI
- Saving
- Loading
- Progression
- Rewards
- Unlocks
- Scene transitions
- Mobile input
- Desktop input

Fix errors before moving on.

4. USE THE CHOSEN ENGINE CORRECTLY

If building in Unity, use appropriate Unity systems such as:

- C#
- Unity UI
- ScriptableObjects
- Physics2D
- Tilemaps
- Animator
- NavMesh/pathfinding where appropriate
- Input System
- Particle systems
- Object pooling
- Addressables where appropriate
- Persistent data systems

If building in GDevelop, prioritise:

- Events
- Behaviours
- Extensions
- Variables
- Storage
- Object groups
- Timers

Use JavaScript only when it provides a clear advantage or is necessary.

If building in another engine, use that engine's native systems instead of pretending that another engine's functionality exists.

5. DO NOT CLAIM SOMETHING WORKS IF IT DOESN'T

Never say a feature is finished simply because its UI exists.

A feature is finished only when the player can actually use it.

---

🔐 ACCOUNT SYSTEM

Create a simple local account system using only:

- Username
- 4–6 digit PIN

Do NOT require:

- Email
- Phone number
- Password
- Social media
- External account

Account Screen

Show:

POCKET MAYHEM

Username
"[ Enter your name ]"

4–6 digit PIN
"[ Enter PIN ]"

Buttons:

- Create Account
- Login
- Guest Mode

The interface must be simple and mobile friendly.

PIN input must be hidden.

Create Account

Validate:

- Username is not empty
- Username uses allowed characters
- PIN contains 4–6 digits
- PIN is valid

Create a local player profile.

Show:

Account Created!

Username: PlayerName

Then enter the game.

Login

Allow players to enter their username and PIN.

If incorrect:

Incorrect username or PIN.

Never display the stored PIN.

Multiple Profiles

Support multiple local profiles where practical.

Each profile should have independent:

- Resources
- Buildings
- HQ
- Troops
- Weapons
- Vehicles
- Campaign
- Missions
- Mini-game scores
- Collection
- Creator creations
- Settings

---

💾 SAVE SYSTEM

Implement a genuine working save system.

Save:

- Profile ID
- Username
- Account data
- Resources
- Buildings
- Building levels
- HQ level
- Troops
- Weapons
- Inventory
- Vehicles
- Campaign progress
- Missions
- World map progress
- Mini-game unlocks
- Mini-game high scores
- Collection
- Shop purchases
- Creator creations
- Settings
- Audio settings
- Graphics settings
- Controls

Automatically save after important actions.

Also save when leaving gameplay where appropriate.

Provide:

Save Game

and:

Load Game

buttons where appropriate.

Continue

Continue must restore the player's previous progress.

New Game

New Game must display a confirmation dialog before resetting progression.

Reset Progress

Reset Progress must display a clear confirmation dialog.

Never delete progress immediately without confirmation.

Guest Mode

Guest Mode must work without an account.

Display:

«Guest saves are stored on this device and may not transfer to another device.»

Cloud-Save Architecture

Structure the save system so a backend/cloud database can be added later.

Do NOT pretend that local storage automatically synchronises between devices.

If no backend exists, keep the system genuinely local.

---

🏠 BASE MODE

Create a fully playable base-building system.

Players can build:

- HQ
- Resource Buildings
- Storage
- Barracks
- Factory
- Research Lab
- Workshop
- Hospital
- Shop
- Archer Tower
- Cannon
- Rocket Launcher
- Tesla Tower
- Walls
- Gates

Buildings must actually:

- Be placed
- Be selected
- Be moved where appropriate
- Be upgraded
- Perform their intended functions
- Take damage
- Be destroyed

Resources:

- Coins
- Gems
- Wood
- Stone
- Scrap

HQ levels:

1–20

HQ progression should unlock:

- Buildings
- Weapons
- Troops
- Vehicles
- Missions
- Areas
- Mini games
- Upgrades

---

⚔️ BATTLE MODE

Create real battles against enemy bases.

Deployable units:

- Warrior
- Archer
- Bomber
- Tank
- Fire Trooper
- Rocket Soldier
- Robot

Each unit must have real differences in:

- Health
- Speed
- Damage
- Attack range
- Attack speed
- Targeting
- Movement

Units must actually attack enemies and buildings.

Buildings must have health.

Buildings must be destroyable.

Destruction should include:

- Explosions
- Debris
- Particles
- Smoke
- Screen shake
- Sound effects
- Damage feedback

Give real rewards after battles.

---

🛡️ DEFENCE MODE

Allow enemies to attack the player's base.

Implement:

- Enemy spawning
- Wave counter
- Base health
- Defensive towers
- Difficulty scaling
- Rewards
- Boss waves

Enemies must actually attack the player's base.

Defensive towers must actually target and attack enemies.

---

🔫 SHOOTING RANGE

Create a fully playable shooting range.

Weapons:

- Pistol
- Shotgun
- Cannon
- Rocket Launcher
- Grenade Launcher
- Laser

Desktop

- Mouse aiming
- Mouse shooting
- Keyboard controls

Mobile

- Touch aiming
- Touch dragging
- Large fire button

Include:

- Targets
- Moving targets
- Destructible objects
- Timer
- Score
- Combos
- Rewards
- Accuracy tracking

Shots must actually interact with targets.

---

💥 MAYHEM SANDBOX

Create a real physics sandbox.

Players can spawn:

- Characters
- Vehicles
- Weapons
- Boxes
- Barrels
- Platforms
- Ropes where supported
- Springs where supported
- Traps
- Cannons
- Targets

Objects should physically interact where practical.

Controls:

- Move
- Rotate
- Connect
- Duplicate
- Delete
- Start simulation
- Stop simulation
- Reset

Create satisfying physics interactions and chain reactions.

Do not simulate physics with fake animations if actual engine physics can reasonably be used.

---

🎮 10 MINI GAMES

Create genuinely playable mini games.

1. Target Blast

Shoot targets before the timer expires.

2. Mayhem Dodge

Dodge falling and moving hazards.

3. Scrap Grab

Collect as much scrap as possible before time runs out.

4. Rocket Rampage

Destroy structures using rockets.

5. Tank Trouble

Fight enemy tanks in an arena.

6. Bomb Builder

Place objects strategically and cause controlled destruction.

7. Crazy Delivery

Drive a vehicle through an obstacle course while protecting the delivery.

8. Stack Attack

Stack physics objects as high as possible.

9. Laser Reflex

React to changing laser patterns.

10. Defuse Mayhem

Complete a timed puzzle before the countdown ends.

Every mini game must have:

- Start
- Restart
- Pause
- Exit
- Real controls
- Objective
- Score
- Win condition
- Lose condition
- Rewards

Save high scores.

Unlock mini games through progression.

---

💣 DESTRUCTION CHALLENGES

Create real destruction challenges involving:

- Buildings
- Weapons
- Explosions
- Chain reactions
- Combos
- Timers
- High scores

Reward players based on actual gameplay results.

---

🛠️ CREATOR MODE

Create a working custom-level creator.

Players can create:

- Shooting ranges
- Obstacle courses
- Arenas
- Physics challenges
- Destruction challenges

Tools:

- Place
- Move
- Rotate
- Delete
- Duplicate
- Save
- Load
- Rename
- Play
- Edit

Creator levels must actually be playable after being created.

Save creations locally.

---

🗺️ WORLD MAP

Create:

- Grasslands
- Desert
- Snowlands
- Volcano
- Industrial Zone
- Islands

Each area should contain different:

- Enemies
- Missions
- Buildings
- Resources
- Challenges
- Rewards

Areas unlock through actual progression.

---

🚗 VEHICLES

Create functional:

- Buggy
- Car
- Truck
- Tank
- Helicopter
- Boat

Vehicles must have actual movement and collision.

Use appropriate simplified controls where full simulation would hurt mobile performance.

Support:

- Keyboard
- Mouse where appropriate
- Touch controls

---

📜 CAMPAIGN

Create progressive campaign missions involving:

- Destroying enemy bases
- Collecting resources
- Protecting buildings
- Winning battles
- Completing mini games
- Destroying targets
- Driving vehicles
- Surviving waves
- Completing destruction challenges

Missions must track actual objectives.

Give real rewards.

---

🖥️ HUD

Create a responsive HUD containing where appropriate:

- Coins
- Gems
- Wood
- Stone
- Scrap
- Health
- Objective
- Score
- Timer
- Selected weapon
- Equipment
- Mini-map

HUD elements must update from actual game data.

---

📱 MOBILE CONTROLS

Support:

- Virtual joystick
- Touch movement
- Touch aiming
- Touch shooting
- Touch building placement
- Touch interaction
- Large action buttons
- Vehicle controls

Controls must actually work.

Buttons must be large enough for comfortable touch input.

---

🖱️ DESKTOP CONTROLS

Support:

- WASD movement
- Mouse aiming
- Mouse shooting
- Keyboard shortcuts
- Mouse building placement
- Vehicle controls
- Escape/Pause

Show controls in Settings.

---

🎨 GRAPHICS

Use a consistent colourful toy-style visual identity.

Include where performance allows:

- Cute characters
- Detailed environments
- Smooth animations
- Particles
- Explosions
- Projectiles
- Shadows
- Destruction effects
- Screen shake
- Weather
- Day/night effects
- Smoke
- Debris
- Floating damage numbers
- Reward animations

Do not sacrifice gameplay performance simply to add visual effects.

---

⚙️ SETTINGS

Create a working Settings menu.

Include:

- Music volume
- Sound volume
- Vibration
- Graphics quality
- FPS options
- Controls
- Language
- Save Game
- Load Game
- Account
- Log Out
- Reset Progress

Every setting must actually affect the game.

If a setting cannot be implemented, remove it rather than displaying a non-functional option.

---

🛒 SHOP

Create a functional in-game shop.

Shop items must actually:

- Cost resources
- Be purchased
- Be added to inventory/collection
- Persist after saving

Do not create fake purchase buttons.

---

🏆 COLLECTION

Create a working collection system for unlocked:

- Troops
- Weapons
- Vehicles
- Buildings
- Items
- Achievements
- Other unlockables

Collection data must persist in saves.

---

📱 RESPONSIVE UI

Every screen must work on:

- Phones
- Tablets
- Chromebooks
- Laptops
- Desktop monitors

Every:

- Button
- Popup
- Tab
- Shop item
- HUD element
- Menu
- Dialog

must fit its content.

Never allow:

- Text overflow
- Text clipping
- Text outside buttons
- Overlapping controls
- Unreadable text
- Tiny touch targets

Use responsive layouts, padding, automatic sizing and appropriate font scaling.

---

⚡ PERFORMANCE

Optimise for lower-end devices.

Use:

- Object pooling
- Reusable objects
- Efficient collision systems
- Efficient AI
- Reasonable particle counts
- Limited physics objects
- Appropriate update rates
- Lightweight effects
- Efficient save operations

Avoid unnecessarily spawning hundreds or thousands of objects.

Prioritise stable frame rates.

---

🧪 FINAL QUALITY ASSURANCE

Before declaring the game finished, actually test:

Accounts

- Account creation
- Login
- PIN validation
- Guest Mode
- Multiple profiles
- Logout

Saving

- Save
- Load
- Continue
- New Game
- Reset confirmation
- Persistence after closing/reopening

Base

- Building
- Moving
- Upgrading
- Resources
- Destruction
- HQ progression

Battles

- Units
- Enemy AI
- Attacks
- Damage
- Destruction
- Rewards

Defence

- Waves
- Enemy spawning
- Towers
- Bosses
- Rewards

Shooting

- Weapons
- Aiming
- Shooting
- Targets
- Accuracy
- Combos
- Score

Vehicles

- Movement
- Collision
- Controls
- Vehicle-specific behaviour

Sandbox

- Spawning
- Physics
- Moving
- Rotating
- Connecting
- Duplicating
- Deleting
- Simulation
- Reset

Mini Games

Test all 10 mini games individually.

Creator

- Create
- Save
- Load
- Rename
- Duplicate
- Delete
- Play
- Edit

Campaign

- Missions
- Objectives
- Rewards
- Unlocks
- World map progression

UI

Test different:

- Resolutions
- Aspect ratios
- Screen sizes
- Mobile touch input
- Desktop input

Fix all:

- Broken events
- Missing variables
- Incorrect references
- Collision bugs
- Control bugs
- Save bugs
- Progression bugs
- UI overlap
- Text overflow
- Missing rewards
- Broken unlocks

---

🚨 FINAL ANTI-FAKE-FEATURE REQUIREMENT

This requirement is mandatory.

DO NOT create a button, menu, system or feature merely because the specification mentions it.

For every feature ask:

«Can the player actually use this?»

If the answer is no:

1. Implement it properly if reasonably possible.
2. If it cannot be implemented reliably, simplify it.
3. If it still cannot be made functional, remove it from the UI.
4. Never leave a fake feature pretending to work.

Examples:

❌ A Shop button that only opens a decorative shop screen.

✅ A Shop button that opens a real shop where purchases change the player's inventory.

❌ A Battle button that shows an animation and awards fake rewards.

✅ A Battle system where units actually fight, buildings take damage, battles can be won/lost and rewards come from the actual result.

❌ A Save button that displays "Saved!" without saving anything.

✅ A Save button that actually serialises the player's progression and restores it through Load/Continue.

❌ A vehicle that only plays a driving animation.

✅ A vehicle with actual movement, collision and controls.

❌ A Creator Mode where objects cannot really be saved.

✅ A creator system where the player can build, save, load and play their creation.

---

DEVELOPMENT PRIORITY

Build in this order:

PHASE 1 — CORE

1. Project setup
2. Main menu
3. Player profile
4. Save/load
5. Input system
6. Core character controller
7. Basic resources
8. Basic UI

PHASE 2 — CORE GAMEPLAY

9. HQ
10. Building placement
11. Building upgrades
12. Basic troops
13. Enemy AI
14. Battle system
15. Destruction
16. Rewards

PHASE 3 — EXPANSION

17. Defence waves
18. Shooting range
19. Weapons
20. Vehicles
21. World map
22. Campaign
23. Missions

PHASE 4 — MAYHEM

24. Physics sandbox
25. Destruction challenges
26. Mini games

PHASE 5 — CREATION

27. Creator mode
28. Save/load creations
29. Play created levels

PHASE 6 — POLISH

30. Shop
31. Collection
32. Animations
33. Particles
34. Sound
35. Screen shake
36. Mobile UI
37. Desktop UI
38. Performance optimisation
39. Accessibility
40. Final QA

Do not move to the next major phase while the previous phase contains critical broken functionality.

---

FINAL EXPERIENCE

The finished game should deliver this loop:

BUILD → UPGRADE → EXPLORE → BATTLE → SHOOT → DESTROY → PLAY → CREATE → UNLOCK → SAVE → CONTINUE

POCKET MAYHEM should be fun in short sessions while also providing enough systems for longer play sessions.

The game should feel like a colourful interactive toy box where players can build things, fight things, drive things, shoot things, destroy things and create their own chaos.

POCKET MAYHEM

Build it. break it . battle it .

hwt2020

Stats

Socials

Achievements

hwt2020

Games

Tinydino13_games_gamehub

POCKET MAYHEM