The official Steam feed adds September 30 resource-patch evidence for specific textures, quests, Egg Heist and console cases. The earlier 20-record board is retained with its own source dates. Developer plans and account restrictions are separate; this is not a complete bug archive and not a live outage monitor.
September 30 Steam patch: targeted fixes, not an all-clear
The official Steam announcement feed includes Patch Notes-v1.0.3629693.0, a September 30 resource update. Restarting the client is the developer’s update instruction; it is not a reason to unlink an account or delete a character.
The patch lists specific Irisalis/other model texture cases, an absent outer-island Sanctum entrance, several quest progression blockers, Home/interface problems and console achievement fixes. Match the described symptom before concluding that a patch applies. Keep the exact error and context for official support if it persists.
The 20 source-dated issue records below remain unchanged as an earlier, explicitly partial board. They are not the complete September 30 fix list. See our resource-patch summary and separate Dev Dispatch plans; the mobile overheating work is not certified complete.
September 30: account enforcement is separate from this bug board
A new official September 30 notice discusses account violations from September 16–22. It does not announce a graphics, connection or capture fix, so the 20 source-dated issue records below remain unchanged.
An explicit restriction needs the account-specific support path. A missing character or generic timeout is not enough to diagnose a ban. The publisher’s notice directs reports of harmful in-game conduct to the in-game report entry; we do not collect accusations or republish the player list.
September 26 review: newer evidence, not a new patch
The official version 1.1 notice was published September 21 for the September 23 update. It explicitly lists red-tint and specific GPU-blackout fixes, an infinite reconnection-loop fix and a Sanctum restart/fainting case. We have now applied those statements to the relevant records instead of leaving the old red-screen conflict as the latest answer.
These are scoped developer claims. Unmentioned first-entry Astra effects and beta Sealed Egg claim eligibility are not automatically resolved. The compensation note below remains an observation dated September 25.
September 25 review: compensation and mailbox follow-up
The official Steam announcement index currently contains a follow-up under the older update-preview headline. It adds 500 Glimmers for the delayed launch to the original 500, and lists one Sparkling Cube for a known issue. It describes two mails: 1,000 Glimmers and one Sparkling Cube, to be sent after mailbox restoration.
This is a notice observed on September 25, not confirmation that the mailbox is still down or that every account has received the items. The follow-up’s precise edit date and delivery completion are not verified. The original maintenance eligibility was registration before the version 1.1 update; this is not a universal new-account reward, and the follow-up does not separately establish every account’s Cube eligibility.
Check the correct character/server and current official messages before reporting a missing mail. Keep maintenance compensation separate from beta Sealed Eggs, Home milestones and code redemption. Do not unlink accounts or enter credentials into a third-party claim form.
September 23: start with the newer launch context
Read the version 1.1 changes and regional event windows or the mobile login checklist first. The September 23 mobile-launch notice confirms launch, not the resolution of every old issue.
The previous patch records below keep their original source dates. An issue missing from a later announcement is not automatically fixed or still happening to all players. Check a current official notice or your client before acting on an old workaround.
Historical September 19 patch context
In the September 19 review, the numbered notice inspected was 1.0.3551601.0, published September 19, 2026 at 09:09 UTC (02:09 PDT / 17:09 UTC+8). These are announcement times, not a claim that every regional client installed it at that instant.
The earlier 1.0.3544783.0 and 1.0.3535596.0 fixes retain their original version labels below; the latter was published September 16 at 16:43 UTC. Read the September 19 English notice or the same patch in Simplified Chinese.
Find your symptom and the next safe step
20 of 20 issues
Localized blackouts on specific GPU models
The 1.1 notice lists a fix for localized rendering blackouts on specific GPU models. It does not say that every black screen has this cause.
What to do: Install the official update. Record the device and exact scene if the issue persists; do not apply PC-only driver instructions to a phone.
Choose the matching graphics checkClient stuck in an infinite reconnection loop
The 1.1 notice lists a fix for an infinite reconnection loop under certain circumstances. This is not a live server-status statement.
What to do: Distinguish a repeated reconnect loop from an ordinary queue, maintenance or a local network error. Keep the client version and error text.
Check reconnection versus queueStuck after restarting during the Sanctum fainting black screen
The 1.1 bug list names a character getting stuck after the client was restarted during the black screen of fainting in a Sanctum.
What to do: Use the updated client and avoid deliberately reproducing this interruption. If stuck, capture the scene and use official support; no save deletion or reward-restoration guarantee is implied.
Separate the restart case from revivalNo designated Aniimo after using Nurture Offerings
The new patch fixes designated Aniimo not refreshing after Nurture Offerings were used to nurture Veins in some areas. It does not name every affected area or give a replacement offering recipe.
What to do: Update, note the exact area and offering, then distinguish a missing refresh from an ordinary rare-form outcome. Do not spend repeated offerings merely to test a suspected malfunction.
Check a missing Nurture refreshWrong Aniimo family at a Zephyrus Landbridge Bloom
The note separately corrects Blooms in Zephyrus Landbridge being associated with the wrong Aniimo family. This is not the same statement as the area-specific refresh failure.
What to do: Compare the current in-game Bloom and family after updating. The note supplies no complete revised family table, so do not import an old spawn list as a guaranteed result.
Check the Bloom-family correctionActive Aniimo cannot revive after repeated faints
The patch names a rare failure to revive after the active Aniimo fainted multiple times inside a Sanctum. The notice gives leaving and re-entering the current scene as a recovery step if it persists.
What to do: Use the normal scene exit when available, then re-enter. Check any exit warning first: this guide cannot guarantee checkpoint or reward preservation.
Follow the Sanctum recovery checksCatch result does not process correctly
The note lists a fix to capture-result processing. It does not identify a species-specific probability, a guaranteed successful catch, or a compensation policy.
What to do: Update and compare the result message with Aniimo Management. Record a repeatable mismatch rather than treating every escaped target as the processing defect.
Separate processing from catch chanceBond Egg hatching conditions disagree with the description
The new fix concerns hatching conditions matching the Bond Egg description. It does not explicitly reopen the beta Sealed Egg claim entry or state who may claim again.
What to do: Check the actual egg description and Hatchinator screen after updating. Keep claim entitlement, hatching conditions and Innate Potential as separate questions.
Check hatching versus reward claimingAn NPC disappears during an interaction
The note fixes NPCs disappearing during interaction and blocking further progress. It does not identify every quest or say that all objective-counter problems share this cause.
What to do: Update and record the NPC, scene and interaction if it recurs. Keep this distinct from the older Butterfly Shadows terrain fix.
Report the exact interactionSealed Egg claims: check your server’s entry
The earlier English notice says Bonded Promise Sealed Egg claiming was paused. The Simplified Chinese version of that same patch reports the Innate Potential fix and directs players to Activity Center → Test Rewards Return to re-claim and hatch. The newer patch does not mention the egg claim. The September 19 Bond Egg hatching-condition fix does not explicitly settle the claim-entry discrepancy.
What to do: Check the actual event entry for your account and server. If it is absent, or an already-claimed egg is affected, ask official support. Do not unlink an account or discard an egg to reconcile conflicting notices.
Compare both reward noticesRed tinting on certain devices: a later 1.1 fix
The later version 1.1 notice explicitly lists screen discoloration (red tinting) on certain devices as fixed. The September 18–19 language discrepancies are historical context, not the only evidence now available.
What to do: Update through the official client. This is a developer-listed fix for a scoped symptom, not certification that every device or every earlier visual-effect issue is repaired.
Check red-screen guidanceAbnormal effects on first entry to Astra
The September 19 Chinese notice still lists abnormal effects on first entry to Astra (星之都). Its absence from the inspected English version does not establish resolution. This remains separate from the earlier floating-decoration fix.
What to do: Record the exact scene, platform and build for support. No specific first-entry workaround is confirmed in that note.
Prepare a useful reportBlocked terrain while gathering Butterfly Shadows
The patch lists a fix for occasionally impassable terrain during Butterfly Shadow collection in The Land Where Dreams Come True. It does not say that every missing objective or collection counter has the same cause.
What to do: Update, check the exact quest and objective, then retry the affected route. A separate guide distinguishes this acknowledged blocker from a different progression problem.
Check the Butterfly Shadows blockerQuick Twine and forms in Susuta / Dr. Glass challenges
Quick Twine problems and some forms being unable to participate in the Susuta and Dr. Glass challenges are listed as fixed. This is scoped to those named challenges, not every Twining interaction.
What to do: Update before retrying the affected challenge. If it persists, report the challenge, form and installed build.
Report a remaining challenge issueUnstuck during a two-player Sanctum mechanism
The patch lists a fix for becoming stuck after using Unstuck while interacting with a two-player mechanism in a two-player Sanctum. That is distinct from the Butterfly Shadow terrain bug.
What to do: Install the update and report the exact mechanism and sequence if the problem remains. Do not treat Unstuck as a guaranteed repair for every quest.
Report the exact mechanismRepeated reconnects when the client lags
Version 1.0.3535596.0 lists a fix for the repeated disconnect/reconnect behavior triggered by client lag. This is not a claim that every network failure is resolved.
What to do: Install available updates through your official client. If it persists, record your build, server, time and error instead of repeatedly reinstalling.
Troubleshoot repeat disconnectsSome Xbox and Xbox PC purchases not delivered
The patch lists a fix for purchased items not being delivered properly on Xbox and Xbox PC. It does not promise that every earlier missing order is automatically restored.
What to do: Check your account and inventory. Keep the receipt for official support; do not buy the same item again as a troubleshooting step.
Handle an undelivered purchaseBlack screen returning from Shop to Design Workshop
This specific navigation-related black screen is listed as fixed. It is not the same as a black screen on login, startup or a different scene.
What to do: Update the client. For another black-screen symptom, use the separate graphics troubleshooting steps.
Find the correct black-screen stepsOther PC black-screen symptoms
The note recommends updating the graphics driver, trying DX11 versus DX12, and disabling DLSS and Frame Generation at the login screen. These are troubleshooting options, not a universal fix.
What to do: Use supported settings and official driver sources. Change one option at a time and retain a way to restore it.
Follow the graphics checklistSteam controller input not working
The official note says to try disabling Steam Input for Aniimo through Steam Library → Aniimo → Properties → Controller.
What to do: Make this a per-game change. Re-test the controller and restore the previous setting if it does not help.
Check the Steam controller routeAn Xbox purchase is still missing after the patch
Keep the order receipt, purchasing platform, account/server and approximate purchase time. Confirm that you are looking at the intended account before reporting the missing item. A fix in patch notes is not an individual order-delivery confirmation.
Our recommendation is to contact official support rather than repeat the purchase. This website cannot inspect receipts, issue refunds or move entitlements. A store purchase is also different from the beta reward redemption process.
Open the in-game Menu → Support, or press F10 on PC. If you cannot enter the game, use [email protected]. Give private account or purchase evidence only to official support, never this fan site, and never send a password or verification code.
A new patch does not settle every older warning
“Fixed” describes the specific symptom and source on the card. It does not establish that all devices are repaired. The later 1.1 red-tint fix supersedes the old conflict for that symptom; the earlier wording remains visible as history.
The first-entry Astra and beta Sealed Egg records have no explicit resolution in the 1.1 statements used here. Do not turn either silence or an unrelated hatching fix into a universal claim-entry, entitlement or refund promise.
Good questions.
What does patch 1.0.3551601.0 address?
Relevant fixes include offering-triggered refresh, Zephyrus Landbridge Bloom families, Sanctum revival, capture-result processing, Bond Egg hatching conditions and disappearing NPCs. Each entry is scoped to the notice.
Does the Bond Egg fix confirm all beta claims reopened?
No. Hatching conditions and claim-entry availability are different questions. The September 19 note does not explicitly settle the earlier Sealed Egg language discrepancy.
Are red screen and first-entry Astra effects resolved?
The later 1.1 notice lists red tinting on certain devices as fixed. It does not explicitly settle the separate first-entry Astra effects case or certify every device. Earlier localized warnings remain historical evidence.
Does the September 19 patch change Prismana catch odds?
The note does not announce a Prismana-specific probability change. A refresh fix and a capture-result fix are not new odds tables.
Check the source
- Patch Notes-v1.0.3629693.0 — official Steam feed
- Aniimo Dev Dispatch Vol. 1 — official Steam feed
- September 16–September 22 Violation Ban Notice
- Version 1.1: Vein Abundance, Floral Soirée, Bloom duration and scoped fixes
- Patch 1.0.3551601.0 — capture, nurturing and Sanctum fixes
- Patch 1.0.3551601.0 — Simplified Chinese counterpart
- Patch 1.0.3544783.0 — fixes and remaining issues
- Patch 1.0.3544783.0 — Simplified Chinese counterpart
- Patch 1.0.3535596.0: disconnect fixes and known issues
- Patch 1.0.3535596.0 — Simplified Chinese reward instructions
- PC & console pre-download FAQ
- Aniimo is officially live on mobile
- September 23 update — Setting Out in Pursuit of the Wind: Part I
- Version 1.1 regional event windows and Iris Petal crafting sequence
- Official Steam announcement — appended maintenance compensation follow-up