Witchcraft U - BETA TESTERS NEEDED

Cast spells, enlist the aid of the spirit world, and earn the respect—or rebuke—of a secret society as a first-year magical studies major with a chequered past in this dark academia game of horror, crime, and intrigue!

Directions for beta-testing:

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 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. Send feedback on one and you can 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

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.

19 Likes

New draft up, v24694! Changelog:

  • inserted chapter/stat headers

Ch. 1

  • deleted repeating passage

Ch. 2

  • inserted missing lines of text

Ch. 5 & Ch. 6

  • fixed romance/invitation code & multireplace issue

Ch. 7

  • addressed autoroute to History class

  • fixed ness_outcome multireplace issue

2 Likes

New draft, v24725! Changelog:

  • created subroutine to limit decimal places savings display
  • fixed loanamount issue

Ch. 7

  • fixed adminmeet multireplace code
1 Like

New draft! Changelog includes:

  • semester GPAs should display at start of each term; cumulative GPA if player makes it through the year
  • Ch. 2: firstpaycheck display bug squashed
  • Ch. 7: smushed gamebreaker bug (invalid @{}/date multireplace error)

This is version 24734

1 Like

New draft! Changelog includes:

  • removed repeating line on stats page
  • fixed some multireplace errors
  • fixed ness_outcome bug in ch 7
  • KISSING ENABLED in ch 6!

This is version 24752

2 Likes

New draft! Fixed some small but important bugs, including:

  • fixed skey_liminalia bug
  • Ch. 3: fixed autoreroute to Ness-spell scene
  • Ch. 5: added thaumaturgy option to third trial

Coming soon: lots of story edits!

This is version 24756

1 Like

New draft, v24812! Changelog:

  • spelling/spacing/grammar fixes
  • money should display correctly
  • GPA no longer abysmally low all the time

Ch. 3

  • fixed costume cost discrepancy

Ch. 5

  • removed extra grayed-out “Buy them now” options
  • addressed class schedule code errors
  • fixed autoreroute to Buyan scene
  • fixed autoromance code issue

Ch. 7

  • made initiation scene accessible!
  • fixed society bug

Ch. 8

  • fixed class schedule code errors
  • closed autoreroute to Poppy journal scene

Ch. 10

  • fixed MLF flyers code bug
1 Like