u/Belbebi_builds

Can you pin a database to a specific version? Would be handy for starting another save with the same setup later.

Just one more engine switch. For security reasons.

The only difference is whether the press calls it a shock result.

Does the undo history stick around after you close the editor, or is it just for the current session?

The little green three-wheeler is my favourite. I'd be taking screenshots of the traffic instead of getting on with the story.

Ask for a loan deal with an option to buy the chair.

The part I'd want is useful feedback on why a tactic is too demanding—limited training time, tired players, or one role a player can't handle. Otherwise simplifying it could mean removing instructions at random. Being able to fix one specific weakness would make the climb through the leagues more interesting to me than just adding complexity as the squad improves.

I'd test a more opaque dialogue panel before changing the font. In these shots, the tree and ground textures showing through behind the letters draw my eye more than the letter shapes. A longer dialogue sample at the actual play resolution would also help judge comfort beyond these short lines.

Thanks for rerunning it. The first/repeat purchase mix I wondered about wasn't doing much in your check, while the country mix changed the picture a lot. I'd add the filtered 20% figure alongside the original 60%, with the dates and regions, so people don't lose that context.

I'd make the first lesson audible: close your eyes, hear the pursuing footsteps slow and switch to searching; open them, hear the creature lock onto you again. Let that happen at a safe distance before asking the player to trust darkness in a real chase. Notes can explain the rule, but the sound change would tell me whether it's working right now.

Are you comparing each platform's first seven days, or everything since launch? With iPhone arriving a week later, the 60% gap may also reflect a different mix of first and repeat purchases. A matched launch window would make that number easier to interpret.

I'd give Lebedev the league starts and keep Lomas in the rotation rather than promise either a full season as first choice. Lebedev's 18 Off the Ball, 16 Composure and 15 league goals make him a credible option now; Cano at 18 looks more like the longer-term project. Lomas's Champions League return is a reason to keep him involved, not write him off after seven league appearances that were all from the bench.

With the updated rule, I'd make 'revenge targets your most profitable property' visible alongside the grudges. Otherwise I could understand why they're angry and still fortify the street where I caused the grudge, rather than the one that's actually at risk.

Will 1.7.0 still load craft files and saves from the older Android version, and is there a supported way to move them to a new phone? Keeping those old creations would be a big part of bringing a long-running sandbox back.

I wouldn't move him out of a role that's worked for thirteen years just because 15 Finishing looks low. With the injuries and that contract, are you planning to rotate in his successor now, or give him another season as the clear first choice?

Did any of the prototype themes survive in the newer soundtrack, or did improving your composition make you want to start fresh?

Did the delivery demo let you try one of those upgrades, or mainly tease them? That difference would be interesting to test: one new route competing for the same driver could sell the next unlock better than a long preview of locked nodes.

The official 4.2.0 notes linked in the post list customizable on-screen controls for Android. That may help with the overlay layout, although I haven't tested the build and the notes don't clarify whether swipe-only controls are an option.

I'd keep the names fixed on the left and highlight the whole row when you hover a value. That would let you follow the orange buy-in cell back to the player without adding four more copies of the XI. I'd compare both layouts at laptop size, rather than judge only by how much empty space they leave.

If co-op is the main hook, I'd get one short level working with two players before calling it the demo. It doesn't need the full progression system, but it should let people experience the reason they'd play together. An earlier solo build could still be useful as a clearly labelled mechanics playtest.

The 'I just wanted to write the music' to 'now we're shipping an action RPG' escalation made me smile. Has writing for actual combat changed the soundtrack much from what you imagined at the start?

I'd add a quick recall test before spending on a creative: show it to someone once, then ask what they'd type into search to find the game. If they can describe the gameplay but can't name it, the ad still has a problem even if the title technically appears somewhere. That's a separate check from whether they'd click.

Thanks for pulling both cuts, especially the sample sizes. With only 44 and 28 launches in the fresh-snapshot groups, I'd be wary of treating their higher medians as a correction factor for the older counts. Keeping the launch-week snapshots sounds like the right way to tighten this up.

Does it count walks with the screen off, or does the game need to stay open? I'd want to put the phone away while walking and check what grew when I got home.

If the contest allows private testing, I'd use the same short level for everyone and ask for a recording of their first ten minutes, without walking them through it. The most useful moment for your game sounds like the first big fall: do they understand why it happened and immediately retry, or get lost and quit? Someone who finishes the test without finding a bug can still give you valuable feedback.