Shadows

Explore another layer of character development, with Shadow-system behaviour tracked separately from ordinary crew growth.

Being finished

A system with its own rules

Shadows add another part to the character-development landscape. They deserve a guide of their own because a player should not have to infer their rules from equipment, recruitment or a similarly shaped window. The rebuild keeps the system distinct instead of assuming that every growth mechanic works in the same way.

That approach is especially useful where preserved information is incomplete. We can identify a system and reconstruct particular actions without having evidence for every cost, availability condition or later result. Unknown details stay open until the relevant source and working behaviour can be connected.

What has been built

The measured work includes opening an owned soul altar, worshipping there, collecting earned souls into the soul bag and selecting a soul. It also checks collection when the bag is full and selling eligible souls. These concrete actions are useful progress, while the missing passing test-server journey remains an explicit qualification.

Implementation is only part of the story here. The current public measurement notes a specific live-testing gap: Shadows does not yet have a passing journey in the set of test-server reports being counted. That matters because an isolated test cannot demonstrate that an ordinary player can reach, use and revisit the system successfully.

Why the test gap stays visible

A development team can exercise a narrow action with a prepared account and still miss a problem in the route that leads to it. The missing full journey therefore remains a limitation, even when several component behaviours have been implemented. We do not turn the existence of a window or stored data into a claim of finished play.

If you are comparing growth systems, read the Haki guide and the Devil Fruits guide. The progress board gives the current Shadows status, and its method page explains the difference between built work, test results and release readiness.