EA_Cade​ 

I think the updated statuses are way better that what we had before when we were reporting bugs. Here are some updates for more improvement:

• The update to the bug statuses should have been a blog post rather than a forum post so all players are aware about how to track the progress of their bug report.
• I'm disappointed the "Awaiting Additional Reports" status wasn't clarified better. The description states: These issues are currently in our backlog as we await further reports or information from the community on them.
  • The posts don't provide clear information on what is needed from the community to move the reports forward in the bug reporting process. For example, I reported this bug [GF] Skill Icon Missing from Perform Romance Scene for Tips | EA Forums - 13067266. I included an image showing the issue. It is for a missing icon. I don't know what additional information is needed from the community. Does this mean save files are needed to identify the problem in the game?
  • There is no clear distinction between this status and Needs More Info. The status for Needs More Info states: We need more information from the community to continue investigating this issue.
• The information on reporting bugs is still scattered, disjointed, and too complex for a player to understand and this new post on the updated statuses contributes to the issue. There should be a single post detailing how to report a bug. Example: 

🌟 Quick Guide: Reporting Bugs in The Sims 4

Short, clear steps so you can create an excellent bug report quickly.

1. Confirm it’s a real bug

• Note what happened, what you were doing, and how often it happens.
• Remove all mods/CC from your Mods folder (don’t just disable them).
• Clear your cache:
  • Close the game.
  • Open your The Sims 4 folder (Documents > Electronic Arts > The Sims 4).
  • Delete these safe-to-remove files/folders:
    • localthumbcache.package
    • cache
    • cachestr
    • onlinethumbnailcache
  • Do not delete your Saves folder.
• Test in a new save with a new Sim.

If the issue still happens, you’re ready to report.

2. Search the bug report forum

• If a report already exists:
  • Vote for it — more votes mean higher visibility and priority.
  • Add extra info such as screenshots, saves, videos, or new discoveries.
  • Do not create a new thread for the same issue. Duplicate posts will be locked and merged.
• If no report exists:
  • Create a new post.
  • Only one issue per post or it will be locked as Multi Report.
  • Reports must be in English or they will be locked and marked Unsupported Language.

3. Write a strong bug report

Title

• Write a descriptive title that someone else could find.
• Include names of objects, assets, careers, aspirations, worlds, lots, and similar details.
• For CAS, you may use names from S4Studio (optional).
• Add pack abbreviations only if the bug affects three or fewer packs.
• Use the official title tag abbreviation list from the EA Forums.

Body

Include:

• Game version number
• Clear description of the bug
• Exact steps to reproduce
• How long you’ve seen this (for example: “since patch X”)
• Error codes (if any)
• LastException.txt text (PC/Mac only), if generated
• LastCrash files (PC/Mac only), if generated
• Links to:
  • Save files (for example, via cloud storage)
  • Screenshots or videos
  • Gallery builds, if relevant

Thread tags

Choose tags that describe your setup and issue. Missing platform or mod-usage tags will cause your post to be marked Incomplete Report.

• Platform: PC, Mac, Xbox, PlayStation
  • If on PC, also choose Steam, Epic, or EA App.
• Mod usage (choose exactly one):
  • CC or Mods Removed
  • Never CC or Mod
• Performance (only if relevant):
  • Crashing
  • Freezing
  • Lags
  • Loading Times
• Game issues (as needed):
  • Error Codes
  • Live Mode
  • Build Mode
  • CAS
  • Maps
  • UI
  • Gallery
  • Game Menu
  • Other relevant categories

Submit your report

• When your title, body, and tags are complete, publish your report.

4. Understand the statuses

Your report may move through these statuses:

• New — Just created.
• Troubleshooting — Staff or community are gathering details.
• Reviewed — Staff believe it might be a real bug. Aim for this status.
• Validating Report — QA is testing to reproduce the issue.
• Needs More Info — More details or files are needed from players.
• Verified — QA reproduced it; waiting on development work.
• Under Investigation — The development team is actively working on it.
• Validating Fix — A fix is being tested internally.
• Upcoming Fix — A fix is approved and planned for a future patch.
• Fixed — Resolved in a patch or confirmed by players.
• Incomplete Report — Missing information or tags; must be updated.
• Awaiting Additional Reports — Waiting for more player reports.
• Unsupported Language — Not in English; thread locked.
• Multi Report — Multiple issues in one post; not allowed.

5. Follow up and be patient

Check your report regularly

• Look for status updates every few days.
• Within 2–3 days, your report should usually move to Reviewed, meaning staff has accepted it as a possible bug.

Respond when needed

If your report is marked Troubleshooting, Needs More Info, or Incomplete Report, you may need to add:

• Missing thread tags (platform, mod usage, and similar details)
• More details or clearer steps
• Save files, screenshots, or videos
• Error codes
• LastException.txt text (PC/Mac only)

If your report stays in Troubleshooting or Incomplete Report for about a month, it may be moved out of the forums.

Keep your report updated

• You can add new information at any time by editing your post: new saves, screenshots, discoveries, or patterns help a lot.
• Update your report if your issue was fixed and the report was not marked as Fixed, and include the patch number.

Be patient

• Some bugs take time to investigate and fix, even after they reach Verified.
• There is no need to contact forum staff about the status unless they specifically ask you for more information.

Stay informed

• Check posts marked Important Info to keep up with changes to the bug reporting process.

Vote on reports

• Bug reports with more votes receive higher priority.
• Continue voting on existing reports that affect you.