Short version: the channel worked and the game did not retain a single person. Here is the autopsy, because the numbers turned out to be more specific than I expected.
The game is a shared 256x256 pixel canvas where an AI adversary erases what people paint. Free, browser, no account. Two posts, one in a pixel art community and one in a web games community, brought 150 arrivals, 38 sessions and 23 people who actually painted. That is more than the project had seen in its entire life. Of those 23, one came back to look and zero painted on a second day.
What the sessions looked like:
- 18 of 23 lasted two minutes or less. Median time from first pixel to last: 41 seconds.
- Median 19 pixels painted. 9 of 23 spent all 30 charges (the bucket refills one charge every 30 seconds).
- In 14 of 23, most of their cells were cells taken back from the adversary. They were not decorating, they were fighting her.
- In 18 of 23 she erased cells while the player was still there, and between 126 and 423 more in the 25 minutes after they left.
- Nobody used undo. Zero comments on either post.
What I read from that: the first session is 30 pixels long, it ends when the charges end, and nothing happens at that moment. No closure, no name, no reason to come back. The adversary was already reacting to them, but she is forbidden from touching any pixel younger than 72 hours, so her answer always landed somewhere they were not looking.
What shipped since, in two passes.
First, making her legible in the first minute:
- When your bucket hits zero she speaks to you, by name, once in your life. The zero stops being a bare number and becomes a state with a countdown.
- Her answer to the cells you took back travels signed, so you can tell it was aimed at you.
- The identity prompt stopped interrupting the burst.
- Her blitz finally respects the 72 hour protection on young pixels, which the code promised in writing and did not do. That single bug had eaten 238 of the 403 cells that cohort painted.
- Instrumentation for the whole first session, so the next wave is measured instead of guessed.
Then, a deeper problem: subtraction is invisible. Nobody notices what is no longer there. A tower sixteen storeys tall, which costs 24 charges of attention, vanished in one hit that cost her exactly what a flat pixel costs. So:
- Height is now resistance. One hit takes one storey off a tower; only a flat light goes out in a single blow. A first session is still as fragile as it was, because nobody builds storeys in their first minute, but what you invested in now holds.
- And she does not only erase, she converts: every storey she takes she raises as her own cold cube in the void cell beside it, and the ring of a siege now rises a storey, so you watch the cage close around a work before the blow lands. Her towers fall in one pixel when you reclaim the cell. Hers is brittle, yours is stubborn.
- And the welcome screen stopped being eight paragraphs nobody read. It is now a four step animation that shows how to build, what her hit does and how to take a cell back, with one line of text under it.
This post is part of the second wave. The success criterion was written down before publishing so I cannot move it afterwards: at least one in five of the people who reach zero charges spends a second batch, and at least 3 of the new painters paint again within 72 hours. Baseline is 0 and 0.
The thing itself, if you want to look: https://ultimaluz.com/r/lemmy-gamedev
One critique I would genuinely like: is a hostile adversary the wrong shape for a first session, or is the shape fine and what was missing is an ending?
Hello Tower, I will try to create a page where the mechanics of it, the machine, are clearly explained. Now I try to explain it here: She thinks every 10 seconds. She is reconquering based on a budget, but it is enhanced if people draw more. Every 15m the LLM chooses a larger target to turn off its lights. She advances along her border but if a player reconquers she can go after him with more determination. It must be taken into account that a painted light has a protection of 72 hours, only a declared fence can with it. I hope I have explained a little more to you. Anyway, I'm going to try to implement that more clearly in the game. If you have any more questions, tell me and I'll answer you.