What this page can and cannot claim
The keyword asks for the best general points build in 1.0, but the supplied source record does not contain a complete, independently checked point-by-point table. This page therefore gives a practical allocation framework and a verification worksheet rather than inventing exact totals. It is a starting route for a player who wants to test a build, not an official developer recommendation.
The release boundary is explicit. The Steam store displays the formal release date as 2026-08-20. The developer Full Release - Version 1.0 announcement is dated 2026-08-19. This page uses the Steam date consistently and keeps the announcement date only as a source-date difference.
A useful allocation order
Begin with the category that makes a run more repeatable, then add scaling that supports the team job you are actually testing. In practice, compare three questions: does the point reduce an early failure, does it keep the core damage pattern active, and does it still matter in the mode you are playing? If the answer is no to all three, hold the point rather than spend it because a guide called it best.
This order is an editorial framework, not a hidden official formula. The exact categories, costs, caps, and interactions must be read from the current in-game or official 1.0 material before publishing a definitive table.
| Pass | Question | Evidence to record |
|---|---|---|
| 1. Stability | Which early failure does this point prevent? | Mode, difficulty, first pressure point |
| 2. Uptime | Does the team keep delivering its main damage? | Attack pattern, movement, cooldown notes |
| 3. Scaling | Does the choice improve the later run as well? | Wave or boss context, repeat run |
| 4. Fit | Does it support the team rather than a different build? | Character, weapon, upgrade route |
How to turn a route into evidence
Write down the starting allocation, the mode, the difficulty, and the team. Run the same opening twice, changing only one point family. Record the first place the builds diverge, not just which run ends with a higher score. A point that prevents an early collapse may be more valuable for a consistent route than one that produces a larger late number in a lucky run.
Then compare the result with Synergies. General points do not operate in a vacuum: a point that is excellent for a coverage-heavy team may be less useful for a focused target route. Keep the point recommendation attached to its scope.
Date and source note
The official release post is still valuable for the 1.0 version boundary and update context, but it is not a substitute for a current point table. The Steam store supplies the purchase and release display used here. Recheck both before treating this page as a permanent meta guide.