This issue is reproducible. I can consistently trigger or avoid the WEASEL error by changing between specific Exotic armor pieces on my Warlock. I am experiencing a reproducible WEASEL error that only affects my Warlock. Issue * Titan and Hunter load normally. * When I select my Warlock, the game starts loading but disconnects with a WEASEL error before reaching Orbit. * My internet connection is stable and this only affects one character. * This has happened approximately 4–5 times over the last few days. Troubleshooting already performed * Deleted all Warlock loadouts in the Destiny Companion App. * Result: No change. Still received WEASEL. * Moved all Exotic armor off the Warlock. * Result: Warlock loaded into Orbit successfully. I then tested different Exotic armor pieces individually. For each test I equipped the armor, completely closed Destiny 2, restarted the game, and selected my Warlock. Results Works correctly * Getaway Artist → Warlock loads normally. * Crown of Tempests → Warlock loads normally. Consistently causes WEASEL before Orbit * Fallen Sunstar * Vesper of Radius * Dawn Chorus When any of the above Exotic armor pieces are equipped, selecting the Warlock results in an immediate WEASEL error before reaching Orbit. Switching back to Getaway Artist immediately allows the Warlock to load normally again. Additional observations * The Destiny Companion App always displays my Warlock correctly. * Titan and Hunter are never affected. * Earlier this week I noticed several loadouts displaying “?” instead of certain Exotic weapons. * Deleting loadouts alone does not resolve the issue. * I only use the official Destiny Companion App for inventory management. I do not use DIM or any other third-party loadout manager. At this point the problem appears to be related to the interaction between my Warlock character data and specific Exotic armor pieces rather than a network issue.