Custom Parties 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
Relink is built around a four-character party in solo and online play, with character-specific weapons, sigils, skills, and progression layers shaping each slot.
In plain player terms: Solo and online play both revolve around a four-character party. Weapons, sigils, talent trees, and skill choices define how each slot contributes. 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 Custom Parties 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 Custom Parties, this wiki should move from official facts to measured advice only when a tester can repeat the result and name the route.
Player Decision
Build the party around a clear job split before chasing final damage: one point character, one burst partner, one safety or support slot, and one flexible slot for the quest problem.
A strong Custom Parties 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 Custom Parties 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.
- Track which party slots are controlled by AI versus players
- Record whether a build works solo, co-op, or both
- Test new playable characters against one stable Relink core party
- Separate character preference from quest-clear consistency
The minimum evidence bar is higher for anything that touches damage, rewards, or progression. If Custom Parties 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 | Four-person party structure; Character-specific trees and equipment; Offline and online planning use the same roster logic | Shows the three claims that should be verified or expanded first. |
| Testing priority | Track which party slots are controlled by AI versus players | Gives the first concrete update task after release. |
Common Mistakes
The fastest way to make a Custom Parties 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 popularity as party synergy
- Building four damage slots before learning survival needs
- Comparing characters without noting who controlled them
Negative results are also useful. If Custom Parties 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
Custom Parties 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.