I design and operate player communities for indie games — from Discord architecture and feedback systems to localization, international communication, and creator outreach.
Communities are systems, not chat rooms. I build the infrastructure that helps players communicate comfortably, give useful feedback, and stay engaged throughout a game’s lifecycle.
Built from a minimal starting structure and developed independently: permissions, categories, staff/public separation, forums, Ticket Tool support, scalable navigation, verification, AutoMod, and structured access. I adapt the architecture to each server rather than applying a fixed template.
Example: Built the entire Discord ecosystem for Money Under The Bed.
Clear onboarding flows with email verification, CAPTCHA, rules acceptance, role architecture, and progression systems built around the project’s identity. Personal welcomes and lightweight orientation help new members find their place without overwhelming them.
Example: 30+ roles across a 35-level progression system.
Structured suggestions with category and status tags, direct bug reporting, and monitoring of Steam reviews, community sentiment, and emerging issues — turning scattered player feedback into information that can be reviewed and acted on.
A persistent system of spaces, events, and recurring formats built around the game’s identity. Each one has its own purpose while remaining part of the same community world.
Examples: Resident Files · Evening Programme · Community Board.
Game Info, rules, announcements, and reusable reference material — built around the project’s visual language rather than generic templates. I keep the structure compact, clear, and easy to maintain.
Branded webhook systems with project-specific visual hierarchy, carefully matched colors, and embedded links. Communication design is part of the community experience.
I developed a persistent community framework built around The Building — a fictional shared space where events, activities, and community contributions become part of the same world. Rather than treating events as isolated announcements, each format has its own place, visual language, and purpose within the setting.
The Building began with a simple idea: community members could become residents. In Resident Files, participants create their own apartments and introduce themselves through their interests, stories, creativity, and anything else they want their neighbours to know.
There is no rigid questionnaire or required format. The structure gives people a place to start, while the open-ended format lets each resident shape their own presence.
“This is your apartment. This is your story.”
The format turns onboarding into participation: residents open their doors, meet their neighbours, and leave something of themselves inside the Building.
The framework is designed to grow. New formats can occupy different parts of the same world while keeping a shared visual and narrative identity.
A recurring creator showcase styled like an old television broadcast, with a recurring character and presentation that reinforce the project’s psychological horror atmosphere.
A fan-art feature styled as a corkboard of found material. I source submissions, prepare them for presentation, request permission, credit artists, and integrate links without disrupting the lore presentation.
Connecting players, developers, and the outside world. I work across localization, creator relations, and multilingual communication while helping reduce operational risks around public-facing projects.
Community and narrative localization into Russian, using a shared multilingual table, Google Sheets and PO-based workflows, terminology management, tags and placeholders, and multi-stage proofreading.
Workflow: Chinese source + English reference + Russian draft, MTPE, detailed proofreading, in-game verification, and final correction.
Research-led outreach across VTubers, creators, press, and publishers — with 100+ individually researched contacts across different audience and language segments. I identify relevant contacts and angles, then position each pitch around the recipient instead of relying on a generic template.
WORKFLOW: Research → qualification → recipient-specific positioning → localized pitch → status tracking → follow-up.
Publishers: Business correspondence may extend to rights, revenue sharing, and funding models.
Adapting language, presentation, and communication style for different international audiences and platforms — including creator-specific tone, press etiquette, and market-specific conventions such as Japanese keigo and Korean professional forms of address.
Monitoring the use of project assets and public-facing materials for leaks, unclear permissions, and guideline violations. When something is ambiguous or potentially sensitive, I document the risk and escalate it to the developer or rights holder rather than making assumptions on their behalf.
Monitoring Steam reviews, community sentiment, and emerging issues so communication risks can be identified, documented, and escalated early. Priorities are based on urgency: sensitive or time-critical issues first, routine feedback later.
Professional communication with developers, creators, press, localization contributors, publishers, and other external partners — with the developer kept informed on important decisions, risks, and opportunities while routine work stays off their desk.
Built a localization workflow around a shared multilingual table, terminology tracking, spreadsheet/PO work, and four-stage review: draft refinement, detailed proofreading, in-game verification, and final correction.
Built a research-led outreach workflow across 100+ targeted contacts in creator, VTuber, press, and publishing segments: target discovery, qualification, recipient-specific positioning, localized communication, status tracking, follow-up, and publisher-facing business correspondence when relevant.
Built the Discord ecosystem from scratch: permissions, tickets, forums, verification, 30+ roles, and a 35-level progression system.
Established The Building as a persistent community world, starting with Resident Files and expanding it with recurring in-universe spaces, events, and visual formats.
Developed the founding Building format into a reusable community framework: apartments, resident roles, an open-ended introduction format, and a structure designed to return with new waves of players.
Psychological horror RPG · Community Manager
A psychological horror RPG built around a jar of money that appears under the player’s bed. I built and run the community layer around the project: Discord architecture, onboarding, progression, feedback, documentation, localization coordination, and international outreach.
Updated as the project progresses.
Project total, reported by the developer. Community work and outreach supported the project as it grew.
Money Under The Bed demo · 152 Steam reviews at the time of this portfolio version.
I work across community structure, player communication, and the operational layer connecting a game with its wider audience.