1
Soul Link is more fun when it is actually playable
The format is messy, cooperative, and entertaining for exactly those reasons. I did not just want to read about it. I wanted to make it practical and understandable.
About Soullinktracker
Why Soullinktracker was built: from a love of Soul Link, curiosity about the rules, and frustration with how clumsy spreadsheets became in real runs.
Why I built Soullinktracker
The starting point was simple: Soul Link is fun. It is one of those Pokemon formats that becomes exciting immediately because the run is never just about one player. It is always about coordination between multiple players.
At the same time, I wanted to understand how the format is actually supposed to be played cleanly. Many rules sound simple at first, but once you really start, you notice how many edge cases, house rules, and coordination questions sit underneath the surface.
So I began with a spreadsheet. That was the obvious path: a few tables, some colors, some structure. It worked for the first ideas, but in real runs it became annoying fast. Statuses had to be maintained manually, links were not truly visible, and after a few sessions there was more admin work than I wanted.
That was the point where an improvised spreadsheet turned into a real project. I wanted something that would not only organize my own runs better, but also create one place where people can understand the rules, avoid common mistakes, and actually play the run more cleanly.
The real triggers behind it
2
I wanted to understand how it is played cleanly
Between community rules, house rules, and common edge cases, there is often no clear structure. That is what led to the guide and reference side of the site.
3
A spreadsheet was a reasonable start, but not a real long-term solution
A table is fine for the first structure. For real runs with teams, boxes, graveyards, links, and route states, it becomes too slow, messy, and error-prone.
4
I wanted documentation and decision support in one place
Not just a place to store data, but a way to read the run: which route is still open, which pair is legal, what dies with what, and where weaknesses are starting to stack.
5
I wanted to build something that helps other players too
If I was already going deep into rules, data, and workflow, it should become more than a private sheet. It should become a public tool with useful guides and references.
Why Excel stopped being enough
The problem was never that you could not store data at all. The problem was that a list does not automatically become a good Soul Link workflow.
Too much manual maintenance
After every encounter, death, and team change, everything had to be updated in multiple places.
The tracker should merge states so the run does not depend on copy-paste discipline.
Links were not truly visible
A spreadsheet can store connections, but not in the way you actually need to read them during the run.
Soul Links should be visible as real relationships, not just as text columns or color coding.
Rule context kept getting lost
Open, encountered, dead, boxed, active, illegal, or strategically awkward: those are exactly the states that blur inside generic tools.
I wanted a structure where the mode itself is part of the logic instead of leaving everything to memory.
Team planning happened too late
In many runs, weaknesses only become obvious right before boss fights even though the signs were already there much earlier.
The site should not just document the run. It should make better decisions easier and earlier.
What the project turned into
That is why Soullinktracker is intentionally split in two parts. The public side explains rules, workflows, and the data foundation. The actual tracker exists to make that understanding usable inside a live run.
It mattered to me that the site should not feel like a tool without context. If someone is new to Soul Link, they need orientation first. If they are already playing, they need a stable workflow. Both belong together.
That is why the site includes more than just a tracker interface. It also includes rule pages, comparisons, FAQs, game lists, Pokemon lists, and team planning. The goal was never only administration. The goal was to make Soul Link more playable.
What the project is supposed to stand for
Clarity over unnecessary complexity
A tool is only good when it makes decisions easier, not when it creates new bureaucracy.
Guides and tool should belong together
Understanding and applying the format should not happen on two completely separate islands.
Specialized beats generic
Soul Link has enough of its own logic that a real specialized workflow makes more sense than a universal sheet.
The community deserves usable tools
If a format is this popular, it should not have to live on awkward workarounds forever.
ðŸ§
If you know the same spreadsheet frustration
That is exactly what this site is built for: understand the format first, then track it cleanly. Read the rules or jump straight into a more structured workflow.