Hands-on Rust: Results don't match screen shot for automata map

Title: Hands-On Rust (Chapter 11: Call the Cellular Automata Architect)

when I “run the program now”, I get something like this…

The screenshot in the book looks like it’s probably from your test harness (I haven’t bothered to set it up)

1 Like

Also… pretty sure the instructions neglected to mention to add use automata::CellularAutomataArchitect; to top of file (Maybe it’s getting to the point you shouldn’t have to mention every detail that is that repetitive. I just added it without much thought, and didn’t think about submitting an errata (well, until now)

1 Like

Thanks! I’ll definitely fix the use statement in the next beta. The screenshot is a tough one. You are right - it is from the test harness. I used it because it shows the whole map (and I don’t have enough pages left to include a “view whole map” admin option); when you launch in-game, you see the portion of it around you, and the FoV code limits your visibility.

I think a good compromise will be to go with a split-screen shot. Show the whole map and what it looks like in-game. I’ll try and rustle that up for the next build.

1 Like