Patch Changes
Support flow recheck
Use this when food, storage, or return flow started feeling slower after a patch.
Support flow pages matter when the update did not change one guide, but did change the way the whole session feels to run.
Watch the support layer around the session and whether food, storage, or return flow now need one cleaner pass.
What to check
Keep the retest short and tied to one real failure.
Why this hub exists
The hub works best when it explains the maintenance reason before it starts routing you onward.
What this hub is for
Support flow pages matter when the update did not change one guide, but did change the way the whole session feels to run.
Current watch
Watch the support layer around the session and whether food, storage, or return flow now need one cleaner pass.
When to leave
Once the current failure is clear, move to Unload lane instead of staying on the hub.
Best next pages
Open the next page that owns the current failure.
FAQ
Short answers before you open another tab.
Why keep this separate from builds?
Because support flow can drift even when the build is still fine.
What if the problem is bigger than one layer?
Then reopen the broader patch or return-player pages first.