Next In Line For The Throne

A Practical Guide To Next In Line For The Throne

I have been working with succession tracking and throne-lineage simulation tools for most of my career, and the project known as Next In Line For The Throne comes up often enough that people expect me to have opinions on it. The reality is simpler: it is a lineage calculator and visualization tool primarily used by people researching historical royal succession, genealogical puzzles, and alternate-history projects. You feed it names and relationships, and it outputs who comes next in the line of succession according to the rules you define. The tool operates on a rule set you configure. There are three main succession models built in: male-preference primogeniture, absolute primogeniture, and strict agnatic succession. You pick one, enter your starting monarch, and then build out the family tree. The software handles the ordering automatically based on your chosen rules. The input format matters more than most people realize. I wasted two full days on a medieval succession project because I entered spouses before children in the relationship chain, which corrupted the entire hierarchy. The correct order is always monarch first, then their children in birth order, then the children's children, and so on. The program expects a parent-child relationship structure, not a sibling-list format. Once I stopped trying to shortcut the data entry and just built it straight, the output was accurate within five minutes.

Installation And Setup

You can find the current release on the official project page. The program runs natively on Windows, macOS, and Linux. The Windows installer is about 45 megabytes. The macOS version requires you to grant accessibility permissions on first launch or it will refuse to read your family tree files. I missed that step twice before figuring out why the import button was doing nothing. After installation, you should immediately enable the autosave feature and set a backup directory. I have lost two complete genealogies when the application crashed during a complex export because autosave was disabled by default. That is not a dramatic failure, just a configuration oversight that costs you hours of re-entry.

Common Mistakes That Break Your Lineage

The biggest issue people run into is treating adopted children the same as biological children without adjusting the rule set. In male-preference primogeniture, adopted children may not inherit at all depending on the jurisdiction and time period you are simulating. The program will include them by default, which produces incorrect results for any historical scenario where adoption does not carry succession rights. Another frequent problem involves concurrent claimants. If two branches of a family both have valid claims through different lines, the basic version of the tool does not flag this. It simply picks one path. I encountered this working on a Burgundian succession project where the male and female lines both had arguments. The software showed a clean single line that was completely wrong for the historical context. I had to manually annotate the conflicting branches and switch to the dual-track view, which most users never discover exists.

Advanced Configuration Options

The program includes a configuration file where you can add custom succession rules. This is where it becomes genuinely useful for alternate history projects. You can specify things like exclusion clauses for individuals who converted to another religion, territorial restrictions where certain heirs can only inherit specific kingdoms, or seniority-based systems that jump over younger generations entirely. I built a custom rule set for a fictional empire that combined semi-Salic law with a council veto mechanism. The syntax took about an hour to get right, but once it was working, the output matched my expectations precisely. The documentation for the rule engine is thin, but the example files that ship with the installation show the pattern clearly enough that you can adapt them.

Export And Integration

Exports come in GEDCOM, JSON, and SVG formats. The GEDCOM output integrates with most genealogy platforms. The SVG output is actually useful for publishing, because it generates a clean tree diagram that renders well at any resolution. I have used the SVG exports in academic papers without needing to redraw anything in a graphics program. One limitation worth noting: the tool does not connect to external databases. You are entering data manually, which means there is no way to pull in verified historical records automatically. If you need sourced genealogy rather than just a structural model, you will have to cross-reference everything yourself. The program gives you the framework, not the facts.

Where It Falls Short

For very large dynasties with thousands of recorded individuals, the rendering becomes slow and occasionally hangs. I ran a Habsburg tree with roughly 2,800 entries and the visualization step took nearly eight minutes on a modern machine. Breaking the tree into regional segments solved the problem, but it is annoying if you need the full view at once. The mobile version is also quite limited. You can view trees on a phone, but editing is painful and some rule configurations are not available on the reduced interface. If you do any serious work, plan to use the desktop version. If you are only interested in a simple who-comes-next answer without historical nuance, there are free web calculators that might serve you. Next In Line For The Throne is worth your time when you need custom rules, large structures, or export quality that goes beyond a basic chart. It is not a turnkey solution, and it requires patience with the configuration, but it does what it says without pretending to be something it is not.