Fortune's Weave Supports, Romance & S-Supports

Fire Emblem: Fortune's Weave does have late-game relationship payoffs, but "romance," "paired ending," and "S-support" are not interchangeable labels. Post-launch guides and community evidence agree that Support conversations exist, that some bonds can lead to an epilogue pairing, and that Eshmel can unlock an S-rank scene at the end of the game. They do not support a simple rule that every high-rank Support becomes a romance.

This page keeps the verified mechanics separate from community-observed details so you can plan relationships without relying on a made-up compatibility chart.

Support rank and romance are different questions

The existing Support guide covers how to raise Support for recruitment and route planning. This page answers a different search intent: what happens after those relationships are built?

Current post-launch sources describe several layers:

Support rating grows as characters interact and fight together.
Support conversations are unlocked at specific ranks or after story conditions.
A-rank bonds can be relevant to paired endings for some characters.
Eshmel's endgame choice can unlock an S-rank scene at maximum Support.
Romance is ending-specific, so an S-rank or paired ending should not be treated as a universal marriage flag.

That distinction explains why launch-week answers can look contradictory. One source may say the game has S-supports while another says it does not have the same selectable romance structure as Three Houses. Both can be describing different parts of the same system.

What is verified post-launch

The safest current conclusions are:

C, B and A Support conversations exist.
Some pairings do not use the same full rank chain as others.
Some high-rank bonds can lead to a Paired Ending in the epilogue.
Eshmel can reach an endgame S-rank scene with a qualifying character after the final battle.
Current guides place that Eshmel payoff at Support rating 5.
A paired ending can be romantic or platonic.
A complete, authoritative romance-eligibility matrix is still not verified.

The last point matters most. The cast is large, support chains vary, and post-launch databases are still being filled in. If a table claims that every recruit can be romanced, or that every A-rank pair has the same ending rules, treat it as unverified unless the underlying scene or game data is shown.

How Eshmel's S-rank scene works

Post-launch coverage consistently separates Eshmel from ordinary character-to-character Support chains.

After the final battle, guides report that Eshmel can be directed toward a character whose relationship has reached the required maximum rating. That choice unlocks an S-rank Support scene. Current reporting places the threshold at Support level 5.

The important planning rule is not "get everyone to S." It is:

build the relationship you care about before the ending;
make sure the target relationship actually reaches the required endgame rank;
do not assume every recruit is eligible;
save before the final sequence if you want to compare available outcomes.

Some guides also report that these scenes can be revisited after completion, but the exact replay flow is a secondary detail and may depend on post-game state.

Paired endings are not automatically romances

A Paired Ending describes who shares an epilogue outcome. That does not guarantee the relationship is romantic.

Current reporting includes examples where the ending is affectionate or future-facing without being framed as a romance. This is why a spoiler-free guide should avoid converting every eligible pair into a "romance option."

A useful way to read the system is:

Term	Practical meaning
Support rating	Relationship progress used by the game's Support system
Support conversation	A scene unlocked by rank and sometimes story progress
A rank	Highest ordinary rank documented for many chains
Paired Ending	Shared epilogue outcome for an eligible pair
S-rank scene	Eshmel's special endgame relationship scene
Romance	A narrative outcome that must be verified pair by pair

This wording is deliberately conservative. The game has relationship content, but the tone and result of each ending can differ.

Do all characters have S-supports?

No complete evidence supports that claim.

Community discussion after release shows active testing and conflicting reports about which characters can reach S with Eshmel and which endings are romantic. Some players have confirmed S-rank availability in the interface, while others are still mapping missing or partial Support chains.

That means this site will not publish a full "romanceable characters" matrix until each row can be backed by a current source or direct in-game evidence.

If your goal is simply to avoid wasting relationship investment, use three checks:

Confirm that the character has a meaningful Support chain.
Raise the bond before the final sequence rather than waiting for the epilogue.
Treat the ending as unconfirmed until the character is shown as an available endgame choice.

How to prepare without spoiling the ending

If you want a spoiler-light run, focus on relationship progress rather than outcome lists.

Use gifts, meals and other shared activities described in the Support guide. If the character is recruitable, also confirm route availability through the Recruitment overview. A character you never recruit cannot become a practical relationship target just because a community chart lists a Support chain.

A good low-spoiler workflow is:

Recruit the characters you actually want in your roster.
Raise Support naturally and use gifts or meals when a bond is lagging.
Read Support conversations as they unlock.
Keep progressing the story if a conversation is locked behind a later Part or chapter.
Before the final battle, review the relationships you care about most.
Make the endgame choice from the options the game actually presents.

This avoids chasing an unverified spreadsheet and keeps the guide useful even while the full support database is still being documented.

Why current sources disagree

The terminology is still settling after launch.

One community-maintained database describes A-rank bonds, Paired Endings and Eshmel's S scene as connected but distinct layers. Another post-launch guide warns that the game does not work like a universal player-directed romance picker. Reddit discussion shows players using "S-support," "romance," and "paired ending" in overlapping ways while new scenes are still being discovered.

The safest interpretation is therefore mechanical rather than semantic:

Yes: the game contains high-rank relationship scenes and paired epilogues.
Yes: Eshmel has an S-rank endgame scene.
No: that does not prove every paired ending is romantic.
No: there is not yet enough verified evidence for a complete eligibility matrix.

Sources

These are post-launch sources and may continue to change as more Support chains are documented. This page intentionally avoids filling evidence gaps with guessed pairings.