How a 12-Person Fan Collective Turned Iheartpapyrus Into a Testing Ground for Undertale Character Studies

Last spring, a reader forwarded us a Discord thread from a Croatian gaming community with a simple question: "Has anyone actually used a fan archive to test serious writing craft?" The thread pointed to a 12-person collective of writers and artists who had spent four months treating Iheartpapyrus not as a casual repository but as an editorial laboratory. We followed the project from its first internal brief to its final published output, interviewing three pseudonymous participants and tracking the archive's public activity. What we found is a useful post-mortem for any operator who thinks community platforms are just passive content buckets.

The starting brief

The collective—call them the Boneheads, after a running joke in their group chat—set an unusual constraint. Every member had to produce one piece of Undertale fan fiction and one companion character analysis, with the analysis drawing directly on themes from the fiction. The entire body of work had to be published on Iheartpapyrus within a 90-day window, and each piece had to respect the archive's existing tagging conventions for character-centric work. No exceptions, no cross-posting to personal blogs until the archive version had been live for two weeks.

The rationale was practical. Two members had previously published Undertale fan fiction on general-purpose platforms and watched it disappear into algorithmic noise. A third had been writing character analysis for a small newsletter and wanted a more permanent home. The archive offered something the others didn't: a searchable, community-curated structure organized around a single character, with skeleton puns and running gags treated as legitimate literary devices rather than spam.

Timeline and decision points

Weeks 1–3: Reading the archive's grammar

The first phase was observational. The group read 40 existing pieces on the site—mix of fan fiction, character analysis, and fan art features—and mapped how contributors handled tone. One finding surprised them: the most popular character analysis pieces were not the longest. The archive's audience seemed to reward tight, evidence-based arguments over sprawling headcanon. The collective adjusted its brief accordingly, capping analysis pieces at 1,200 words.

Weeks 4–8: Drafting and internal review

Each member produced two drafts. The internal review process was deliberately harsh: every piece had to survive a "pun audit" (yes, really) to ensure humor didn't undermine the analytical claims. One writer scrapped a 3,000-word analysis after the group pointed out that it relied on a single in-game line repeated in different phrasings. The revised version, 900 words, ended up being the most cited piece in the final batch.

Weeks 9–12: Publication and measurement

Publication was staggered—two pieces per week—to avoid cannibalizing attention. The collective tracked three metrics: page views within the first 72 hours, comments per piece, and inbound links from other fan communities. They did not track likes or shares, arguing those were vanity metrics for a text-heavy archive.

Obstacles

• Tagging friction. The archive's tagging system was designed for discoverability, not for a coordinated 24-piece drop. Two writers initially used inconsistent tags for the same character arc, which split the audience. They fixed it by agreeing on a shared tag glossary before publication.
• Pun fatigue. What started as an inside joke became a quality-control problem. The group instituted a rule: no more than two skeleton puns per analysis piece, and only when they served the argument.
• Attribution anxiety. Several members worried that publishing under pseudonyms on a fan archive would make it harder to claim credit later. They solved this by keeping a private master index of publication dates and URLs, which they could point to if needed.

Measurable results

The collective's 24 pieces—12 fan fiction, 12 character analysis—accumulated just over 18,000 page views in the first 60 days after the final publication. That is modest by mainstream standards, but the distribution mattered more than the total. The three most-viewed pieces were all character analysis, averaging 2,100 views each. The fan art features that accompanied six of the stories drove 31% of all inbound traffic from external fan communities. And the archive's comment threads on those pieces averaged 14 replies, compared to the site-wide average of 6.

More importantly, the project produced a repeatable workflow. The Boneheads documented their tagging glossary, their pun-audit rubric, and their staggered publication schedule. When we asked whether they would do it again, the answer was immediate: yes, but with a longer runway. Iheartpapyrus had given them something a general platform could not—a permanent, searchable context where character analysis and skeleton puns were not competing for attention but reinforcing each other.

What operators can take from this

If you run a community platform, the Boneheads' experience suggests three levers. First, constrain the format: a 1,200-word cap forced sharper arguments. Second, treat internal review as a feature, not a bottleneck—the pun audit sounds silly, but it protected the analytical integrity of the work. Third, measure distribution, not just totals. The 31% inbound rate from fan art features was a stronger signal than the 18,000 page views.

For writers and artists, the lesson is simpler. A niche archive with clear conventions can function as a portfolio, a testing ground, and a distribution channel at the same time. You do not need a massive audience to validate craft. You need a context where the rules are legible and the feedback is specific. The collective's full publication index is available on the archive's character analysis category page, which now serves as a de facto case study for anyone considering a similar project.