Before changing settings or reinstalling, check whether your symptom appears in the dated September 3 record—and whether its platform qualifier matches your case.
Short answerThe September 3 record separates four issues expected to be fixed from one console-only issue listed as fixed. The expected group covers missing skill VFX for the Ephemeral Dream - Butterfly's Emissary skin, abnormal Behemoth mount-action display, incorrect swimming status in certain underground scenes, and—on console only—a missing team entry in the function wheel and navigation menu in Manibus (Novice). The console-only language-switching issue during the beginner securement-facility task appears in the fixed group. A match confirms that the symptom was documented; it does not prove that every current occurrence has the same cause or status. Record the platform, displayed version, location, trigger, and observed result before changing the installation or submitting a report.
Read the September 3 status labels correctly
Prevent a dated announcement from being treated as proof that every occurrence has disappeared.
- Treat the first group as issues the announcement expected to be fixed by 6:00 AM PT, while recognizing that the captured sentence about actual completion is incomplete.
- Treat the separate task-guidance entry as listed in the announcement's fixed group.
- Use the record as a bounded symptom list rather than a complete catalog of version 3.0.4 issues.
Match the expected-fix symptom group
Give players a concise matrix that preserves the subject and scope of each documented symptom.
- Ephemeral Dream - Butterfly's Emissary skin: its skill VFX could be missing.
- Behemoth mount: its actions could display abnormally.
- Certain underground scenes: players could incorrectly enter swimming status.
- Console only, Manibus (Novice): the team entry could disappear from both the function wheel and navigation menu.
Separate the console-only fixed entry
Keep the platform qualifier and task context attached to the documented classification.
- The entry applies to console only.
- The symptom was task guidance switching to another language.
- The documented context was the beginner task while building securement facilities.
- Do not infer the same classification for PC or mobile from this console-only entry.
Verify a live symptom before troubleshooting
Turn a possible match into a reproducible record without assuming its cause.
- Record the platform and displayed game version.
- Write down the scenario, scene, task, skin, or mount involved.
- Repeat only the action that triggered the symptom and note the observed result.
- Compare the full context with the announcement instead of matching on one shared word.
- Check a newer official notice before treating the September 3 label as current.
Report a remaining issue with useful context
Help players submit a bounded report when the symptom persists or falls outside the supplied list.
- On PC, the official index directs players through ESC, Support & Feedback, and Submit Suggestion.
- On mobile, the official index directs players through the map's left-side menu, the headphones icon, Suggestions, and Submit Suggestion.
- Include the platform, displayed version, reproduction sequence, location, and observed result.
- Describe an unlisted symptom as unclassified by this record rather than declaring it resolved or unresolved.
Worked example
A console player in Manibus (Novice) cannot see the team entry in either the function wheel or navigation menu. That full description matches the console-only entry in the September 3 expected-fix group. The player records the displayed version, confirms both menu locations, repeats the trigger once, and notes the time observed. Because the dated listing does not establish the current status of every occurrence, the player checks for a newer notice and reports the recorded details if the symptom remains. A PC player with a missing team entry would not inherit the console-only classification from this record.
Frequently asked questions
Does the September 3 record prove my symptom is fixed now?
No. It is a dated classification record. Most entries appear in a group expected to be fixed, while the console-only task-guidance entry appears in a separate fixed group. Newer notices and the details of the live case still matter.
What if my symptom resembles an entry but occurs on another platform?
Preserve the platform qualifier. The missing team entry and task-guidance language entries are console only in the supplied record, so their classification should not be extended to PC or mobile.
What if my issue is not in this list?
Describe it as unclassified by the supplied September 3 record. The announcement is a limited fix list, not a complete catalog of version 3.0.4 behavior.
What should I record before reporting the issue?
Record the platform, displayed version, scenario or location, affected task or cosmetic context, triggering action, observed result, and whether the result repeats.
Sources and review notes
E-02 supports the September 3 symptom descriptions, status-group distinction, platform qualifiers, and publication date. E-01 confirms that the official update index listed the September 3 bug-fix notice and supplies the PC and mobile reporting paths. The evidence was captured on September 4, 2026, and does not establish later status changes or a complete issue catalog.
Prepared with an automated research workflow and published only after evidence and policy checks.