Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

[Chapter 40] Stealth fix for chapter 33 is not mentioned in the course

Open
#232 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
45/100
Issue type
Documentation
Clarity
Mostly clear
Activity status
Stale
Tech stack
rust
Domain
documentation

Research direction

Start with chapter-40-doors/src/map_builders/waveform_collapse/mod.rs at lines 40-41, then compare the WaveformCollapseBuilder introduced in chapter 33 with the chapter and book text. Document the try limit and any related state-clearing changes so readers know about the fix and can reproduce the corrected level-generation behavior.

Written by the indexing model from the issue text.

Description

https://github.com/amethyst/rustrogueliketutorial/blob/33872fe582f226178436847e1f74eafcbf9c0d1a/chapter-40-doors/src/map_builders/waveform_collapse/mod.rs#L40-L41

In chapter 40, there is an update to the code of WaveformCollapseBuilder (introduced in chapter 33).
It adds a try limit to the solver loop to avoid an infinite (or at least a very long) loop.
(Not sure, but I think the additional lines to clear spawn_list, rooms, and corridors after making a copy of the map are also part of the fix).

However, this is not mentioned anywhere in the chapter (or in the book), so people will have to power through the following chapters with a level generation that breaks regularly.

Dominant language
Rust
Stars
967
Forks
166
PR merge metrics
No merged PRs in 30d

Getting set up

This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from amethyst/rustrogueliketutorial

All issues in amethyst/rustrogueliketutorial

Similar issues

More Rust issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.