Original Encounter: I initially did not get an Error Code, but I was unable to load any properties in the Sage Estates neighborhood of Willow Creek. It was just an infinite loading screen, but no Error Code (I received Error Code 801 later, as indicated below). I did not have this issue before. I only recently noticed this when trying to access a family.
There was no issue prior to the Life and Death patch. I own all expansion and game packs except Eco Lifestyle, Seasons, Werewolves, and Batuu. I do not have any residential rentals in my game, as I removed them long ago due to numerous issues, including the litter bug.
First Troubleshoot: I took a look at the Lot Data in Sims 4 Studio and the Object Data for the two Sage Estates lots was missing. I then looked at an older save from late November 2024, and the corruption was present there too (no Object Data present). The last time I played in Sage Estates, and it was normal was in September 2024, prior to the Life and Death patch.
Second Troubleshoot: I was able to access the Sage Estates lots with no cc/mods enabled after the January 15, 2025 update. BOTH HOUSES WERE GONE! The house next door to this one reverted to the default EA house, but when I entered the lot, it was bulldozed. Now both houses appear bulldozed from the neighborhood view, live mode, and map view. I did not save. I exited and rebooted.
Third Troubleshoot: I cleared cache etc., rebooted, moved the families out of the two lots, tried to access one of the lots in build mode, got kicked to the World Screen and received Error Code 801. From the map screen, it appears that the houses are still there, but I know they are not. I can no longer access the two lots. One lot gave me the Error Code 801 and the other lot was an infinite loading screen.
First Last Exception: I received a last exception when I got the Error Code 801. I asked ChatGPT to make sense of what it meant. It said the following:
The XML report you provided indicates that there are two separate desynchronization errors occurring within a game, "The Sims 4." Here's a breakdown of the issues based on the information in the report:
First Desync Issue: Error: RuntimeError('Attempting to set _zone_id to 401118774130050038 when its already set 401118774130050614.') Cause: This error suggests that there is an attempt to set a zone ID to a new value (401118774130050038) while it is already set to a different value (401118774130050614). This kind of conflict typically occurs when there is a race condition or an improper state management in the game's code, particularly in the zone initialization process. The game is trying to create or initialize a zone but encounters a state where it believes a different zone is currently active.
Second Desync Issue: Error: AttributeError("'NoneType' object has no attribute 'id'") Cause: This error occurs when the game attempts to access an attribute (id) on an object that is None. This typically indicates that the code expects an object to be instantiated but it is not, possibly due to a failure in the previous zone initialization or shutdown process. In this case, it occurs during the zone shutdown, where the game is trying to remove an ID from an indexed manager, but the object it is trying to manipulate does not exist (is None).
Summary: These desync issues likely stem from conflicts in the game's state management related to zone initialization and shutdown processes. The first error is a conflict with zone IDs, and the second error is a missing object reference.
Second Last Exception: I tried to access the lots again and received another Error Code 801, and last exception. The possible LE causes were further detailed as above but with additional information:
Possible Causes of the Issue:
- Race Conditions:
- The errors may arise from race conditions, where the game is trying to initialize or shut down zones concurrently in a way that leads to inconsistent states.
- Incomplete Zone Initialization:
- If the zone initialization process fails partway through, the game might attempt to operate on a zone that is not fully set up, leading to a conflict with existing zones.
- Scripting Errors:
- The paths mentioned (e.g., zone_manager.py, areaserver.py) suggest that there may be bugs or unhandled exceptions in the game's scripting. If the code does not properly check for existing zones or handles exceptions during zone creation/removal, it can lead to these types of errors.
- Game Environment:
- The report indicates that the game is not modded, which rules out third-party modifications as a cause. However, issues may still arise from game updates, patches, or bugs within the game's own codebase.
