A game delay is never good news. Even when players understand the reason, they were still looking forward to a particular date. Move that date and you remove a moment they had already built into their calendar.
For an early-access game, the communication problem is even harder. These players are not waiting outside the product. They are already inside it. They have paid, played, formed opinions and, in many cases, invested time in helping shape what the finished game should become.
So what do you say when your 1.0 launch needs more time?
Moon Studios has just provided a useful case study with No Rest for the Wicked. The studio moved the game’s full release from October 2026 to March 2027. The interesting part is not simply that the date changed. It is how the studio turned the delay into a new community narrative: what needs more work, when players can test it, how updates will continue and what early supporters can expect.
That does not make a delay painless. It does provide players with something better than a vague apology and a new date.
What happened with No Rest for the Wicked?
Moon Studios announced that No Rest for the Wicked’s version 1.0 launch would move from its previously planned October 2026 window to March 2027. The game entered Steam Early Access in April 2024 and remains available there while development continues.
In reporting by GamesIndustry.biz, Moon Studios described the game as close to completion but said that “close” was not sufficient for the full launch. The studio identified performance improvements, work on the class system and wider polish as reasons for taking the additional time.
The announcement also included a testing plan. Moon Studios said there would be more closed and open beta tests, with an open beta scheduled for December. The studio plans to continue sharing development information through its Wicked Inside video diaries.
The delay was paired with an extension to the Founders Pack eligibility window. According to Gematsu’s report, qualifying PC purchases made before January 1, 2027 will receive the rewards, and players who bought after the previous July deadline will be included retroactively. PlayStation pre-orders are planned for January 2027 and will also include the rewards.
The game has already built a substantial audience. GamesIndustry.biz reported that it had sold two million copies as of July 2026. That makes the communication challenge materially different from announcing a delay before anyone has played the game. Moon Studios was speaking to an established community with expectations, experience and a direct stake in the result.
A delay announcement has three audiences
It is tempting to treat a delay announcement as a message to prospective customers. For an early-access title, that is only one part of the job.
You are speaking to at least three groups:
- Existing players, who want to know what the delay means for the product they are playing now.
- Supporters and prospective buyers, who need a reason to keep trusting the project.
- The wider market, including press, creators and platform audiences, who will decide whether the announcement signals responsible development or trouble behind the scenes.
A single sentence rarely serves all three audiences. “We need more time to make the game better” may be true, but it leaves important questions unanswered.
What needs more time? What will players see before the new launch? How will the team use feedback? Does the current version continue to receive support? Has anything changed for people who already bought the game?
The strongest delay communications anticipate those questions before the community has to ask them repeatedly.
Explain the work, not just the emotion
Players do not need a studio to pretend that a delay is exciting. They need clarity.
Moon Studios connected the extra time to particular areas of work: performance, the class system and polish. That is more useful than describing the delay only as a commitment to quality. “Quality” is a conclusion. “We are using the extra time to improve performance and tighten the class system” gives the audience something concrete to understand.
This does not mean publishing an internal production plan or promising a feature-by-feature schedule that the team cannot maintain. It means explaining the decision at the level players can evaluate.
A useful delay message should answer:
- What is not ready yet?
- Why does it matter to the full-release experience?
- What is the team doing about it?
- What should players expect during the additional development period?
Be specific enough to build confidence. Be careful enough not to create a second set of promises that will become a problem later.
Replace the missing launch beat
A postponed launch creates a hole in the marketing calendar. If the only communication is the new date, the team loses the attention that would have surrounded the original launch window.
For an early-access game, that hole can be filled with meaningful participation rather than empty hype.
Moon Studios paired the delay with further testing and a December open beta. That gives players a reason to return before March and gives the studio a defined opportunity to demonstrate progress. The testing plan is not just a development activity. It is also a communications rhythm.
That distinction matters. A studio should not turn every development task into a marketing stunt. But if players can genuinely test an important part of the game and provide feedback, the event can serve both product development and community communication.
The key is to explain the role of the test honestly. Is it a preview? A feedback opportunity? A stress test? A chance to try a system that was not previously available? Players can accept an unfinished experience more readily when they understand what they are being invited to do.
Do not call players “partners” if their feedback disappears into a black hole. Participation creates value only when the team closes the loop.
Give supporters a reason to feel recognised
The extended Founders Pack window is another notable part of Moon Studios’ response. The studio did not simply move the date and leave existing buyers to interpret the consequences. It extended eligibility and included buyers who had purchased after the previous cutoff.
That is not a universal solution. Rewards can create their own problems if they feel manipulative, unfair or disconnected from the community’s concerns. A cosmetic item cannot compensate for poor communication or a product that does not improve.
But recognition can help when it is aligned with the history of the product. Early-access players took a chance on an unfinished game. A clearly explained founder benefit can acknowledge that support, particularly when the full release has moved further away.
The principle is more important than the specific reward: know what your existing players have already given you, and communicate what the delay means for them—not only what it means for your future launch campaign.
Keep the message in the places players already use
An early-access community should not have to hunt across six platforms to find the official explanation for a delay.
Publish the core message where the game is being played and discussed. That may include the Steam store or community hub, the official website, email, social channels and a video announcement. Each channel can have a different job, but the facts should remain consistent.
The Steam page for No Rest for the Wicked identifies the game as an Early Access action RPG from Moon Studios and provides the store context players need. For a game in this position, Steam is not merely a shop window. It is part of the product’s ongoing communication environment.
That does not mean every discussion belongs on Steam, or that a studio should abandon the channels where its community is most active. It does mean the official answer should be easy to find next to the place where players make purchase and support decisions.
My guide on building a game community beyond Discord makes a related point: community strategy should not depend entirely on one external platform. A delay is exactly the sort of moment when channel dependency becomes visible. If your most important players cannot find the announcement without joining a separate server, your communication plan has a weakness.
Do not overpromise the new date
A new date can reassure people. It can also create a new countdown clock.
If March 2027 is a target rather than an immovable commitment, say so in language that the audience can understand. The team should be confident enough to provide direction without presenting an uncertain estimate as an absolute guarantee.
This is one of the hardest parts of delay PR. Players want certainty, while development often produces information gradually. A studio that gives a date too early may have to repeat the same bad news. A studio that refuses to give any timeframe may appear to have no plan.
The answer is not perfect certainty. It is disciplined communication:
- explain the current target
- describe the remaining work at a useful level
- publish progress updates when there is something meaningful to report
- avoid turning every small milestone into a promise
- return to the community if the situation materially changes
Trust is not built by never changing a plan. It is built by making changes understandable.
What should you actually do if your game needs more time?
1. Prepare the player-facing explanation first
Before posting the announcement, list the questions existing players will ask. Include questions about current access, future testing, refunds or purchase benefits where relevant, platform versions and support during the delay.
If your team cannot answer a question yet, say that. “We are still confirming the console schedule” is more credible than an invented certainty.
2. Attach the delay to visible work
Name the broad areas the team will improve. Avoid technical detail for its own sake, but do not hide behind vague language about quality.
Players need to understand what the additional time is supposed to change.
3. Build a communications calendar for the extra runway
The postponed launch should not be the last time players hear from you. Plan the next meaningful beats: a development diary, a test, a progress update, a community Q&A or a new look at a system that is changing.
Each beat should have a purpose. More posts do not automatically create more confidence.
4. Close the feedback loop
If you invite testing, explain how feedback will be collected and when players can expect to hear what the team learned. You do not need to implement every request. You do need to show that participation was not decorative.
5. Recognise the people already invested
Consider what existing buyers, testers and community members have contributed. If you offer a reward or extend an eligibility window, explain the decision and apply it consistently.
6. Make one source of truth easy to find
Keep the date, reason, roadmap and key links together. Repeat the essential information across the channels your audience actually uses, but avoid creating contradictory versions of the announcement.
My guide on preparing for Steam Next Fest also highlights the value of being present in Steam conversations and responding to players where they are. The same principle applies during a delay: do not make the community do all the work of finding and interpreting your message.
A delay is a communications test
Moon Studios’ announcement is not proof that every delay should include a beta, a reward or a new video diary. Those choices make sense because No Rest for the Wicked is already in Early Access, has an established player base and is still being actively developed toward a 1.0 release.
The broader lesson is simpler.
A delay announcement should answer the audience’s next question, not just announce the date that disappeared.
What happened? What needs more work? What will happen next? How can players participate? What does this mean for the people who already supported the game?
If your message answers those questions with evidence and restraint, the delay can become more than an apology. It can become a clearer explanation of the product’s direction and a practical way to keep the community involved while the team finishes the work.
The new launch date matters. But during a delay, the quality of the communication between now and then matters just as much.
