Flikk Didn't Make the Game You Pictured? 8 Fixes That Work
No game plan, a missing feature, something covered up or too easy? Here are 8 real problems we ran into on Flikk, and exactly how we fixed each one.
In this article
- First: two things that make every fix easier
- Problem 1: No game plan, just a red line
- Problem 2: The plan is a different game than the one in your head
- Problem 3: Part of your request is missing from the plan
- Problem 4: "Flikk can't make that one"
- Problem 5: Something is too small to read
- Problem 6: An edit broke something else
- Problem 7: The camera isn't where you wanted it
- Problem 8: The game is too easy
- The fix for almost everything
- FAQ
Making a game with AI is fast, but it isn't magic. Sometimes the plan isn't what you pictured. Sometimes a part of your idea goes missing, or an edit moves something you didn't ask about. That's normal, and almost everything can be fixed in a sentence.
Here are 8 real problems we ran into while making games on Flikk, what caused them, and the fix that worked. Every screenshot is from our own games.
Quick note: Flikk is our app. We're sharing the bumps on purpose. Knowing them saves you Tokens.
First: two things that make every fix easier
- Game plans are free. Before you build, you can change your idea and get a new plan as often as you like. Many problems are cheapest to fix right there.
- Edits don't break your live game. An edit costs 25 Tokens and takes about 5 minutes, and players keep the current version until the new one is ready. So trying a fix is low-risk.
Problem 1: No game plan, just a red line
What happened: we typed "A fun game" in the Create tab. No plan came back, only a red hint: "Say what the player actually does, even roughly."
Why: "fun" describes a feeling, not a game. The companion needs an action to build around.
The fix: add a verb. "A cat catches fish" is four words and got a full plan. Catch, jump, stack, dodge, match: any action works.
Problem 2: The plan is a different game than the one in your head
What happened: we typed "A racing game". Flikk made a plan called Turbo Circuit and decided everything itself: drag to steer, a drift button, a nitro tank, five rivals.
Why: anything you don't mention, the AI decides for you, usually with safe, typical choices.
The fix: tap Edit, or type a new, more detailed idea, and add what matters to you. When we described a steering wheel, a wide track, turrets and a 180-degree turn, every detail made it into the new plan. It was free, because we hadn't built anything yet.
Problem 3: Part of your request is missing from the plan
What happened: in an edit for Retro Quiz Show, we asked for podiums in red, blue, green and yellow and special lighting. The plan included everything else, but said: "Specific podium colors and lighting effects are determined by the engine's visual styling, so they were left out."
Why: some details aren't up to your game. Flikk says so instead of quietly skipping them.
The fix: read the last lines of every plan before you tap Build it. Then decide: build it anyway, or ask for the same feeling in a different way. We built it anyway, and the stage still changed a lot: it turned night, with a spotlight on the contestant.
Problem 4: "Flikk can't make that one"
What happened: we asked an existing game for tilt controls, steering by tilting the phone. A red note appeared: "Flikk can't make that one. Say what the game should be like instead — how it plays, looks or sounds."
Why: some features aren't possible on Flikk yet. Tilt controls are one, landscape games are another (every game is portrait).
The fix: describe the feeling instead of the feature. Instead of tilting, ask for a joystick, swipes or drag-to-move. Nothing was built and nothing was spent, so trying again costs nothing.
Problem 5: Something is too small to read
What happened: our first edit to Retro Quiz Show added an emoji bonus round. It worked, but the emoji were tiny. On a phone, you had to squint.
Why: the AI doesn't hold your phone. It can't see what's hard to read for you.
The fix: say exactly how big. "Make the emoji clues in the bonus round three times bigger" did it in one edit. Numbers ("three times", "twice as fast") beat vague words ("bigger", "faster").
Problem 6: An edit broke something else
What happened: after our second Retro Quiz Show edit, the question board got wider in one era and covered the score bar at the top.
Why: an edit can move things you didn't ask about, especially when it changes the layout.
The fix: describe what you see, in plain words. We typed: "The question board got wider and it covers the score board at the top. Please fix it so the points etc. can also be seen." Flikk turned that into "Reposition and resize the question board to prevent it from overlapping the top scoreboard", and about 5 minutes later it was fixed.
Tip: after every edit, play every part of your game, not just the part you changed.
Problem 7: The camera isn't where you wanted it
What happened: for our 3D platformer Lava Leap, we asked for the camera behind the player. It came out higher, looking down on the player. The game's How to play explained that you can swipe the right side of the screen to turn the view.
Why: in 3D, the camera is one of the hardest things to get exactly right from a sentence.
The fix: first, play it for a bit. A different camera than you pictured can still work. If it doesn't, describe it again in an edit with known camera words, like "the camera follows close behind the player". Our 3D game glossary has the words that help.
Problem 8: The game is too easy
What happened: Lava Leap's first stages were plain: run, jump, done. And after two edits to Hungry Cat Catch, it still wasn't hard enough for us.
Why: a first build plays it safe. Difficulty is something you tune once the game works.
The fix: name the challenge. "Make it harder" is vague. "Make some platforms move side to side and add lasers to jump over" gave Lava Leap real obstacles in one edit. Make Edits also suggests a one-tap "Make the game harder" if you just want a quick bump.
The fix for almost everything
Look back at the 8 fixes, and you'll see the same pattern:
- Say what you see. "It covers the score." "The emoji are tiny."
- Say what you want instead. "Make them three times bigger."
- Name things, not vibes. "Moving platforms and lasers," not "more exciting".
- Read the plan, including the last lines.
- Play everything after an edit.
Want more examples of edits that worked the first time? Here are 9 Make Edits prompts with before and after. Stuck on a prompt from the start? Our game prompt guide helps.
Download Flikk on iOS · Download Flikk on Android
FAQ
Why didn't Flikk make a game plan for my idea?
Your idea was probably too vague. If you see the red hint "Say what the player actually does, even roughly.", add an action, like catch, jump or stack. "A cat catches fish" is enough.
Why did Flikk leave part of my idea out?
Some details aren't possible on Flikk yet, or are decided by the app rather than your game. The plan says what was left out and why, before you spend anything. You can change your idea or build it anyway.
How do I fix a bug in my Flikk game?
Open your game's page, tap Make Edits and describe what you see and what you want instead, like "The question board covers the score at the top. Please move it so I can see the score." Flikk shows a plan of the fix, and it's ready in about 5 minutes.
Does fixing my game cost Tokens?
Changing your idea before you build is free. After the game is built, each edit costs 25 Tokens.
Will players see my game while I fix it?
Yes, but they keep the current version until the fix is ready. Then everyone gets the new version.
