Link Attacks sits in the Relink Core layer of Granblue Fantasy: Relink - Endless Ragnarok. This page is built for a player who needs to know what the mechanic changes, when to care about it, and what evidence should be collected after launch before it becomes a build recommendation. It also separates official wording from launch-test fields so early readers can act now without mistaking a trailer description for final strategy.
Official Role
Link Attacks are part of the base Relink combat loop: stun pressure creates openings, party actions raise link level, and successful timing can lead into Link Time.
In plain player terms: Stun pressure opens Link Attacks, and party actions raise link level. At full link level, a successful Link Attack can trigger Link Time. This matters because Endless Ragnarok adds new systems on top of Relink's existing four-character combat loop instead of replacing that loop. A page about Link Attacks has to connect the official feature name to a real action: buying the right product, opening the right menu, choosing the right party, timing the right burst window, or deciding which postgame route to test.
The useful boundary is important. Official copy can confirm names, supported platforms, broad purpose, and visible feature relationships. It cannot confirm final farming routes, best-in-slot loadouts, cooldown breakpoints, reward odds, or universal character rankings. For Link Attacks, this wiki should move from official facts to measured advice only when a tester can repeat the result and name the route.
Player Decision
Use Link Attacks as a timing language. If a party cannot reliably create or spend openings, Summons, Primal Bursts, and Chaos quest plans will feel random.
A strong Link Attacks page should change one of four decisions. It should tell a new player what to learn next, tell a returning player what changed from base Relink, tell a co-op group how to coordinate, or tell an endgame player what needs live testing before investment. If a note does not affect one of those decisions, it belongs in a dated observation rather than the main recommendation.
What to Verify
The first launch update for Link Attacks should be practical, not decorative. A reader needs unlock condition, menu location, quest or platform context, and the exact reason the mechanic changes play. Screenshots, short tables, and dated test notes are more useful than a long opinion paragraph because they survive patches better.
- Record enemy stun setup and trigger condition
- Check whether the opening is reliable in solo and online play
- Note which characters help create stun faster
- Capture whether Link Time changes damage or survival decisions
The minimum evidence bar is higher for anything that touches damage, rewards, or progression. If Link Attacks affects clear time, survivability, unlock routing, or account behavior, the page should preserve the raw observation first: platform, party, quest, date, and result. Recommendations can come after that. This keeps launch-week pages fast without letting first impressions become permanent advice.
Current Tracking Fields
| Field | Current value | Why it matters |
|---|---|---|
| Phase | Relink Core | Decides whether the page teaches a base loop or an Endless Ragnarok addition. |
| Core hooks | Build enemy stun gauges; Coordinate party burst windows; Use Link Time to slow enemies and gain buffs | Shows the three claims that should be verified or expanded first. |
| Testing priority | Record enemy stun setup and trigger condition | Gives the first concrete update task after release. |
Common Mistakes
The fastest way to make a Link Attacks guide useless is to treat a feature name as a solved strategy. Avoid these mistakes until the release build and first patch cycle provide enough repeatable evidence.
- Treating Link Attacks as automatic damage instead of setup payoff
- Ignoring the party actions that build link level
- Testing burst routes without first testing stun reliability
Negative results are also useful. If Link Attacks does not change a route, does not improve a clear, or works only under narrow conditions, keep that note visible. Players trust a wiki faster when it explains what not to force, especially in a launch window where every new term can look mandatory.
Related Systems
Link Attacks rarely stands alone. If it changes party timing, read the Link Attacks, Chain Bursts, Summons, and Primal Bursts pages together. If it changes progression, compare it with Chaos Quests, The Conflux, Master Traits, release timing, and edition ownership. That cross-check keeps one page from drifting away from the actual player route.