Publishing and launch support
Publishing Built Around the Launch Window
A multiplayer launch is a ninety-day window, starting before the store page goes live and continuing after launch day. Marvelous Foundry LLC plans distribution, launch strategy, community groundwork, and live operations as one working schedule.
A practical fit for independent teams with a multiplayer build in hand and a target launch window to discuss.
-
What a Publishing Partner Does
Each workstream has a named output. Select a pillar to see where it fits in the plan.
Production planning
A milestone plan tied to build readiness, dependencies, and platform review dates.
Platform distribution
A storefront checklist covering page assets, metadata, pricing, and certification timing.
Launch strategy
A rollout sequence with responsibilities, review points, and a first-patch plan.
Player acquisition
Audience priorities and a measurable plan for bringing the right players to the lobby.
Creator partnerships
A contact schedule, briefing notes, and clear expectations for creator outreach.
Monetization planning
A cosmetic-first model and storefront language prepared for review before launch.
-
The Ninety-Day Launch Sequence
The calendar follows build readiness and certification windows. Open each phase for the work it covers.
Before launch Groundwork and readiness
Work begins before the store page goes live. Dates stay tied to the platform review schedule.
- Prepare the store page, metadata, and pricing
- Schedule certification against build milestones
- Start creator outreach and briefing
- Set up community spaces and moderation cover
Launch week Rollout and live monitoring
Keep the rollout pace manageable and give the team a clear view of player reports.
- Coordinate platform availability and announcements
- Monitor server health, onboarding, and support themes
- Set the first patch cadence from observed issues
Days 1–90 Season one and live operations
The launch team stays involved as the first season moves into regular operations.
- Publish an update calendar with the studio
- Review player feedback and service signals
- Plan season-one content and operational handoffs
-
Fill the Lobby Before Day One
Creator outreach works when it is scheduled around playable builds and a clear audience fit. Start early.
We plan creator contact weeks ahead, with briefing material and a realistic reply window. The goal is a prepared community and active onboarding, not a sudden burst of attention.
That means setting up community spaces, assigning moderation coverage, writing onboarding copy, and preparing a first-week event plan. Friend-invite prompts are clear about what they do and contain no promotional reward mechanics.
See how we support player communitiesTimingScheduled workWeek −6Confirm creator fit, outreach list, and the build available for review.
Week −4Send briefings, open community channels, and prepare moderation guidance.
Week −1Share launch details, test onboarding, and confirm first-week event coverage.
Day oneKeep community support staffed and route recurring issues to the team.
-
Monetization That Survives Review
Plan the business model with the storefront and the season calendar in view. Plain disclosure matters.
We start with cosmetic-first purchases and explain what each item includes. Pricing and currency display are checked against U.S. storefront conventions before the page is ready for review.
Season content is agreed before launch, so the live-operations calendar has dates and owners. Bonus progression and ranked-ladder plans are reviewed alongside that schedule.
Review our live-service approachCosmetic items
Use clear item descriptions and visible prices. Players should know what they are buying before they confirm.
Season content
Set the content scope, dates, and progression terms before launch; publish the schedule in plain language.
Bonus progression
Document the progression rules and how rewards are earned before they appear in the live plan.
Ranked ladder
Agree on season timing and competitive rules with the studio, then align updates to the published calendar.
-
What We Need From a Partner
A useful first conversation starts with enough detail to assess the build and the timing. Be direct.
- A playable multiplayer build
- A defined target platform set
- A realistic launch window
- A named technical contact
This is a poor fit for projects without a playable build, or teams looking only for a one-time promotional push. We stay involved through launch planning and live operations.
Start With a Build and a Window
The first conversation is technical: we’ll review positioning, platform sequence, and whether the live-operations plan fits your team.