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

Flat colour

Generated from: a scene from a small video game about: a game hevily inspired by tricky castle and it kinda looks same # CURIOUS CASTLE ### A trick-room puzzle platformer **Curious Castle** is a 2D, single-screen puzzle-platformer heavily inspired by the *Tricky Castle* style of gameplay. You play as a mysterious French wanderer carrying a lantern, entering a strange castle filled with traps, misleading objects, strange mechanisms, and rooms that constantly challenge your assumptions. The goal is simple: **Reach the exit of every room and continue deeper into the castle.** But the obvious solution is rarely the correct one. --- ## 1. HOW THE GAME LOOKS The game is presented in **2D side-view pixel/artistic style**. Each level is a **single-screen room**. You can see almost the entire room when you enter. The castle should feel: * old * mysterious * slightly creepy * lonely * beautiful rather than horrifying * full of secrets ### Visual atmosphere Think: **old European castle + fairy-tale darkness + mysterious puzzle world.** Stone walls, wooden platforms, old paintings, candles, chains, bookshelves, statues, giant doors, broken architecture and strange mechanisms. The protagonist is visually simple: **A small French wanderer carrying a lantern.** The lantern becomes an important part of both the character's identity and later gameplay. The castle should not be covered in extreme darkness. The player needs to clearly see the objects that matter. --- # 2. HOW A LEVEL WORKS Every level is one self-contained room. You enter from one side. Somewhere in the room is the exit. Your job is to figure out: **“How the hell do I get there?”** A room might contain: * platforms * doors * buttons * levers * pressure plates * crates * spikes * fire * moving platforms * switches * paintings * statues * signs * fake objects * hidden mechanisms * strange environmental details But objects should never exist simply because the designer needed something to put in the room. **Everything should have a purpose.** --- # 3. THE MAIN GAMEPLAY LOOP The basic loop is: **ENTER ROOM → OBSERVE → EXPERIMENT → FAIL → UNDERSTAND → SOLVE → EXIT** For example: You enter a room. You see: * a huge wall * a crate * a lever * spikes * an exit Your first assumption might be: > “I need to activate the lever.” You try it. Something happens—but not what you expected. You experiment. Eventually you realize: **The crate isn't decoration. It's part of the solution.** You use it to reach the higher platform. You reach the exit. The next room introduces another idea. --- # 4. THE IMPORTANT RULE Curious Castle should follow one fundamental philosophy: ### The player should think: **“OH. I SHOULD HAVE NOTICED THAT.”** Not: **“HOW THE FUCK WAS I SUPPOSED TO KNOW THAT?”** The game can surprise the player. It can trick them. It can make them question everything. But after discovering the solution, the player should be able to look back at the room and understand why the solution worked. --- # 5. THE TRICKS The castle constantly plays with player assumptions. For example: ### A door that looks locked The player searches for a key. There is no key. Eventually they realize: **The door was never locked.** --- ### Spikes that look dangerous The player carefully tries to avoid them. Eventually they discover they're only painted onto the floor. --- ### An exit that isn't an exit The giant golden arch looks like the obvious way out. The player reaches it. Nothing happens. Eventually they discover it's only a painting. The real exit was somewhere else. --- ### A lever that seems important The player pulls it. Something happens across the room. But that isn't actually the solution. The lever was designed to make the player think it controlled something important. --- The important part is that these tricks should be **logical**, not random. --- # 6. PLATFORMING The platforming should stay relatively simple. The game is primarily about **thinking**, not difficult execution. The player can: * walk * run * jump * interact * restart Jumping shouldn't require extremely precise platforming. The challenge comes from figuring out **where you need to go and what you need to do.** --- # 7. DEATH Death should be cheap. If the player: * hits spikes * falls * gets crushed * activates the wrong trap the room immediately resets. No long loading screen. No losing progress. No punishment that makes experimentation annoying. The philosophy is: **Failure is part of solving the puzzle.** The player should be encouraged to try stupid things. --- # 8. THE NARRATOR Every level has a narrator. The narrator appears in a small dialogue box during the room. The narrator can: * introduce the room * comment on what the player does * react to failures * make observations * occasionally give clues * tell jokes * create mystery * occasionally mislead the player The narrator becomes part of the personality of Curious Castle. But the narrator shouldn't simply explain every puzzle. The player still needs to figure things out themselves. --- # 9. HINT SYSTEM If a player gets stuck, they can request hints. Each room can have three levels: ### Hint 1 — Nudge Points the player toward something. ### Hint 2 — Stronger clue Explains what they should be investigating. ### Hint 3 — Solution Essentially tells them what to do. Hints should never introduce information the room itself didn't communicate. --- # 10. THE LANTERN The lantern is the signature visual element of the game. At first, it is mostly part of the protagonist's appearance. Later, it becomes a gameplay mechanic. Certain things in the castle behave differently depending on whether the lantern is on or off. For example: **Objects visible only in darkness.** **Platforms that become solid under light.** **Symbols revealed by the lantern.** **Creatures or mechanisms that react to light.** This mechanic should be introduced gradually rather than dumped on the player. --- # 11. LEVEL PROGRESSION The game should eventually have around **100 levels**. But the difficulty shouldn't increase simply by making platforms smaller or traps faster. Instead: ### Early levels Teach one idea. ### Middle levels Combine two ideas. ### Later levels Combine several ideas the player has already learned. The player gradually learns the **language of the castle.** For example: **Level 5:** Learn that paintings can hide things. **Level 20:** A painting becomes part of a puzzle. **Level 50:** A painting interacts with another mechanic. **Level 80:** The player sees something that looks like a painting and has to decide whether it's actually one. The game rewards the player for remembering. --- # 12. WHAT MAKES CURIOUS CASTLE DIFFERENT The game isn't about defeating enemies. It isn't about collecting huge amounts of loot. It isn't about becoming stronger. The player's progression is: ### YOU become smarter. The character doesn't gain ten new abilities. **The player learns how the castle works.** That's the real progression. --- # 13. THE FEELING WE WANT The ideal reaction after solving a room is: > “Wait…” > “Oh.” > “OH!” > “You fucking bastard.” And then the player laughs and enters the next room. 😂 The castle should constantly make the player question their assumptions without making them feel cheated. --- # 14. THE CORE IDENTITY **Curious Castle** is: > **A mysterious 2D puzzle-platformer where every room is a small mystery, the castle constantly challenges your assumptions, and the only real way forward is to understand what the room is actually telling you.** The castle doesn't become harder because it becomes more unfair. **It becomes harder because the player has to think differently.**, as an in-game screenshot in flat colour 2D shapes with a bright limited palette. Palette: sky blue #8ecae6, grass #3a7d44, player sunflower #ffb703, threat red #d62828, accent white #fdfcdc. 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.