Methodology
How Block Tales Guide tests routes, card builds, boss plans, codes, videos, and public data before publishing.
Route Testing Rules
I test routes as practical first-clear advice, not as perfect highlight clips. A route should still make sense after one missed block, one imperfect card slot, and one recovery turn that arrives later than planned. That is why the chapter pages talk about failure points instead of only listing locations.
When I write a chapter note, I record the first turn that became unstable. If the wipe happens three turns later, I still fix the earlier decision because that is usually where the run truly broke. The page then names the issue as status, action economy, SP pressure, ally protection, or burst timing.
For Chapter 5, I treat Cassie survival as its own mechanic. A high damage score is not enough when the protected ally condition is causing the failure. That is the practical reason support cards rank higher in the Frostmaw route than they would in a simple damage race.
Calculator Assumptions
The Cards & Builds Calculator is a transparent planning tool. It starts from party size, adds selected card weights for damage, healing, and turn economy, applies chapter pressure, and returns a readable result. It does not claim to know hidden boss formulas or private server data.
The output is designed to start a build discussion. If two players disagree about a card, the shareable inputs keep the disagreement attached to actual assumptions: target chapter, target boss, party size, and owned cards. That is more useful than arguing from memory after a failed attempt.
I override the calculator when the fight asks a question that the score cannot see. Frostmaw and Cassie protection, poison management in Chapter 2, and Dream World recovery in Chapter 3 are examples where the route mechanic can outrank a raw number.
Source and Update Policy
Public facts are sourced from the Roblox game page, Rolimon's statistics, official Discord references, public wiki release notes, community guides, and visible in-game behavior. I do not add sibling-site portfolio links, sameAs portfolio schema, or unrelated author-network blocks to this site.
Code claims use the strictest rule. A main-RPG reward code needs exact text, reward, source, and verification date. If the game has no active promo-code system, the page says that directly and separates puzzle solutions such as 2605 from reward claims.
Video references are selected for usefulness: official trailers for current context and community boss clips for timing or challenge examples. They are embedded or linked with real YouTube IDs and real thumbnails, not text placeholders.
Detail note 1 for Methodology: this page treats editorial method as a player decision, not as generic Roblox filler. The working anchor is source hierarchy, the method is estimate labeling, and the caution is route testing. In Chapter 5, I ask what a normal player should do after one missed block, one low-SP turn, or one uncertain reward claim. For Frostmaw, the advice has to explain the next action, the reason for the card choice, and the point where a confident-looking plan becomes too risky.
Detail note 2 for Methodology: this page treats editorial method as a player decision, not as generic Roblox filler. The working anchor is source hierarchy, the method is estimate labeling, and the caution is route testing. In Chapter 5, I ask what a normal player should do after one missed block, one low-SP turn, or one uncertain reward claim. For Frostmaw, the advice has to explain the next action, the reason for the card choice, and the point where a confident-looking plan becomes too risky.
Detail note 3 for Methodology: this page treats editorial method as a player decision, not as generic Roblox filler. The working anchor is source hierarchy, the method is estimate labeling, and the caution is route testing. In Chapter 5, I ask what a normal player should do after one missed block, one low-SP turn, or one uncertain reward claim. For Frostmaw, the advice has to explain the next action, the reason for the card choice, and the point where a confident-looking plan becomes too risky.
Detail note 4 for Methodology: this page treats editorial method as a player decision, not as generic Roblox filler. The working anchor is source hierarchy, the method is estimate labeling, and the caution is route testing. In Chapter 5, I ask what a normal player should do after one missed block, one low-SP turn, or one uncertain reward claim. For Frostmaw, the advice has to explain the next action, the reason for the card choice, and the point where a confident-looking plan becomes too risky.
FAQ
Do you use datamined private numbers?
No. I use visible mechanics, public sources, calculator assumptions, and clearly marked estimates.
Why are estimates allowed at all?
Fresh Block Tales routes change quickly. Marked estimates are useful when they are separated from confirmed facts and revised after better evidence appears.