I wanted to make a small Wishlist suggestion regarding the current bug reporting process.
First: I completely understand why the team prefers separate bug reports. From a QA/tracking perspective, isolating issues individually makes complete sense.
That said, once players begin interacting with larger interconnected systems like:
-
businesses
-
careers
-
crime
-
social AI
-
household autonomy
…the current reporting structure can become difficult from the player side.
A single gameplay session can easily produce multiple related bugs that appear connected to the same underlying system behavior.
For example, while running a café-style business, players may encounter:
-
employees ignoring assignments
-
wandering interruptions
-
customer interaction failures
-
broken restocking logic
-
off-lot simulation issues
-
social AI interruptions
From the player’s perspective, those don’t feel like six unrelated bugs. They feel like:
“Something in the business AI/system is unstable.”
Because of that, reporting every issue separately can become overwhelming and may scatter related reports across the forum, making recurring patterns harder for both players and the team to identify.
Possible Improvements
1) Extensive System-Based Categories + Subcategories
Examples:
Businesses
-
Restaurant
-
Hair Salon
-
Retail
Subcategories:
-
Employees
-
Customers
-
Assignments
-
Interactions
-
Objects
-
Off-Lot Simulation
Crime
-
Heists
-
Wanted System
-
Police
-
Court
Subcategories:
-
Lockpicking
-
Hacking
-
Scripted Events
-
World Interactions
Careers
-
Music Production
-
Reporter
-
Researcher
Subcategories:
-
Tasks
-
Promotions
-
Interviews
-
Workplace Interactions
-
Objects
This would help players organize reports while still allowing the team to isolate individual bugs internally. There can even be a quick wins category listing simple lot issues, e.g., a door on a public lot needs to be moved, or a restaurant is missing a trash can.
2) Grouped / Linked Reporting
Allow players to:
-
Create one “master” gameplay-session thread under a main category
-
Attach multiple related bugs underneath it
-
Link related bug reports together so players don’t have to keep uploading the same save file in multiple threads. It would help reduce duplicate uploads, repeated context explanations, and fragmented investigation efforts for issues that appear to share the same underlying system behavior.
Additional ideas:
-
Players can quickly +1 existing bugs individually within the thread instead of creating duplicates
-
AI summary at the top lists bugs noted in the thread individually, with the number of +1’s
-
Known workarounds or temporary fixes can be added to the summary
Benefits:
-
Easier for players to check if a bug report already exists
-
Easier for the team to identify recurring patterns
-
Reduces duplicate reporting and repeated setup/context explanations
-
The current AI gets better at connecting players to relevant threads as they write their bug report
I think changes like this could create a better balance between:
-
keeping bug tracking manageable for the team
-
and keeping reporting manageable for players
Especially in early access, where interconnected systems can generate a large number of overlapping bugs very quickly.
Please chime in with anything you’d like to add @HeinziDerHeld and @yofford.
