How I'm Playing Fortune's Weave Without Optimizing the Fun Out of It

I have a specific problem with games like this. I love learning how a system works — genuinely love it, it is most of why I play — and there is a point where that curiosity stops being fun and turns into being afraid to play the game wrong.

I know exactly where the habit comes from. I was twelve when the Super Nintendo arrived, which is also when I started reading the manual on the way home from the shop, and around the same time Nintendo Power started turning up in the post. By the time we pulled into the driveway I usually knew what every item did. I loved that. I still love it. But Nintendo Power did two quite different things in the same magazine: it explained how a game worked, and it printed the maps. Thirty years later I can tell you which one made me better at games, and it was not the maps.

Fortune's Weave is exactly the kind of game that could tip me over. Four protagonists, classes, proficiencies, Supports, recruits, Boons, Karma, route-specific systems, a replay structure, and enough small icons to keep the I should understand this before I continue part of my brain occupied until the console goes into a drawer.

So I need a rule that lets me be that person without turning a first playthrough into homework.

I am allowed to understand everything. I do not have to optimize everything.

The manual, not the walkthrough

What I want from a guide — including this one — is the manual half of Nintendo Power. Tell me what the icons mean, what the stats actually do, why a weapon matters, what a class is trying to be, what is scarce, what is safe to experiment with, and what a character is naturally good at before I spend six hours training the opposite thing.

What I do not want is somebody solving the map for me. If a battle is hard, I want to win it because I understood the threat ranges and built the right people, not because a page told me to move Cai three tiles left on turn four.

That is the line, and it is sharper than it sounds. Ask me what Rider proficiency does and I want the complete answer, including the parts that complicate it. Ask me whether to attack the soldier or reposition, and I want to be the one who gets that wrong. Understanding the rules makes the choices more mine. Being handed the choices makes the game less mine.

Finish before perfecting

I have a lot of unfinished games. That matters to me considerably more than whether my first run through Cai's route is the theoretically correct one.

Reach the end of Fortune's Weave with a strong understanding of how it works.

Everything else waits behind that. Replay exists. Missed content can be revisited, characters can be rebuilt, Supports can be tidied up, and I can come back to Cai on a higher difficulty once I actually know Fire Emblem — instead of trying to produce the definitive version of him while I am still working out what Resistance is for.

Mario Paint is the reason I believe that, oddly enough. It was the first game that taught me a game could be something you mess about in rather than something you complete, and that nothing you make in it has to be the final version. That is a useful thing to remember while staring at a class tree.

Grind for a reason

I am not against grinding. I enjoy it sometimes, in the way you enjoy tidying a drawer. The problem is that I will keep going purely because a number is still capable of getting bigger, which is a reflex rather than a reason.

So there is a test. Training is worth doing when I need a proficiency for a class I actually want, when a recruit I intend to use is genuinely behind, when a battle exposed a real weakness, when I want a class mastered for a specific ability, or when I am deliberately testing an alternate build.

It is not worth doing because the bar is not full yet. That is the only bad reason on the list, and it is the one that gets me every time.

The systems I am happy to optimise on purpose

Tactical decisions I want to make badly and learn from. Progression systems are a different category: working out the efficient path there makes the rest of the game less repetitive without telling me how to solve a single map.

So the Boons get deliberately optimised, and normal EXP gets treated as a dial I adjust rather than a purchase I make once. The reasoning is in Karma, Boons and what I buy first; the practical point is that I want this site to remember what I am buying next and why, so that I stop re-researching the same menu every time I earn another handful of shards.

The Wooden Sword lesson

Cai gets a Wooden Sword very early and I equipped it immediately, because the game gave me a sword. Then I learned how classes and proficiencies actually relate to each other, and it turned out that owning a weapon says almost nothing about what a character should become.

That is the kind of mistake I am delighted to make once, understand, and then write down so it stops being a live question. The long version is in my character and class compass. The short version is that a free item is not a build plan, and a recruit who duplicates a job the team already has is not an upgrade.

My personal warning sign

There is a real difference between enjoying a complicated game and being unable to press Continue until every uncertainty is gone. Star Fox is the first game I remember understanding rather than just playing, and the understanding made it better. If reading about something makes me play better, good, that is the whole point of this site.

