Testers needed for new BDB Project’s game: Plague on the Discovery. (Morgan Tyler series #3)

Good morning. Here we go again.

With the present game, we are delving deep into Morgan Tyler’s saga, with our hero now on a Search and Rescue mission in outer space. In this episode, Morgan will board the Discovery, an exploration ship now adrift near the asteroid belt, to find out how and why it disappeared and what happened to its crew.

This time the game ranks as “difficult” due to the presence of timers right at the beginning, so the expected playing time is, again, a couple of hours (a little bit more for an in-depth beta test). Map and solutions will be provided. Also, please note that the game has already undergone 3 rounds of testing, so there shouldn’t be major issues to find and fix (hopefully). As usual, it is written in PunyInform, so you’ll need a Z-code interpreter.

All of the games in the saga are self-contained, so it’s not necessary to have played Eclipse and The Cursed Planet before this one.

I’m particularly looking for feedback on:

Does the story make sense within the context of the game?

Spelling and grammar errors. (The games are in American English, but UK English spelling should be accepted in commands.)

Are the puzzles well hinted, too easy or too hard?

Was there anything you tried that should have been accepted, but wasn’t?

Is all scenery implemented?

Bugs, of course.

Anything else you think of.

If you can help out with the game, please send me a personal message, and I’ll get it to you a.s.a.p.

As said, the game comes with a map and a walkthrough, in case you are stuck or you don’t have too much time to spare. The tentative release window is Sunday, October 4, 2026 (two weeks from now), so I’d really appreciate if you could get back within a week.

EDIT: Please note that the game will be renamed “Plague on the Discovery” instead of “Star Plague” to avoid confusion with the original game from BDB.

3 Likes

May I assume that there will not be a transcript option?

You can use SCRIPT ON to enable it.

And type an asterisk at the start of a command to leave a comment in the transcript. Doing so will avoid a parser error.

I think transcript support depends on your interpreter. All the modern interpreters support it, but I’m not sure about the retro interpreters if you were thinking of using something like (say) Apple II or Atari 8-bit.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.