Why a 65,000-Name Credits Promise Exposed Game Development's Crediting Mess

The "6 designers, 3 programmers, 65 people" game credits story took off because it looked funny: a tiny indie team asked social media for extra names to pad out its ending credits, then got flooded with responses. But the joke only worked because game credits are still governed mostly by studio habit, not binding rules. Once you look past the meme, the episode says more about missing standards, unreadable credit rolls, and career proof for laid-off developers than it does about one viral tweet.

ConnectedShadowGames, the studio behind Twilight Moonflower, posted that it needed about 100 names to fill out its credits footage. The response snowballed. The studio later wrote: "Thank you to all 64,901 applicants. We are men of our word. We swear to ensure every single one of you makes it into the ending credits."

That turned a throwaway social post into a public promise with a hard implementation problem.

What made this blow up

Most summaries stopped at the punchline: small team, huge credits list, internet chaos. The more interesting part is the team shape that made the original ask feel plausible. A credits page showing a small core crew with six designers, three programmers, and 65 total credited people already raises a familiar question for anyone who has worked around games: who counts as part of the team, who counts as support, and what exactly does each label mean?

In games, those answers are often inconsistent from one studio to the next. One company may list contractors alongside full-time staff. Another may put outsourced art houses under a single vendor heading. Another may move short-term contributors into "Additional" roles or "Special Thanks." So when readers saw a compact core team and then watched the credits promise balloon into tens of thousands of names, the stunt exposed a system that was already fuzzy.

Film has rules. Games mostly have customs.

Film and television credits are shaped by union and guild agreements. The Writers Guild of America, SAG-AFTRA, and the Directors Guild of America all have rules around credit eligibility, ordering, disputes, and arbitration. If a studio gets a major credit wrong, there is a process.

Games do not have an equivalent industry-wide system with the same force.

The International Game Developers Association has published crediting recommendations, but they are recommendations. They are useful, often sensible, and widely cited, but they are not enforceable across the industry. A studio can follow them closely, ignore them entirely, or borrow only the parts it likes.

That means a credit such as "Design," "Additional Design," or "Special Thanks" can carry very different meanings depending on the project. According to the IGDA Game Crediting Guidelines 10.1, studios are encouraged to credit anyone with at least 30 days of contribution and to use clearer rules for attribution. But because those guidelines are voluntary, they do not settle disputes by themselves.

That gap matters because credits are not just ceremonial. For many developers, especially after layoffs, a shipped-game credit is public evidence that they worked on a product.

Why 64,901 names create a real production problem

The studio did not say it would build a new credits system around the response. Reportedly, it said it needed names to fill the duration of existing credits footage. That detail matters.

If the credits sequence is fixed length, then every extra name has to fit into the same runtime. At normal credit speeds and readable text sizes, that breaks quickly.

A rough calculation shows why. If one screen can display 40 to 60 names legibly and each screen stays up for two seconds, 64,901 names would require well over half an hour even in chunked pages. A traditional vertical scroll at readable size could run much longer. The exact duration depends on font size, line spacing, platform resolution, and whether names are grouped in columns, but the basic constraint is obvious: there is no clean way to show that many names in a normal ending roll without making them too small or too fast to read.

That leaves only a few realistic options:

• Make the text tiny enough that inclusion becomes technically true but practically useless.
• Break from the original idea and move the names to a website or external credits page.
• Build an in-game searchable credits interface instead of a simple roll.
• Split the presentation: a standard ending roll plus a separate giant archive.

Any of those can work. None is the same as a normal ending credits sequence.

As of the events discussed here, the studio had not publicly detailed which implementation it would use.

Why this matters more than one joke tweet

The reason this story stuck is that game credits already carry career stakes far beyond audience curiosity.

From 2023 through 2025, the game industry saw mass layoffs across publishers and studios. Reported totals varied by tracker, but industry-wide counts easily passed 10,000 lost jobs during that period. In that environment, credits become one of the few durable, public records of contribution that survive after layoffs, contract work, or studio closure.

So when the system for assigning credits is inconsistent, the harm is not abstract.

A developer who shipped a feature may get listed as "Additional Programming" at one company and "Programmer" at another. Someone who worked for months may be omitted because they left before ship. Someone else may appear in "Special Thanks" for a minor favor. Readers outside the industry may not notice the difference. Hiring managers and peers often do.

That is why the meme version of this story misses the real point. If a studio can promise credits to tens of thousands of social media respondents while the industry still struggles to credit actual workers consistently, the problem is not internet culture. The problem is that credits still lack shared rules with teeth.

The oddity isn't a small team. It's what the credits are being asked to do.

