Fire Emblem: Something to Hold On To
By Team Shocking Truth II
[Download Coming Soon – Stay Tuned for Updates]
Current Progress: Finishing final chapters, polishing and playtesting before public release. Project will be released [complete].
About
Something to Hold On To (StHoT) is an upcoming custom FE8 campaign featuring 25 chapters and over 60 playable characters, built in FEBuilder. This hack was built in the “telephone” style, where different developers owned their chapters, building on the plot over time to tell a complete and cohesive story.
The hack features a true “utility” lord, who can do almost anything – except fight directly. Most notably, they have a personal staff that grants them a limited number of refreshes to use throughout the game (plus more unique staves to unlock as you progress).
The hack will likely appeal to old school Fire Emblem fans seeking a stripped down experience with a stronger focus on counting squares and doing math, as well as story-oriented gamers looking for a grounded, political narrative. The hack is designed with ironman and replayability in mind.
Plot Synopsis
Lady Aika of House Bingai ruled one of the many noble houses in the League of Tongsa, an independent nation ruled by a collective of land-owning nobles. The League sits in a frosty mountain range wedged between two greater powers, Edraith and Magedema, on the continent of Thennin.
As a ruler and administrator, Aika is generally regarded as effective. However, not all are satisfied. Her throne is usurped by her younger sister, Touka, and she is exiled to an old shrine in the remote Dagor Mountains. For seven years, she grew to accept and appreciate her new life, writing fiction, reading poetry, and picking up other hobbies with her newfound abundance of time.
Her quiet life is upended when the shrine is suddenly attacked by soldiers from her old noble house. She makes a daring escape into the frozen wastes with only her loyal retainer, her young cousin, a seasoned curate, and a handful of guards. Ousted from her home once again, she finds herself embroiled in a simmering conspiracy that threatens to engulf the entire continent in the largest crisis of her age.
Throughout her journey, Aika navigates a complex web of friends, foes, alliances, and dark secrets. To uncover the truth and overcome these new trials, she must hold on to that which she holds most dear and let go of the things that hold her back.
Development
This is created by the same team that brought you Call of the Armor, Bells of Byelen, Tales of Kotor, and An Unexpected Caller. After the completion of Bells of Byelen, we debated ideas for how to approach another fully custom telephone hack while working on ToK and AUC. There were many ideas and false starts (and definitely some ideas I’d want us to revisit), but eventually we landed on this concept and I took on the lead role to produce the hack.
Our goal was to create something that was more stripped down and challenge ourselves to not stick so strongly to a pre-existing sandbox. While Call of the Armor stuck close to FE8 and Bells of Byelen to FE5, for Something to Hold On To, we leaned into the simplicity of FE6 w/ some FE4 flair, but nothing here is fully 1-to-1 to any existing sandbox as previous hacks were. Our work on An Unexpected Caller showed us we could do good gameplay without a common vanilla game as a touchstone to draw from, and we hope we did it again here. Beyond this, the primary gimmick was creating a lord who has zero combat and has a limited number of dances/refreshes to use (shoutout to knabepicer for doing this). While familiar, the lord’s capabilities, distinct numbers, and EXP curve made the experience fresh to design and play around. The simplicity of the mechanics gave us a lot of room to add complexity, nuance, and texture to the maps, objectives, and narrative.
In addition, we also were more flexible in how we doled out units to make it feel more “organic” versus our past hacks where it was always “two per map”. We even have a rare “zero new unit map” – just like vanilla!
Narratively, we wanted to focus on a more “grounded”, political story. This would prove to be the biggest challenge working in a large team, tracking all of the various factions and ensuring intent was captured chapter-to-chapter made for good debate on how to best proceed throughout while also balancing individual developer vision and preferences.
This hack took a lot longer to build than initially hoped. We started at the end of 2023 and there were many long hiatuses in between. Much of this is a consequence of the times and how much our group has aged in the past 5 years since our four month blitz to crank out Call of the Armor. Like An Unexpected Caller, we used the interludes as break points to go back and polish the previous set of chapters to ensure they were in strong condition before moving forward.
That said, I think the extra time in the oven helped improve gameplay and give us more time to edit both story and gameplay. There were long stretches where nothing happened, and others where we moved quickly. We didn’t try to force it, and many of us had other commitments to work on throughout this development.
In addition, we stuck less to the traditional telephone format and worked more collaboratively. While some chapters were solo-led, others involved duos to split up duties, usually with one person directing and the other person supporting. Often this was a gameplay/writing split, which helped us each lean into our strengths as designers more while giving everyone a chance to “own” a chapter and direct where the story went. In addition, as lead, I played a more active role in editing the hack’s narrative and gameplay to ensure stronger cohesion to make the hack feel less “uneven”, as it can tend to in hacks like this where everyone has different approaches to design and chapter writing. Throughout the hack’s development, it was not uncommon to see different team members take charge to build and support different aspects of development outside the chapters they are credited for. Later in development, team members took on lead roles in different areas to ensure a level of consistency and quality across different gameplay and visual elements, such as Levin editing portraits and RandomWizard updating everyone’s maps.
The various iterations of this team has produced a total of five hacks together now, and while each has their merits, I think Something to Hold On To is the most cohesive end-to-end. The writing, aesthetics, and gameplay, while made by many hands, feels more unified than our past hacks. We focused on executing the fundamentals well while adding a bit of flair to keep it fresh.
This was not only true for the game itself, but how we went about building it. The benefit of working together with a seasoned team is that there is a high degree of trust, as well as a willingness to compromise and iterate on ideas, which I feel ultimately helped us make a better product.
I know the team and I enjoyed working on this and are proud to share it (soon!). We hope you enjoy it.
Gameplay Changes + Features
- 25 chapters; fully custom self-contained story with over 60 units to choose from.
- Mechanically simple gameplay with an emphasis on old school positioning and number crunching.
- Lord with custom PRF staves focused on refreshing.
- Many custom items and weapons, including those inspired by classics such as Gant Lance and Al Sword.
- Elibe-style item-based promotion, modified to suit the needs of the game’s cast, such as a “Rider Whip” that works for cavaliers, pegasus knights, and wyverns.
- Mono-weapon cavaliers and armors; with an overall class list inspired by FE6 + FE4 (playable Ballistician included).
- Slowed down EXP gain + adjusted formula to account for the game’s length and desired difficulty.
- Objectives from across the series and new ones to explore.
- Three Tear Ring Saga inspired interludes where you can select two of six units to join your team.
- Universal 30 class caps for all promoted classes.
- One difficulty mode, which we estimate is more difficult than the median vanilla “normal mode”, but not always as difficult as the median vanilla “hard mode”.
Team Shocking Truth II Staff
Project Lead and Producer
Pandan
Chief Artist
Levin64
Chief Map Aesthetician
RandomWizard
Chief Musician
RandomWizard
Chief Wizard
knabepicer
Chief of UI
Citrus
Chief Writer and Editor
Pandan
Chapter Developers
LegendofLoog
knabepicer
Parrhesia
Leche
Roze
Knight_Moris
RandomWizard
Rivian
bpat
Kyrads
GodsPetTurtle
MournfulRelic
Citrus
Contributors
DrGreen3339
Levin64
Archerbias
hypergammaspaces
Ditto
sdaht
Devisio
Chapter Credits
Note that many chapters feature edits or contributions from others on the team, those listed were responsible for the bulk of the original gameplay, narrative, etc.
Ch1: Pandan
Ch1x: Pandan
Ch2: LegendofLoog
Ch3: bpat
Ch4: knabepicer
Ch5: Roze
Ch6: Knight_Moris
Ch7: Parrhesia
Ch8: Kyrads
Ch9: Pandan
Ch9x: Pandan
Ch10: Rivian
Ch11: MournfulRelic
Ch12: Citrus
Ch13: GodsPetTurtle and Parrhesia
Ch14: Pandan and Parrhesia
Ch15: Kyrads
Ch16: bpat
Ch17: Parrhesia
Ch17x: Pandan
Ch18: LegendofLoog
Ch19: RandomWizard
Ch20: Leche
Ch21: Leche and Pandan
Ch22: bpat and Pandan
Ch23: Kyrads
Ch24: RandomWizard
Endgame: Roze
Credits
Coming soon (don’t worry we have them on a spreadsheet)
[Download link to go here when ready]



















