Monster Miners · Alpha · round r18

Tester Checklist

New build 2394 round is up. Most of this round is me fixing what you four found last time, so section one is short and it is the one that matters.

Night on your plot and around the hub is lighter. Three of you said it was too dark to see anything, and it was: nothing in the game lit the surface after dark at all. There is a fill now that comes in at dusk and goes out at dawn. If it has gone too far the other way, that is a fail as well and I want to hear it.

Jen, three of yours. The Gem Bench message that says what a missed cut cost was drawing behind the bench window, which is why your dust kept going with nothing to explain it. The bench says whose Gem Dust that number is now, and a cut you cannot afford tells you what you have as well as what it needs. The trophy pedestals hand a trophy back from beside them, not only from on top.

There is a journal. Second icon in the new strip at the top of your screen, next to the backpack. It holds every find you have made with what it was worth and where you first dug one, a page for each species, and the story so far.

Eggs are red, orange, yellow, green and blue by tier now. All the text in the game is one font.

The build number in the bottom corner should say 2394 unless I randomly push something else. Answer what you get to and leave the rest blank. You can always skip anything you can't get to or don't want to do.

Mark every line you tried: ✓ it did what it says, ✗ it did not, n/a you could not test it. Leave it blank if you never got that far — blank is data too, and it is why the list is worth measuring. Click a mark again to clear it. A ✗ opens a note; a note is welcome but never required. Put your name at the bottom and send.

0 answered

1 Six things you found, and I fixed

2 On a phone or tablet

3 This one keeps coming back

4 There is a journal now

5 The top of your screen

6 Windows, and eggs

7 Smaller things I changed

8 Still true from before

✉ Anything else, and send

Including things that are not on this list — the most useful reports usually are.

→ If you want to say more

  1. Quote the code. Every line has one — 2b, 4e, 6c. Leading with it saves everybody a paragraph.
  2. Screenshot it. Especially anything floating, buried, tilted or in the wrong place.
  3. Say roughly when you played, and whether you were alone in the server or with someone.
  4. Say what you expected and what happened. "The cart was sunk into the floor" beats "the cart looks wrong".
  5. Say whether it repeated after a rejoin. A lot of this is rolled fresh per server, so once vs. every time is the most useful thing you can tell us.