Fart Together’s pre-release clone complaint raises a practical question: how do players reach the game they meant to play, and who should make that easier?
Hello there, co-op chaos enthusiasts, indie-game explorers, and everyone who has convinced three friends to download something before checking whether they found the same thing.
A funny clip can sell a game’s appeal in seconds. Identifying the people behind it sometimes takes considerably longer.
Fart Together makes that mismatch worth examining. GamesMrkt’s game puts two to four players on a shared raft powered by precisely what the title suggests. Its developer has publicly complained about near-identical copies appearing before the main game launches. Meanwhile, players searching for the title can encounter listings bearing a different developer’s name.
We wanted to follow the useful question underneath the argument: when a game catches our attention, how do we make sure our next click reaches its creators?
🦊 Kiki: “I can accept that a game about coordinated hippo farts might test my judgment. That is part of the entertainment contract. What irritates me is needing a background check before I can arrange a stupid evening with my friends. I saw the raft. I liked the raft. Now I would quite like to find the people who made the raft. Surely the industry can manage that little introduction before presenting the enormous download button. We have made purchasing wonderfully convenient. I would appreciate putting a little of that enthusiasm into helping me understand what I am purchasing.”
🍪 Chip hovers beside Kiki with four tiny controllers, then pauses to compare the names on two store pages.
The demo is available and the main release is still coming
First, the status matters. As of our November 3 check, Fart Together’s main Steam page identifies GamesMrkt as both developer and publisher and lists the game as coming soon. The free Steam demo was released on October 8 and lists Windows requirements.
On October 26, GamesMrkt reported passing 70,000 Steam wishlists and more than 4,500 simultaneous demo players. Those are the studio’s figures. On October 29, it announced a launch delay, saying the build submitted on October 20 was still awaiting Steam approval. Both statements remain available in its official Steam announcements.
Separately, GamesMrkt developer Emrah İşlek complained on LinkedIn about numerous near-identical copies of a game he said had been revealed roughly a month earlier. He questioned how those copies passed review while developers faced repeated revisions.
That establishes his complaint. It does not establish how every competing app was made, what permissions its publisher holds, or what a platform reviewed. Nor does the Steam delay explain the decisions of a different store.
🦊 Kiki: “Imagine finally getting people excited about your small game, then discovering that part of your launch job is explaining which game is yours. Delightful. The marketing campaign now comes with unpaid identity administration. And no, I do not need a courtroom verdict to understand why that would drive a developer up the wall. I do need evidence before accusing a particular app of stealing anything. Both thoughts fit in my head, sweetheart. We can take the developer’s frustration seriously without promoting every angry sentence into an established fact. That would only give everyone another mess to clean up.”
🍪 Chip floats between a launch checklist and a magnifying glass, reluctantly adding another sheet to the pile.
The same title does not establish the same developer
Here is a concrete distinction readers can check themselves.
The Steam listing names GamesMrkt. A Google Play listing also titled Fart Together names ALDAN and describes fart-powered boat movement, physics obstacles, and solo or cooperative play.
Those are statements visible on the storefronts. We have not independently tested that Android app’s advertised features or verified a commercial relationship between the listed developers.
A different publisher can legitimately handle a port. A developer may also operate under more than one business name. The useful response to a mismatch is therefore to look for confirmation from the original studio, rather than immediately declare fraud.
For this game, we can directly identify GamesMrkt’s Steam page and demo. A matching title elsewhere does not, by itself, establish that another listing is an official version.
The same principle applies to reviews. Feedback on one listing describes that product. Carrying its rating over to another game with the same name would mislead readers in either direction.
🦊 Kiki: “The title is how I find you. The developer name helps me work out who actually turned up. I would prefer those two pieces of information to remain friends. If there is an official port, fantastic: show me where the original studio announced it and let us get on with our evening. If that connection is unclear, I am allowed to pause. That does not make me a detective, a hater, or an enemy of indie development. It makes me someone who would like to spend her time on the intended game. Apparently that modest ambition now requires a research tab.”
🍪 Chip hovers over the matching titles, then slides a magnifying glass down to the developer names.
The stores already have rules about confusion
Google Play’s impersonation policy prohibits misleading users about an app’s relationship to another developer or product. It specifically addresses titles, icons, descriptions, and other elements that could create a false impression of affiliation.
Apple’s App Review Guidelines, section 4.1, address copycats and impersonation. They also prohibit using another developer’s icon, brand, or product name in an app’s icon or name without approval.
These policies provide relevant context. They are not findings that a particular Fart Together listing violated them.
Our editorial expectation is straightforward: stores should help players distinguish products, make developer identity easy to inspect, and investigate specific, documented complaints. Similarity can justify examination without automatically deciding its outcome.
That also means giving legitimate developers a fair way to explain an authorized relationship or challenge an incorrect decision. A process that simply removes everything resembling something popular would create its own problems.
🦊 Kiki: “A beautifully written policy is lovely. I am sure it looks magnificent in a presentation. I care about what happens when somebody brings you two listings and a reasonable question. Can they submit the evidence? Does someone examine it? Can the other developer respond? Does the player eventually get a clearer answer? Those are rather more useful features than a paragraph everyone can quote while nothing becomes easier to understand. I am not asking a store to ban every game featuring a boat and questionable life choices. I am asking it to care whether customers can tell whose boat they are boarding.”
🍪 Chip floats past a towering rulebook and points toward a small, unattended stack of reports.
A quick check before the download
Players should not have to audit an entire business. A few checks can still prevent an avoidable mix-up:
- Follow a link from the developer. Start with the studio’s established site or account, then use its store link. A familiar title in search results is a lead, not confirmation.
- Read the developer and publisher fields. If they differ from the studio you expected, look for an announcement explaining the relationship.
- Check the platform and release status. A playable PC demo does not establish that a mobile version or the main release is available.
- Compare the promised experience. Player count, online features, and supported devices matter more than a similar thumbnail.
- Share the exact store link with friends. “Download Fart Together” leaves more room for confusion than a direct link to the intended listing.
If the connection remains unclear, waiting is a reasonable choice. Reviews and download counts can help describe an app’s reception, but they do not establish authorization or identity.
For anyone wanting to try the GamesMrkt game covered here, the source-verified starting point is its Steam demo.
🦊 Kiki: “Please send your friends the actual link. We already have one person who cannot find the lobby, another updating their drivers, and someone announcing they will be ready in five minutes while apparently moving house. We do not need a fourth complication because everyone downloaded a different interpretation of the same title. And stop treating popularity like identification. A large crowd can tell me lots of people arrived. It cannot tell me I reached the place I intended. Check the name, follow the connection, and then enjoy the extremely serious business of arguing about whose fart ruined the turn.”
🍪 Chip hovers above the group chat, drops in one store link, and finally distributes the controllers.
Developers should make the right door obvious
Studios cannot control every search result, but they can make their own route easier to follow.
We would like to see one clearly maintained page linking every authorized release, with platform, developer or publishing partner, and current availability. Social profiles and promotional clips should point back to that page or directly to the relevant store.
When a game is attracting attention, a pinned clarification can answer practical questions: which demo is available, whether a mobile version has been announced, and which account provides release updates.
If a studio raises a complaint, specific listing URLs and clearly described similarities give platforms and reporters more to examine than a general accusation. Public statements should distinguish what the studio can demonstrate from what it suspects.
Publications and creators have a role too. We should link the product we cover, name its developer, date release information, and avoid turning an allegation into a stronger headline than the evidence supports.
🦊 Kiki: “Developers, help me give you the attention you worked for. Put the correct link where I can find it. Tell me which versions exist. If another company is publishing the port, introduce them instead of making me reconstruct your business relationship from three profiles and an abandoned announcement. I know you are busy making the game. That is precisely why the same question should not require your personal intervention two hundred times. And to everyone covering it: add the link. You had room for fourteen adjectives describing the chaos. You can spare a few words for the people who built it.”
🍪 Chip floats beside a messy web of arrows, gathers them into one clear route, and gestures toward the developer’s page.
Fart Together gives us an unusually silly setting for a serious discovery problem. Players should be able to follow their interest to the intended game. Developers deserve a clear opportunity to identify their work. Stores should make those connections easier to understand and investigate confusion when it is documented.
We can enjoy the ridiculous raft and still expect the journey to its download page to make sense.
🔎 Stay curious about who made the game that caught your attention.
🎮 Keep the official link handy when you bring your friends aboard.
🍪 Remember: finding the title is only the first step. Check the developer before you jump in.
🦊 Kiki · 🍪 Chip · ⭐ Byte · 🦁 Leo
Have you ever downloaded the wrong game after seeing a clip? We would love to hear what led you there.
Game Cookies | Gaming Trends, One Bite at a Time.
