Undying Fortress - BETA TESTERS LAST CALL

Wield your magic sword against the undead that fill a mysterious tower, and uncover the secrets of the past!

Undying Fortress is a dark epic fantasy interactive novel by Yeonsoo Julian Kim, author of The Fog Knows Your Name.

For centuries, a mysterious fortress has floated above the kingdom of Serendal. Now it has fallen - and all of its secrets, treasures, and monsters are within reach.

You have fallen too: after expulsion from the Imperial Academy cut short your studies as an aspiring knight-scholar, you turned to the life of a mercenary. Wielding your family’s legendary blade Wicked Fate has won you a certain degree of fame and fortune - but now the ancient fortress presents the opportunity to climb much much higher.

Enter the tower with a motley group of companions: fighters, spellcasters, and thieves; former friends and mentors from the Academy; even a prince of the realm. Within lie countless skeletons, shambling Afflicted, ferocious flying creatures cobbled together from bones, and more, all commanded by the fearsome Carrion Mother, an ancient deity long suppressed by Serendal’s rulers. Fight off undead monsters to protect Serendal; or learn to wield forbidden mortuary magic and get the creatures to do your bidding. Uncover ancient secrets that may shake the realm to its core, or keep them hidden and become the power behind a new throne. Win glory with your magic sword and prove that you are worthy of knighthood - or just gather treasure to come out of this the wealthiest mercenary who ever lived.


Email us, beta AT choiceofgames for access.

DO NOT POST ASKING WHAT THE BETA EMAIL ADDRESS IS. The first test to becoming a beta tester is inferring what it is based on how we describe it above.

Do not send DMs/PMs through the forum mail system, Discord, text message, carrier pigeon, or any other method than email.

When you send your EMAIL, include:

  • the game you want to test in the Subject line of the email.
  • your forum-name
  • your real name (first and last). Please indicate if your family/surname comes first as well. Beta testers’ names are listed in the game’s credits, which are accessed with the “About” link you’ll see within the game. If you don’t want to appear in the credits, or you want to be credited under a name other than your real one, please let us know.

Do not email us multiple times about joining a beta. If you don’t email us as soon as we post a beta, you go into a queue. As we post new drafts, we admit more people from the queue. Eventually, we will get to you. Some beta processes last longer than others, and it may take up to a few weeks to reach the front of the queue.

When you have been admitted to the beta, we will send you a link, a username, and a password as a reply to your email.

When you have feedback to submit:

  • Return feedback as part of the same email thread where you were admitted. Copying beta@choiceofgames on that email is the best way to make sure your comments are seen as soon as possible.
  • Please send screenshots or copy/pasted quotes whenever you can; it helps us track down whatever observation you’re making. In particular, the author may see things that you don’t, and/or the screenshot may contain more information than you realize.
  • If you’re sending multiple screenshots/comments, please combine them into a single email. One email with five screenshots is much easier to manage than five emails with one screenshot each.
  • If you’re submitting feedback using the Bug/Submit button in the game, make sure you include your handle/name in the body of the email. The Submit button obscures your email address, and I can’t give you credit for feedback if I don’t know who you are.

A few more notes:

  • You cannot be testing two games at once. If you are already testing one game, send in feedback on that game before you apply to another. If you apply for multiple games at the same time, you will likely be admitted first to whichever game has testing slots open up first, and we won’t be able to admit you to the other one until you send in your comments for that one. (From an admin standpoint, it’s easiest if you don’t apply to more than one game at once – applying to multiple games makes it more likely that we’ll miss admitting you to one of them.)
  • If you’re admitted as a tester but realize you won’t be able to send in feedback for that game, please let us know! You won’t be penalized in any way - we’ll just take you off the list of testers for that game. But if you sign up to test a game and don’t send comments or withdraw, it will affect your chances of being admitted to future betas.
  • There’s no standard length of time for a beta testing period to last, and we usually don’t know exactly how long a game will be in beta when it opens. The best way to know how long a beta will be open is to follow the thread for updates.
  • It’s fine to send multiple feedback emails, but if you have a lot of quick comments, it’s easier to keep track of them if you bundle them into one email.

Tips on How to Give Feedback
We’re looking for “high level” and “low level” feedback. Not mid-level feedback.

Low-level = typos and continuity errors. A continuity error is when a character’s gender flips, or someone comes back from the dead, or you run into a plotline that just doesn’t make sense (because it’s probably a coding error). For these low-level issues, screenshots are very helpful. If you see a problem, take a screenshot, or copy and paste the text that is in error, and email that.

“High level” feedback has to do with things like plot, pacing, and characters. “Scene A didn’t work for me because x, y, and z,” is useful feedback. “B character was entirely unsympathetic, because u, w, and v,” is also useful feedback.

“Mid-level” feedback describes things like grammar, style, word choice, or the use of commas. As I said above, I do not want mid-level feedback. In particular, DO NOT WRITE TO ME ABOUT COMMAS.

“I had a great time and saw only a few spelling errors,” is not useful feedback. In fact, it’s the sort of thing that results in you not being given access to future betas.

