Banned From Equestria Endings: All Routes Guide
This Banned From Equestria endings guide compares normal, good and secret Day 4 possibilities with separate saves, without confusing Alpha 1.5 and the community Android 1.6 package.
Ending route checkpoint plan
The safest route is a controlled replay plan: identify the build, save before each major choice and record what changed.
| Ending path | What to preserve | Best use |
|---|---|---|
| Normal ending | A clean early save | Learn the three-day loop |
| Good ending | Quest items, bits and relationship choices | Test the strongest route |
| Secret Day 4 | A save before the final night | Verify optional triggers |
| Community 1.6 | A separate install and save set | Compare packaging differences |
What counts as Banned From Equestria endings
This Banned From Equestria endings guide uses the game's short three-day structure, so an ending is usually the result of several earlier choices rather than one final dialogue option. The normal ending is the baseline ending, while stronger or hidden endings depend on completed objectives, route access, spending decisions and the state of your save.
Treat “all routes” and “all endings” as connected but different tasks. A route follows a character or objective; an ending records the state reached when the time limit closes. This page focuses on repeatable ending checks instead of explicit scene descriptions.
Build a three-save checkpoint system
Use this Banned From Equestria endings guide with one save near the beginning, one before the final day and one before the last night. Keep the files separate and name them outside the game if your Ruffle or Android wrapper does not expose clear labels. This prevents a failed experiment from overwriting the only route that still works.
On the first run, learn movement, shops, travel costs and time gates. On the second, reserve bits and key items for the route you are testing. On the third, change only one major decision at a time. A small decision log is more reliable than copying a video made with another build.
Normal, good and secret Day 4 checks
Use the normal ending as a control run: avoid late optional detours and note which quests remain incomplete. For a better ending, complete the route prerequisites earlier, keep enough bits for required travel or purchases and revisit locations after day/night transitions.
Secret Day 4 claims need extra caution. Save before the final night, verify that optional objectives are complete, then compare the ending state with a clean Alpha 1.5 reference. If a guide shows extra content only in a community package, label it as package-specific rather than proof of an original hidden ending.
Version and device differences
Checked November 5, 2026: the BFE-Spanish itch.io download listing exposes BFE 1.5 (Executable) at 23 MB, BFE 1.6 (ANDROID).apk at 60 MB and BFE 1.5 (SWF).swf at 21 MB. The listing is the source page for this guide; this check did not confirm a stable direct file URL or a newer release.
Use Alpha 1.5 as the historical reference for walkthrough notes. Keep Android 1.6 in a separate install because a wrapper can store saves, focus and storage differently. Never treat a competitor's 1.6.5 label as proof of an official build, and back up every save before moving between Ruffle, Windows and Android.
Troubleshooting a missing ending
If an ending does not appear, first confirm the exact build, then reload the pre-final-night save and check time, bits, quest items and location transitions. A missed prerequisite often happened earlier than the visible failure point.
Use the general guide for the complete three-day loop, gameplay for controls and economy, and the versions page before following any download-specific walkthrough. The Celestia and Big Mac pages cover narrower route or hidden-trigger questions.
All endings checklist: run order, saves and evidence
A reliable all endings run starts with the build, not the final dialogue. Write down whether you are using the preserved English Alpha 1.5 SWF, the community Windows package or the Android 1.6 listing. Record the file name and platform beside each save. If a result differs from a guide, this small note tells you whether the difference is a route mistake, an emulator state or a package change.
Use three checkpoint saves. Keep a clean slot near the start of Day 1, a second slot before the final day and a third immediately before the last night. Do not overwrite the clean slot after testing an optional trigger. Name copies outside the game when the wrapper uses generic save labels. A controlled replay is faster than restarting because one late experiment erased every earlier route.
During the first run, make a simple route log rather than chasing the best ending. Mark the character or objective, the time phase, the item or Bits cost and whether the scene consumed time. A scene that looks complete may still need a follow-up visit after sleep. The log also separates six qualifying outcomes from bonus scenes that unlock content but do not change the ending grade.
For the normal ending, let the three-day clock finish with a clean save and note the farewell. For a better ending, complete distinct route endings early enough to leave time for night-only steps, keep a Bits reserve and revisit locations after phase changes. Change one major decision per replay. If you buy an item, skip a night trigger and change a dialogue choice in the same attempt, you cannot tell which condition mattered.
Day 4 and Sudden End checks belong in a separate experiment. Community notes describe rewind- or pause-dependent methods that were written for standalone Flash players. Ruffle and Android wrappers can handle old state differently, so label a failed attempt as version-sensitive rather than as proof that the route is fake. Save before the last night, test once, then return to the clean Alpha 1.5 run.
Before Day 1, finish one ordinary run so you know that the map, input focus and save restore work. Reserve early Bits for required travel or purchases; optional shopping can wait. Keep the build label beside the save and reject a guide that promises every scene without naming its source.
Before the final night, check the calendar, Bits reserve, required items and unfinished objectives from the clean slot. Revisit a location in both phases when a trigger is described as night-only. Copy the save before a good ending or secret continuation and change one variable at a time: a scene outcome, an item order or a travel visit.
When a trigger is missing, reload the pre-final-night save and confirm the exact package. Check phase, route count, inventory, Bits, transformation or book flags and travel order. Switching emulators should be the last test because it changes the state you are diagnosing. If a community result never appears in Alpha 1.5, mark it as package-specific and use the versions page instead of an unverified mirror.
Checkpoint rules
Keep the clean slot untouched, keep an experiment slot for optional triggers and write the build beside both. This turns a vague spoiler report into a repeatable test.
A route log is most useful when it records time phase, cost and whether a scene consumed a day. It prevents a bonus scene from being counted as a new ending.
- Build and platform beside the save name
- One clean slot kept untouched
- Day and night locations marked on the route log
Version-aware Day 4 testing
The Day 4 and Sudden End notes are historical, not a promise that every player can reproduce them. Old Flash rewind and pause state may not survive in Ruffle or Android.
Use a copied save, note the player and package, and return to Alpha 1.5 for the normal ending route. A failed experiment is useful evidence when the version boundary is recorded.
- Save before the final night
- Test one method once
- Label community additions separately
Recovery when a route fails
A missing ending usually points to an earlier prerequisite. Recheck the day, night, item, Bits and travel sequence before blaming the final dialogue.
If the same clean save fails twice on the same build, document the package and consult the versions page. Do not install a random mirror just to force a checklist result.
- Finish one normal three-day run first.
- Track unique qualifying outcomes instead of repeating one route.
- Keep Alpha 1.5 and community 1.6 saves separate.
- Treat Day 4 as an optional, version-sensitive experiment.
- Use the final-night save to reproduce a missing trigger.
- Record the source and build whenever a guide disagrees.
Banned From Equestria Endings: All Routes Guide FAQ
How many endings does the Banned From Equestria endings guide cover?
This Banned From Equestria endings guide keeps labels separate because public guides mix route endings, hidden scenes and community additions. Track normal, improved and secret Day 4 endings by build instead of trusting one universal count.
How do I get a better ending?
Save early, complete route prerequisites before the final night, preserve enough bits for required actions and change one major decision per replay.
Is there a secret Day 4?
Some guides describe Day 4 or hidden continuation conditions. Verify the claim against Alpha 1.5 and keep community 1.6 additions clearly separated.
Can I use the same save on Android and PC?
Do not assume compatibility. Back up the original save and test a copy because Ruffle, Windows builds and Android wrappers can store data differently.
Which version should I use for an endings walkthrough?
Use Alpha 1.5 as the historical reference. Treat community Android 1.6 behavior as package-specific when it differs.
Should I count bonus scenes as endings?
Keep bonus scenes in a separate column. They may unlock a route or an item without changing the three-day farewell, so a checklist should distinguish route progress from the final ending state.
Why does Day 4 work in one player but not another?
Historical Day 4 notes rely on old Flash rewind, pause and scene state. Ruffle, desktop Flash-compatible players and Android wrappers can expose different behavior; label the attempt by build and keep the save isolated.
Where should I report a version mismatch?
Record the package, platform, file name and save checkpoint, then compare the verified itch.io listing and the versions page. Avoid presenting an unverified mirror or a competitor label as official evidence.