But if I cannot start the next chapter until I have read twenty pages on every possible consequence, then the guide has stopped serving the game and started replacing it.

Understand the rule. Make a reasonable choice. Keep moving. Replay exists.

The replay structure is what makes that honest rather than a consolation prize. This is not the definitive history — it is the version I am playing now. A missed recruit or a better build does not automatically force a restart. I restart only when the retry itself is doing useful work: preserving meaningful progress while letting me execute a chapter substantially better.

What I want this site to do for me

When I sit down after a few days away, I should not have to rebuild the whole model from memory. I want to see where I was, what I was doing next, what I had already decided, which questions are still open, which Boon I wanted, and what each character is supposed to be turning into.

That is the real purpose of Dad Save Point. It is the manual I would have read in the car, except this time I am the one writing it, and the twelve-year-old it is for has a mortgage.

Chapter 6 update: I was wrong about normal EXP

The original version of this page treated normal EXP as a dial I should keep low enough to preserve a tightly matched tactical challenge.

That was a reasonable theory before I had enough battles to know what I actually enjoyed.

The Thundercloud Knights qualifier gave me the answer.

Cai's team felt roughly matched to the opposition rather than clearly ahead of it. Stronger guest characters made the contrast even more obvious. I could still play the map, but the feeling was not the one I wanted from this team.

I like trained heroes.

I like Cai and his friends walking into an ordinary encounter after weeks of training and being obviously better than the people standing across from them. I like seeing a main unit one-round a normal enemy. Especially with Cai's young team, the sense that they have worked hard enough to become frighteningly good is part of the story I am enjoying.

So the old rule is now historical rather than current.

Normal EXP is a throttle.

My current rule is:

Deliberately overlevel Cai's core. The warning sign is boredom, not being above the recommended level.

I still want tactical decisions. Bosses, objectives, terrain and positioning should still matter. But I no longer need ordinary enemies to be statistically equal to my main army in order for those decisions to be interesting.

That also gives Auto-Activities a new role in how I play. Once I have completed the quests, Support work and other Free Time activities I actually care about, spare Turns can become Combat training camp at the Inn. The tactical maps remain mine to play; the repetitive conditioning between them is exactly the kind of thing I am happy to automate.

This is the kind of change Dad Save Point needs to preserve. The earlier rule was not bad advice that should disappear. It was what I believed before enough play taught me what I actually enjoy.

Chapter 6 update: restarting can be progression

I have now played Chapter 6 three times.

That sounds like exactly the behaviour this page was supposed to protect me from, but the important detail is why I restarted and what the game kept.

The first pass was discovery. I wandered, fished, explored the dungeon and learned how much the world-map travel could cost me.

The second pass was informed, but I still saw enough wasted movement and missed structure that I knew I could execute it much better.

The third pass became the mastery run.

I completed every quest, made it back for the qualifier I wanted to spectate, kept every weekly training/activity cycle I cared about, reached Pale Raven Support level 4, unlocked Smyrnos Bless Level 1, recruited Majide, finished the Support requirement for Sofia and Goliath, bought and refined Cai's Da Mina Spear to +1, bought Spear EXP +1, and still had 150 Karma banked.

The reason that did not feel like throwing two attempts away is that the systems I cared about were accumulating across the resets. Support gains stayed. My unspent Karma stayed. Purchased Boons stayed. So I was learning the chapter and leaving each attempt with permanent progress.

That is much closer to how I actually play than either "never restart" or "perfect every chapter." I like iterative mastery: explore until I understand the system, then execute it cleanly when the clean execution itself is fun.

Chapter 6 update: empty equipment slots are allowed

Majide taught me another rule almost immediately. I gave the big axe recruit a shield because a shield slot existed. His Attack Speed fell to 0 and the whole unit felt awful.

The correction is simple: equipment is not a checklist.

For an offensive unit, I start with the weapon that does the job and then ask what each additional equipped item costs in the battle forecast. A shield is useful when the defense matters more than a follow-up. It is not automatically useful because the game lets me put one on.

Guzran reinforces the same idea. His normal sword should preserve the fast, reliable exchange I want; the heavier Zanbato comes out when its cavalry job is actually relevant. Cai's spear choices follow the same rule: power is good, but power that preserves the double is better for the way I am building him.