The release of major software updates often brings enhanced features and stability, yet they can inadvertently introduce critical errors that disrupt user access. One such issue has surfaced regarding the game "Night of the Full Moon," specifically affecting the ability to sign in or launch the application following a recent patch. Users are reporting that the game becomes unresponsive at the start screen, preventing progression. This phenomenon is not merely a user error but stems from a programming mistake related to date fetching and potential archive damage within the local application data. By analyzing community reports and official troubleshooting methods, a clear pathway to resolution emerges. The core of the problem lies in a specific configuration file that retains corrupted data, which blocks the authentication process.
The community has identified that the inability to log in is often a symptom of a corrupted user data file. When the game attempts to read this file during the boot sequence, the corruption causes a hard freeze. The solution involves identifying the precise file path where this corruption resides and removing it, forcing the game to regenerate a fresh, clean configuration. This process effectively resets the local state without necessarily erasing global achievements, provided the server-side data remains intact. Understanding the mechanics of this failure and the exact steps to resolve it is essential for any player facing this barrier.
Understanding the Root Cause of the Boot Failure
The primary driver behind the inability to sign in to "Night of the Full Moon" is a flaw in the game's programming logic regarding date retrieval. Following the latest update, the game engine fails to fetch the current date correctly. This failure triggers a cascade of errors that prevent the application from completing its initialization sequence. The symptom manifests as the game getting stuck on the "Start" screen, a state where the user interface is visible but unresponsive to input. This is not a network connectivity issue but a local software logic error that halts the boot process.
In addition to the date-fetching error, a second critical factor has been identified: archive damage. When the game's local data archive becomes corrupted, the authentication module cannot verify the user's credentials or load the necessary session data. This corruption likely occurs during the update process or through a system crash during a save operation. The game attempts to read a damaged file, encounters an unreadable data structure, and halts execution. This dual failure mode—software logic error combined with file corruption—creates a deadlock for the user.
The specific file responsible for this issue is located within the user's application data directory. The game stores user-specific configuration and save data in a file named "UserinfoRecord." When this file is damaged, the game cannot proceed past the initial login prompt. The error message is rarely explicit; instead, the application simply stops responding, leaving the user stuck in a frozen state. This behavior confirms that the game's error handling is insufficient to gracefully report the corruption, leading to a silent failure.
Furthermore, the issue appears to be isolated to the local installation of the game rather than a server-side outage. This distinction is crucial because it shifts the resolution from a waiting game for a server fix to a user-side remediation. The user must intervene directly on their machine to clear the corrupted local data. The community consensus indicates that this is a known issue post-update, suggesting that the development team may have introduced a bug in the date-handling module, which interacts poorly with the user information file.
The Corrupted UserinfoRecord File and Its Path
To resolve the login freeze, one must locate and delete the specific file causing the blockage. The file is named "UserinfoRecord" and is stored in a deep directory within the Windows operating system. The exact path is: C:\Users\YourUserName\AppData\LocalLow\ztgame\月圆之夜\UserinfoRecord. This path points to the local application data folder where the game stores its persistent user information.
The location AppData\LocalLow is a standard Windows directory for applications that require lower security privileges or need to store user-specific settings. The folder ztgame\月圆之夜 indicates the game's specific installation directory for "Night of the Full Moon." Inside this directory, the UserinfoRecord file contains the cached user profile data. If this file is damaged, the game engine cannot initialize the user session, leading to the boot freeze.
Deleting this file does not result in the loss of global achievements. The game's achievement system is typically server-side, meaning the progress tracked by Steam or the game servers remains intact. However, local progress, such as specific save states or local configuration settings, will be reset. The game will generate a new UserinfoRecord file upon the next launch, effectively bypassing the corruption.
The following table outlines the critical file details and the impact of deletion:
| Attribute | Detail |
|---|---|
| File Name | UserinfoRecord |
| File Path | C:\Users\YourUserName\AppData\LocalLow\ztgame\月圆之夜\ |
| Cause of Issue | Archive damage or programming error in date fetching |
| Impact of Deletion | Local progress may be cleared, but achievements are preserved |
| Result | Resolves the "stuck at Start screen" issue |
It is important to note that the file name and path are specific to this title. Users must replace YourUserName with their actual Windows username to locate the file. The directory LocalLow is hidden by default in Windows, requiring users to enable the "Show Hidden Files" option in folder options or navigate directly using the Run dialog.
Step-by-Step Remediation Procedure
Resolving the login issue requires a precise, manual intervention on the user's machine. The process involves navigating the file system, locating the corrupted file, and removing it to allow the game to regenerate a clean data file. This procedure is the definitive fix for the post-update login freeze.
Step 1: Enable Hidden Folders
Before proceeding, ensure that hidden system files are visible. In Windows File Explorer, click on "View" in the menu bar and check the box for "Hidden items." This reveals the AppData folder, which is otherwise invisible. Without this step, the LocalLow directory will not appear, making the file inaccessible.
Step 2: Navigate to the Target Directory
Open the File Explorer and navigate to the following path:
C:\Users\YourUserName\AppData\LocalLow\ztgame\月圆之夜\
Replace YourUserName with the name of the user account currently logged into the Windows machine. If the AppData folder is not visible, the "Show Hidden Items" step above is mandatory.
Step 3: Identify and Delete the Corrupted File
Within the 月圆之夜 folder, locate the file named UserinfoRecord. This file is the source of the corruption. Right-click the file and select "Delete." If the system prompts for administrative permissions, confirm the action. It is critical to delete this file only; do not delete the entire ztgame or 月圆之夜 folder, as this would remove the game's local data entirely.
Step 4: Relaunch the Game
After deleting the file, restart the game through Steam. The application will detect the missing file, generate a fresh UserinfoRecord file, and proceed with the login process. The date-fetching error should no longer trigger a freeze because the new file contains clean data.
Step 5: Verify Functionality
Once the game launches successfully, verify that the "Start" screen is responsive and that the login process completes. If the game still freezes, it may indicate a deeper issue with the update's core code that requires a patch from the developers. However, in the vast majority of cases reported by the community, deleting the UserinfoRecord file resolves the issue immediately.
Analyzing the Impact on Progress and Achievements
A common concern for users facing this issue is the potential loss of in-game progress. It is vital to distinguish between local save data and server-side achievements. The UserinfoRecord file primarily stores local configuration and user session data. When this file is deleted and regenerated, the local save state—such as the specific point reached in the game or local settings—will be reset to the default state. This means that any unsaved progress made after the last successful save point within that session might be lost.
However, achievements in "Night of the Full Moon" are typically tied to the Steam account and are stored on the server side. Deleting the local UserinfoRecord file does not impact the global achievement list. Players who have unlocked achievements will retain them even after the file is cleared. This distinction is crucial for user reassurance.
The table below compares the impact of file deletion on different types of data:
| Data Type | Storage Location | Impact of Deleting UserinfoRecord |
|---|---|---|
| Local Save Progress | Local File System | Reset to default (Potential loss) |
| Achievements | Steam Server | No Impact (Retained) |
| Game Settings | Local File System | Reset to default values |
| Login Credentials | Server / Local Cache | Cleared (Re-authentication required) |
Users should be aware that if they have made significant progress that was not saved to the cloud or server, this progress will be lost upon regeneration of the file. Therefore, this fix is a trade-off: immediate access to the game versus the potential loss of local session data. For most users, regaining access is the priority, and the game's design ensures that the core achievement data remains safe.
Community Verification and Developer Feedback
The solution involving the deletion of the UserinfoRecord file has been validated by multiple community members. User reports confirm that the fix works immediately after the file is removed and the game is relaunched. However, there is also a note of caution: some users have reported that the file deletion did not resolve the issue in their specific cases, indicating that the problem might be more complex or related to the core update bug itself.
One community member, cq13845 (Vegta), reported that after contacting the official support, they were instructed to delete the specific document. This confirms that the fix is not just a user hack but an officially acknowledged remedy for archive damage. The user noted that while local progress might be cleared, the achievements remain safe.
Conversely, another user (goteki❥45) mentioned that they tried the suggestion but found it ineffective. This suggests that while the fix works for many, it may not address the underlying programming error regarding date fetching. If the date-fetching bug is hardcoded in the update, deleting the local file might not be enough if the game engine itself fails to process the date correctly regardless of the local file state.
The consensus in the community discussions highlights that the primary method is to clear the corrupted local data. The date-fetching issue is a known programming mistake that prevents the game from reading the system date correctly, which in turn corrupts the local record file. By removing the corrupted record, the game is forced to create a new one, potentially bypassing the date error if the error is strictly in the reading of the old file.
Technical Analysis of the Date Fetching Bug
The core technical failure identified in the community reports is a "mistake in programming that cannot fetch date correctly." This specific bug is the catalyst for the broader issue. When the game update fails to retrieve the system date, it likely causes an exception in the initialization sequence. This exception propagates to the file I/O layer, resulting in the UserinfoRecord file becoming unreadable or corrupted.
The mechanism appears to be a race condition or a logic error where the game expects a valid date to validate the session. If the date retrieval fails, the game attempts to write or read the UserinfoRecord file with invalid data, corrupting the archive. This corruption is what causes the game to freeze at the start screen. The fix of deleting the file works because it removes the corrupted data structure, allowing the game to start with a clean slate.
However, if the date-fetching bug is persistent in the game's code, simply deleting the file may only provide a temporary fix. If the game cannot fetch the date correctly on the subsequent launch, it might immediately corrupt the new UserinfoRecord file again, leading to a recurring issue. This suggests that a permanent resolution requires a patch from the developers to fix the date-fetching logic in the game engine. Until such a patch is released, the file deletion method is the only viable workaround for users.
The interaction between the date bug and the file corruption highlights the fragility of the game's update process. The update likely modified the initialization code, introducing a bug that interferes with the operating system's date handling. This type of error is common in rapid update cycles where edge cases regarding system date formats or time zones are not fully tested.
Broader Context of Game Updates and Stability
The "Night of the Full Moon" update that introduced this issue represents a common challenge in software development: the balance between adding features and maintaining stability. Updates often bring new content but can inadvertently introduce regression bugs. The specific case of the date-fetching error is a classic example of a regression bug where a change in the codebase broke an existing function.
For users, the lesson is that software updates can sometimes require manual intervention. The community-driven solution of deleting the UserinfoRecord file demonstrates the value of collaborative troubleshooting. By sharing the specific file path and the nature of the corruption, the community enabled affected users to regain access to the game while the developers work on a permanent code fix.
The existence of this issue also underscores the importance of cloud saves and server-side data management. Because achievements are stored on the server, they are insulated from local file corruption. This architectural design ensures that even when local data is reset, the player's long-term progress and milestones are preserved. This separation of concerns is a critical feature in modern gaming platforms.
In summary, the login failure in "Night of the Full Moon" is a result of a specific interaction between a date-fetching bug and local file corruption. The solution involves a targeted deletion of the corrupted UserinfoRecord file in the LocalLow directory. While this may reset local progress, it preserves server-side achievements. The community has validated this fix, and it serves as a practical workaround until the developers release a code-level patch for the date-handling error.
Conclusion
The inability to sign in to "Night of the Full Moon" following the recent update is a documented issue rooted in a programming error regarding date fetching and subsequent corruption of the local UserinfoRecord file. The solution requires users to manually navigate to the hidden AppData\LocalLow directory and delete the specific file. This action clears the corrupted data, allowing the game to regenerate a fresh configuration file and bypass the boot freeze. While this process may reset local game progress, it does not affect server-side achievements. This community-verified fix provides immediate relief, bridging the gap until an official patch resolves the underlying date-fetching bug in the game's code.