What Luck should answer
The official Stats (Survivors) page is the starting point for what Luck means and which parts of the game it affects. Read the current definition before making a build claim. A stat name alone does not prove that it improves every random outcome, every item, or every upgrade offer. This page deliberately avoids a made-up percentage or a universal drop-rate promise.
The official Upgrades page supplies the second half of the question: where Luck appears in the upgrade structure and what the listed effect says. Connect the two pages literally. If the source limits the effect to a particular system, keep that limit in the guide.
A test that can answer something
Choose a repeated situation and define the outcome before you begin: a visible offer, an item encounter, or another event the current source associates with Luck. Run a baseline and a Luck-focused route under the same mode, difficulty, team, and approximate duration. Count multiple attempts. If the source does not define a measurable outcome, describe the observation qualitatively and keep the conclusion open.
The purpose is not to reverse-engineer an undocumented formula. It is to prevent a build note from claiming more than the evidence supports. If the observed result depends on a specific upgrade, record that dependency and link to the upgrade page.
- Define the outcome before testing.
- Keep the run context stable.
- Repeat enough times to see whether the pattern persists.
- Separate a source-defined effect from an editor hypothesis.
When to prioritize Luck
Use Luck when the current upgrade text and run goal make its effect relevant. Do not prioritize it simply because the word sounds universally positive. If the team is failing from a direct coverage or survival gap, a Luck choice may not answer the immediate problem. Conversely, if the route is already stable and the source-defined Luck effect supports the next goal, it can be a reasonable experiment.
This is a decision lens, not a tier ranking. The correct pick depends on the current offer and the role your team is trying to fill.
Keep the page current
Stats and upgrade wording can change with a balance patch. Reopen both official pages after an update and replace any test note whose version is no longer clear. Until an official formula is available, a transparent observation is better than false precision.