Guide + Tracker for Soul Links

No Encounter
forgotten.
No Link
broken.

Soullinktracker is more than just a checklist for encounters. The site explains the rules, points out common mistakes in the Soul Link Challenge, and provides a tracker that keeps both players on the same page.

If you are just starting, read the Soul Link rules and the tracker guide. If you are already playing, you can create a shared run right after that.

Track PokemonRead Soul Link rules
45Supported Games
∞Runs Possible
∞Players per Run
100%Free

What makes the Soul Link Challenge difficult

A classic Nuzlocke run can still be managed with rough notes or a small spreadsheet. A Soul Link Challenge gets harder the moment two players need to keep the same rules, route states, and consequences in view. Once a Pokemon faints, it affects not just one team slot, but an entire connection between both runs.

That is why a simple product description is not enough. People searching for a Soul Link tracker usually need orientation first: Which rules really matter? What mistakes happen in the midgame? How do you document edge cases? When is a dedicated tracker actually better than Excel?

Soullinktracker delivers both. Public pages explain rules, differences, and workflows. The tracker then turns that knowledge into a usable system, so you spend less time debating and more time making good decisions.

Challenges a good tracker solves

Real problems often only appear mid-game. Good preparation solves them before they turn into arguments.

Encounter chaos after multiple sessions

You continue the run on different days, talk through updates in chat, and suddenly disagree on whether a route is already spent.

A clear status per area stops memory from becoming a rules decision. This makes the run fairer and reduces discussions.

One loss destroys more than one Pokemon

In a Soul Link Challenge, a death is never isolated. It can affect your partner, your team structure, and your planned type coverage.

The connection must remain visible at all times. Good documentation instantly reflects which chain is affected and which backups can replace it.

Spreadsheets don't know the rules

A spreadsheet stores data but doesn't think along with you. It won't warn you if you mix up team, box, and graveyard, or if a pair no longer makes strategic sense.

A specialized workflow is better because it separates states clearly, leaving less room for avoidable mistakes.

Team planning fails without context

Many runs fail not due to a lack of Pokemon, but poor role distribution. Two offensive pairs might look strong on paper but collapse due to shared weaknesses.

When you evaluate typing, backups, and existing links together, planning becomes calmer and panic choices become less common.

How an organized run works

The real value of a tracker isn't visible when creating the run, but between battles-when you can actually use the information you've collected.

01

Set rules before starting

Both players agree on the game, variants, and edge cases. Documentation only makes sense once you know how to handle gifts, static encounters, or duplicate clauses.

02

Record immediately

Mark encounters right after a catch, failure, or skip. It's a simple habit that prevents later mistakes. Delayed entry always creates uncertainty.

03

Review links and team state

When new pairs are formed, don't just check the link-check if the pair fits the team structure. That's the difference between a list and actual planning.

04

Rebuild calmly after losses

When a link breaks, you need immediate visibility into backups, box state, and remaining types. A clean tracker speeds up this reset and keeps the run playable.

If you want to read through this workflow first, start with How to play Soul Link and then fill in the edge cases through the FAQ.

Why many teams eventually leave Excel

Excel, Discord, and screenshots work at the start. But once the run spans multiple sessions, box management, and broken links, they become a liability.

🔗

Links stay understandable

Every Pokemon is visibly connected to its partner. When a status changes, your team instantly sees which link is affected and what decisions follow.

📍

Routes are tracked clearly

In longer runs, it is easy to forget which area is already spent. A clear encounter state prevents arguments and avoids accidental rule breaks.

🧾

Box, team, and graveyard stay separate

Spreadsheets often mix active Pokemon, dead pairs, and viable backups. The tracker keeps those states separate so decisions remain clear.

📊

Type analysis instead of guessing

A Soul Link run rarely fails because of one bad fight alone. More often, both teams stack the same weaknesses. The type view makes that risk visible.

🛡️

Both players see the same state

When partners track progress separately, the run gets messy. A shared view cuts down on misunderstandings and wasted time.

📜

The run remains readable

This matters beyond the current session. A clean history shows which pairs worked, where the run collapsed, and which rules held up in practice.

Useful without an account

A tool should be useful even without signing up. That is why the guides and reference tables are open to everyone.

Who is behind the project

About the projectLegal notice

When to start where

Read the guides first if you want to understand rules, variants, or team logic.

Go directly to the tracker if your rules are already set and you want to document a shared run cleanly.

For edge cases, the FAQ and the tracker guide are the best next steps.

🔗

Understand first, then track

If you only want to learn the rules, start with the guides. If you are already in the middle of a run and need a clean workflow, jump straight into the tracker.

Create a runOpen step-by-step guide