A compact team structure is not unusual. Many indie projects rely on a small internal group plus contractors, outsourcing partners, middleware, composers, QA support, localization vendors, and friends thanked at the end. A credits list can easily outrun the headcount of full-time staff.

What's unusual here is the scale jump.

A game that starts with a recognizable indie ratio, such as six designers, three programmers, and a broader credited list of 65 people, is still within the range of normal modern production once you include support roles. Jumping from dozens to 64,901 is different. At that point, the credits stop functioning mainly as production record and start functioning as spectacle.

That shift creates a trust problem. A credit list is supposed to answer a basic historical question: who made this thing? Once credits become a viral participation mechanic, the record gets noisier.

The standards problem has been documented for years

This is not a brand-new complaint created by one viral post.

The IGDA has argued for years that game credits should be more standardized and more inclusive of contributors who are often left off. Developers have also discussed the ambiguity publicly in forums, postmortems, and hiring circles for a long time. One recurring point is that labels such as "Additional" are not self-explanatory. They sound precise, but in practice they may only reflect internal studio policy.

The result is a system where the same title can imply very different levels of work.

That weakens credits in three ways:

1. As labor history: outsiders cannot easily tell who did what.
2. As hiring proof: candidates cannot assume one studio's title maps cleanly to another's.
3. As public recognition: meaningful contribution can be buried under inconsistent labels.

The viral credits promise did not create these weaknesses. It made them visible to people who usually ignore credits entirely.

Could a studio still keep the promise?

Possibly, but only by redefining what "in the ending credits" means.

A searchable database inside the game is the most defensible solution if the goal is genuine inclusion. It lets players find names, supports large datasets, and avoids a five-hour scroll. But it requires interface work, input handling, testing, font support, and likely platform-specific QA. For a small studio, that is not free.

A web page is easier, but weaker. It solves the scale issue and can include every name, yet it does not satisfy the common-sense reading of an ending credits promise.

A hyper-compressed roll is the cheapest route, but also the least credible. If names flash past in microscopic text, inclusion becomes ceremonial rather than readable.

So yes, the promise might be fulfilled in some form. The problem is that each implementation changes the meaning of the original claim.

What developers should actually take from this

If you run a studio, this episode is a warning about casual public promises and sloppy credit policy.

Before you turn credits into a community stunt, answer these questions first:

• What is your written rule for who receives a standard production credit?
• How do you label contractors, vendors, short-term contributors, and community participants?
• If your credits UI has a display limit, what is it on your target platform?
• Are names stored as plain text, localized strings, or a searchable data structure?
• If you promise inclusion publicly, what exact format are you promising?

Those are not legal niceties. They are production questions.

They also matter for teams using AI tools in asset generation, writing assistance, code support, or localization workflows. Credits policy gets murkier when outputs are shaped by a mix of staff, contractors, and machine-assisted processes. Current game-crediting guidance does not fully resolve those edge cases either, which means studios need their own clear internal rules before release.

Pricing and public availability

This article is about a crediting controversy, not a software product comparison, but pricing references still need to be concrete.

As of the events described here, Twilight Moonflower did not have a publicly listed launch price. The IGDA crediting guidelines are publicly available at no cost. MobyGames can be browsed publicly, though its contributor and account features vary by service terms rather than a consumer-style software subscription.

Questions readers usually ask

Are game credits legally standardized?

No, not across the industry. Film and TV have stronger crediting structures through guild and union agreements. Games have guidance, most notably from the IGDA, but not a single binding cross-industry enforcement system.

Does "Additional Programming" have a fixed meaning?

No. According to industry discussions and the voluntary IGDA framework, it may indicate a smaller or shorter contribution, but studios do not all apply the label the same way.

Is it actually possible to show 65,000 names in-game?

Yes, technically. The hard part is doing it in a way that is readable and faithful to what people think an ending credit should be. A database, segmented list, or external archive can handle the volume better than a standard scroll.

Why did this story resonate so much?

One explanation is timing. In a period marked by layoffs and disputes over who gets credited, a viral promise to hand out tens of thousands of credits landed on a raw nerve.

What this story proves

The real lesson from the "6 designers, 3 programmers, 65 people" game credits saga is not that indie studios should stop joking online. It is that game credits are doing too many jobs at once: historical record, professional proof, public thank-you, and now social media marketing hook. Without enforceable standards, those uses collide. That is why a silly request for extra names turned into a case study in trust, labor recognition, and implementation reality. Until studios adopt clearer internal rules, and the industry treats credits as more than decoration, the next viral credits stunt will expose the same weakness all over again.