Bite By Night, the Roblox asymmetrical horror game built in the mold of FNAF, Forsaken, and Dead by Daylight, has been offline far longer than it was ever playable. What began as a routine maintenance window has now collided with a wave of departures from the people who built the game, and several of them have gone public with claims of unpaid work.
Quick answer: Bite By Night is still shut down and cannot be joined. Multiple developers — Lukasz, ZoCarp, Aerozity, and Bea — have resigned, and no official return date exists. You can confirm the game is still down by opening the Bite by Night Roblox page, where the play button drops you into the maintenance state instead of a server.
Which Bite By Night developers resigned
Four names account for the bulk of the exodus. Each posted their own resignation publicly rather than through the game’s official channels, and two of them said they would release the work they had already finished on YouTube instead of holding it back for an update that may never ship.
| Developer | What they said |
|---|---|
| Lukasz (@LukaszBorges) | Resigned citing poor management, lack of communication, and the team not being paid. |
| ZoCarp (@ZoCarp) | Announced an official resignation and plans to upload their finished work to YouTube. |
| Aerozity (@Aerozity) | Left the development team and said their music tracks would go up on YouTube. |
| Bea (@coffbea) | Published a document detailing management problems and claiming more than $3,000 in unpaid wages. |
The pattern the community noticed first was the music. Puppet-themed tracks and a Beartrap theme began appearing publicly before anyone announced anything, which is usually a sign that composers are cutting their work loose from a project rather than saving it for a launch.
The payment dispute over the $3,000 claim
Bea’s document is the most concrete part of the fallout. It lays out her account of how the project was managed and states that Bite By Night’s management still owes her over $3,000 for completed work. Lukasz’s resignation points at the same underlying issue, describing a team that was neither kept informed nor paid.
Management’s position, delivered earlier through a written statement about the game’s former PR manager, is that the payments were final and the matter was closed. The two accounts do not line up, and nothing has been produced publicly that settles which version holds.
Note: These are competing public claims between individuals, not a resolved dispute. Treat the dollar figure as one side’s stated total.
How long the maintenance has actually run
The shutdown passed the 100-day mark and has now outlasted the period the game spent publicly playable. By mid-August 2026, players on the wiki were counting four months without access, and the tone of the discussion had shifted from waiting to writing the game off entirely.
That length is unusual even by Roblox standards. Long maintenance windows on live games are typically measured in hours or days, and a multi-month closure with no patch, no test build, and no firm reopening target is closer to a shutdown than a repair.
What the developers said before the resignations
Communication was thin throughout. A Discord message from Ozel apologised for the delay and said matters were being handled behind the scenes for the game’s future, without naming what those matters were. At other points the team said outright that they could not discuss the maintenance at all.
The silence reached the volunteers as well. A member of the wiki team posted publicly that they had no contact with the developers either, that their group chat had gone quiet, and that the wiki’s lack of updates came down to miscommunication rather than neglect. That post also warned readers not to direct anger at the developers.
Signs of backend activity in August 2026
The game was not completely abandoned during the closure. On Sunday, August 23, 2026, four separate “Last Updated Changed” entries were logged on the game within a 14-minute span, and a single new visit was recorded that same day at 6:20 AM — consistent with a developer or tester entering the closed place.
Edits like these confirm someone was touching the game files. They do not indicate progress toward a release, and they carry no date attached. In practice, a burst of place updates followed by continued silence tells you the project was still open on someone’s screen, nothing more.
Status of the Puppet update
The Puppet update — the one the game’s page still teases with its Marionette title tag — was delayed repeatedly, had its release day moved more than once, and ended up with no scheduled date at all. It became the standing explanation for why the game stayed down, which is exactly what frustrated players who wanted the servers reopened first and the new killer shipped later.
With the composers behind the Puppet’s themes now out of the project and releasing that music independently, the update as it was pitched is not in a position to arrive on schedule. No new release window has been given.
How to check whether Bite By Night is back
What has not been confirmed
No official cancellation has been announced. Equally, no return date, no reopening window, and no revised plan for the Puppet content have been confirmed. Community members describing the game as dead are drawing a conclusion from the resignations and the length of the closure, not repeating a statement from the team.
What is confirmed is narrower and harder to walk back. Key contributors have left, at least one of them says she is owed money, management says the payments are settled, and the servers remain closed. Until someone with access to the place either reopens it or says plainly that it is over, that is where things stand.
