Your first Wishlist¶
A Wishlist describes the Echo build you want. It can include copies you do not own yet.
Plan before enabling automation¶
- Open Wishlists or type
/nexus editor. - Create a Wishlist, or import a Wishlist code into a draft.
- Review the exact Echo qualities and copy counts. Keep rolled targets and permanent-slot targets separate.
- Save the plan and assign it to the intended Saved Build/loadout.
- Review recommendations before enabling the master Automation switch and its individual actions.
Supported plans include 79 rolled copies and 6 permanent-slot copies. That does not mean 85 ordinary rolled picks. Duplicate copies and different qualities matter.
If a save is refused
The public beta preserves the draft and explains the refusal. Check the intended destination and assignment rather than clearing your data or assuming the save succeeded.
Three different things¶
| Term | Meaning |
|---|---|
| Wishlist | Your desired Echo plan. |
| Saved Build | A server-side build slot. |
| Active Loadout | The currently selected server loadout. |
| Build Library | Locally known saved/shared records for browsing. |
Saving a Wishlist is different from saving a server build or choosing Share Build.
Understand the controls¶
Recommendations help you review a decision. Enabling automation permits selected actions; it does not guarantee that Nexus can proceed in every state. A pending result, unavailable capability, or unresolved offer can still pause progress.
The current beta uses an experimental adaptive rolling strategy by default. The previous strategy remains selectable. Selecting a Saved Build does not guarantee future Echo offers.
Permanent-slot targets are the intended plan. Current permanent Echoes are what you own. Freeze retains an offer temporarily. These are separate concepts; opening the target editor does not itself change owned permanent slots.
For Orbs / Lost Memories, review the feature limits and the in-game Help before starting a run.
Sources: public test.9092 and tagged player guide.