Some examples of useful feedback :

  • In Choice of the Dragon, you get to choose what type of wings you have: leather or scaled. Someone wrote in and asked about having feathered wings. Great suggestion! Done!
  • In “The Eagle’s Heir,” someone asked about Eugenie. They said that the romance moved too quickly–because she only appeared in the last third of the game–and wished they could have had an opportunity to meet her earlier. So the authors added an opportunity to meet her and start the romance earlier in the game (in a scene that already existed).
  • In “Demon Mark: A Russian Saga” several people commented on how the PC’s parents were unsympathetic, so the authors added a choice or two to deepen the relationship with the parents in the first chapter, to help better establish their characters.
  • Pointing out a specific choice and saying, “this is who I imagined my character was at this particular moment, and none of these options seemed right for me. I would have liked an option to do X instead,” is also really helpful feedback.
  • If you choose an #option and then the results of that #option don’t make sense. Like, if you thought an #option might test one stat, but it seems to have tested a different one.
12 Likes

New draft!

Changelog:

  • Assorted typos fixed and confusing wording clarified

  • The object belonging to Sanha found in Ch 4 stays a hairpin and does not turn into a comb.

  • Fixed an obscure but potentially game-breaking bug in Ch 10 (the real reason for the new draft!)

This is version 68254

2 Likes

New draft! Changelog includes:

Fixed assorted typos and confusing bits of wording

Stat bars for relationships and goals now correctly appear on the stats page when the respective NPCs and goals get introduced

Ch 2: smoothed out continuity about the PC’s past interactions with Kuho

Ch 9-10: fixed (I hope!) continuity about where the tower is, and what the status of the army is (including fixing a bug in which they disappeared entirely!)

Fixed a bug where the PC ends Ch 10 trapped in the Pale but starts the epilogue somewhere entirely different.

This is version 68281

1 Like

New draft!

Lots of small clarifications and minor continuity issues

Ongoing bug-squashing in the epilogue! Most notably:

  • smoothed out the continuity of who is talking to whom in the assembly scene
  • further ensuring that no text gets skipped
  • made sure that Captain Rhoe is not leading her own funeral procession

This is version 68323

3 Likes

New draft!

Changelog includes:

  • Dilis and Hani’s stat bars now appear when they are introduced
  • A couple more opportunities to berate Kuho for his terrible decisions, and one of his decisions is now less terrible (he no longer willingly begs the Pale to bring him to Sanha after you’ve saved him)
  • Improved continuity in Ch 3 about what the PC knows about boneweaving and when
  • Expanded range of interactions with Eredith and Sef, and better continuity about what they’re able to do at the end of the game.
  • In Ch 9, the conversation about who’s going to guard Vartell no longer happens right in front of them
  • More references to the army of farmers when you’re fighting the Carrion Mother

This is version 68401

3 Likes

New draft!

Changelog includes:

  • Chapter headers! Aren’t they pretty?
  • Streamlined stats page
  • Fixed the usual collection of typos, minor code errors, and minor confusing bits
    added a few page-breaks to break up walls of text
  • Ch 10: smoothed out the flow of the conversation with Hani about Dilis; fixed some bugs that resulted in Dilis randomly dying, then occasionally returning from the dead
  • Epilogue: fixed some bugs that resulted in duplicate and/or omitted endings to conversations with ROs

This is version 68450

2 Likes

New draft!

Fixed a few assorted typos; but more importantly, fixed an obscure but potentially crashing bug in the epilogue.

This is version 68517

1 Like

New draft! Notable changes include:

  • Huge recalibration of stats and checks! It should now be easier to do just about everything, especially bargaining with the Carrion Mother, saving Kuho in the Pale, and everything to do with Hani

  • Tura no longer appears in the epilogue unless you’ve successfully bargained with the Carrion Mother, which explains why her scene had missing text before

Plus correcting the usual assortment of typos.

This is version 68584

2 Likes

New draft! No major changes; just caught one of those ‘hard to find, but if you do it’ll crash’ bugs.

This is version 69092

1 Like

New draft! Changelog includes:

The usual assortment of corrected typos and clarifications

Ch 1

  • A couple of subtle hints added as to what is really going on with Vartell
  • Expanded Silver Arrow dialogue about their role in the community
  • An additional choice about the PC’s physical features
  • Fixed an incorrect reference to character age

Ch 2

  • A little more description added during the journey from Abersong to Taeria
  • Fixed a continuity issue regarding whether Hani knows you’ve been in Abersong all this time
  • You can now give Rylan a chicken leg (never let it be said that we do not pay attention to important issues!!)

Ch. 6

  • More description of interacting with Somi and Tariq if you prioritize helping the Silver Arrow

Epilogue

  • More mentions of Somi and Tariq
  • If Rylan is dead, you can now ask the musician to commemorate Rylan in her epic so that he will never be forgotten
  • You now have a conversation with Kuho about what happened with Sanha if you went against his wishes

LAST CALL FOR TESTERS! This beta will be ending very soon. If you have not yet sent in your feedback, please do so now! If you have already played, now is a great time to play again to see what’s changed.

This is version 61905

2 Likes