18+ archive guide
Banned from Equestria Endings: Track Routes Spoiler-Free
Quick answer
The game runs on a limited three-day structure with day and night actions, so missed slots and unrecorded choices are the usual reasons a route fails. Track what you did, not what a guide says you should feel, and label endings yourself instead of chasing spoiler lists.
Why route tracking beats a spoiler list
Quick answer
A spoiler list tells you the destination; a run log tells you why you did not get there. The game's limits are time, gated choices, and version-specific content, and a log makes those visible without describing explicit scenes.
Most route failures are mundane. You spent a day slot on an action that did not advance the character you wanted. You missed a night-only trigger. You assumed a scene existed in 1.5 because a guide was actually describing a fan-extended Android build.
A run log records those decisions in order. After one ending, you can compare the log with the result and change one variable at a time. That is more reliable than restarting from a video and hoping the same clicks line up.
This guide stays structural. It does not publish explicit scene text, and the tracker asks you to use your own labels. That keeps the page useful without turning it into a spoiler gallery.
How the three-day structure works
Quick answer
The game advances through three in-game days, with day and night actions and limited opportunities. Some choices are gated by items, money, tickets, or prior interactions, so the order of actions matters.
The exact number of actions per day is a property of the build, not a universal rule. The safe approach is to treat each day as a small budget and record what you spent it on. If a guide says "do X first", write down whether X was available and what it displaced.
Night actions are the usual source of disagreement because a guide may assume a trigger you have not seen. Record the state before the night slot: items, money, and who you last interacted with. That context is what makes a failed attempt diagnosable.
| Resource | Why it matters | What to record |
|---|---|---|
| Day / night slot | Actions advance time | Which slot you used and what it changed |
| Items and money | Some routes need a trigger | What you had before the choice |
| Character contact | Routes depend on prior meetings | Who you met and when |
| Version | Scenes differ across builds | Build label and language |
| Save state | A bad branch can be retried | Where you saved or restarted |
What to record after each slot
Quick answer
Record four things: the slot, the action, the state before it, and the visible result. Keep it short. A log you actually maintain is better than a perfect template you abandon.
Do not write explicit scene descriptions. A short functional note such as "met X, gained item, night unlocked" is enough to reconstruct the decision later. It also keeps the log safe to leave on a shared device.
If you are streaming or sharing screenshots, the log is a better artifact than a scene capture. It shows route logic without exposing adult material.
- Slot: day number and day or night.
- Action: where you went and what you chose.
- State: items, money, and the last character interaction.
- Result: new scene, new item, route flag, or nothing visible.
- Version: build label and language.
- Question: what you would try differently next time.
Open the run log
Quick answer
The log below stores entries in your browser's local storage. It never uploads them. Add a label, a day, a route note, and an outcome; export a copy when you are done.
Use one entry per attempt, not one per scene. A run is a sequence of choices that ends in an outcome. If you restart from the middle, add a new entry and note where you branched.
Export the log before clearing browser data. The export is a plain text or JSON file you can keep with your notes. It does not contain game files or account data.
Interactive tool
Spoiler-light run log
Entries stay on this device. Use neutral labels; do not paste explicit text.
Entries stay in this browser.
Version differences that break guides
Quick answer
Alpha 1.5 English, Spanish 1.5, Android 1.6 and Halloween/Forever are not interchangeable for route advice. A guide written for one build can describe a scene, menu label, or gate that another build does not have.
The final creator build is Alpha 1.5. Spanish 1.5 is a translation of that build, so the structure should be close, but translated labels can differ from an English guide. Android 1.6 is a fan-extended package with extra scenes; a guide for 1.5 may not mention them, and a guide for 1.6 may assume content you do not have.
Halloween is the seasonal build that Pokehidden's archive also labels Forever. It is not a numbered sequel. If a route guide says "Forever", check whether it means the Halloween build or is inventing a new main-line version.
Before following a route guide, write the build label at the top of your run log. When a choice does not appear, check the version before assuming you missed a step.
A spoiler-light replay plan
Quick answer
Finish one run without a guide, log it, then change one variable per replay. That preserves discovery and gives you a controlled comparison instead of a checklist of scenes.
- Play the first run without a route guide and log each slot.
- At the ending, write a neutral label and the choices you think mattered.
- Pick one variable to change: an early action, a night slot, or an item purchase.
- Replay from the earliest point that can change that variable.
- Compare the new log with the first; keep the difference, discard the noise.
- Only consult a guide when a specific gate is unclear, and note the guide's version.
This method is slower than following a full checklist, but it produces knowledge you can reuse. It also avoids the common trap of copying a video route that was recorded on a different build.
If you only want to see one ending and move on, that is a valid way to play. The tracker is optional. The important part is not to treat a spoiler list as a requirement for enjoying the game.
FAQ
How many endings does the game have?
The game has multiple endings tied to routes and day progression, but the count depends on how a guide defines an ending and which build it covers. This page does not publish a definitive count.
Can I track routes without spoilers?
Yes. Record slots, actions, state, and visible results in neutral language. Avoid scene descriptions and let the outcome stay unlabeled until you see it.
Why did a choice not appear?
Check the build label first, then the state before the choice. A missing item, a spent slot, or a fan-extended build can all explain it.
Does the run log upload my notes?
No. It uses browser local storage and an optional local export. Nothing is sent to this site.
Will clearing browser data delete the log?
Yes, if the log is stored in local storage for this site. Export a copy before clearing site data.
Sources
The three-day structure and version context come from this archive's walkthrough and version pages. The Forever alias is documented on Pokehidden's archive.