Ironheart - BETA TESTERS NEEDED

Ironheart, by Lee Williams

When your space mission goes awry you find yourself crash-landing back on earth…but centuries in the past! You must deal with the disrupted timeline your own crash caused: you’re in the 12th Century and technology includes stories-tall mechs! How will you survive, smack in the middle of the Crusades?

Directions for beta-testing:
Email us, beta AT choiceofgames for access. (THIS HAS CHANGED.)

  • Do not send me DMs/PMs through the forum mail system, Discord, text message, carrier pigeon, or anything 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) — if your family/surname comes first, please indicate that. I will assume that your given name is listed first unless you tell me otherwise.

  • 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.

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 to beta@choiceofgames.com, preferably part of the same email thread/chain, rather than a new one.
  • Please send screenshots or copy/pasted quotes as often as 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 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.
    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 the above paragraph.

Lastly, you cannot be testing two games at once. Send feedback on one and you can apply to another.

Tips on How to Give Feedback
I’m 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.

Similarly, 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.

Another useful piece of 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.

18 Likes

We’ve had enough responses that we’re going to hit pause on admitting new testers for a bit. Once some of the current testers have submitted their feedback and there’s a new draft of the game, we’ll invite new testers in. Thanks to everyone who has signed up so far!

8 Likes

New draft posted! Remember to clear your cache or play in an incognito window: look for v 18817 on the About page.

  • heaps of small catches and alterations
  • a good deal of fleshing-out of choices concerning the PC’s religion and ROs…
1 Like

New draft posted. Remember to clear your cache or play in an incognito window: look for v 18829 on the About page.

  • Typos in Prologue and Glossary fixed
  • Made the game much more reactive to player religion throughout
  • Caught one huge bug which meant the player would still sometimes be treated as the owner of their fief even after losing or ceding it

New draft posted. Remember to clear your cache or play in an incognito window: look for v 18858 on the About page.

  • All typos and stats screen issues reported so far are fixed.
  • ROs should now be generally much easier to access.
  • There are now more building options during fief management (and some options, like irrigation and defence, have more than one level) so you should never now run out of things to build.

New draft posted. Remember to clear your cache or play in an incognito window: look for v 18906 on the About page.

Lots of changes in this draft. If you played once and found it unsatisfying/buggy, now is the time to try again.

  • More stat balancing.
  • Many continuity errors fixed.
  • More NPC interactions and conversation options throughout.
  • Broken RO (Ygraine) now fixed.
  • More nuanced approach to allegiance and diplomacy.
5 Likes

New draft posted. Remember to clear your cache or play in an incognito window: look for v 18947 on the About page.

  • All romances overhauled.
  • New content available for players who want to discover more about the time travel aspect of the story.
  • Options to make cosmetic improvements to your archon.
  • Relationship stats now viewable on stats page.
  • Glossary now updates as content is discovered.
  • New endings available.
  • Several large bugs fixed.

New draft posted! Remember to clear your cache or play in an incognito window: look for v 18977 on the About page.

  • Continuity error for death of Louis fixed
  • Mongols continuity error fixed
  • Ch 9 test issue fixed
  • Many other small tweaks to balance the game

Thanks to everyone for their feedback! The beta is now closed.

1 Like