Edit - Software Engineering Stack Exchange

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

Rev

Sounds like Krustle's algorithm. I have not tried that one, however I have tried three like it. I'm not satisfied by these algorithms because they tend to either have paths with few intersections, to many short dead ends, influences, or tend to be short and straight to the solution. I would like greater control over my maze so that I can fix these problems, and that is why I'm dividing the maze creation into two steps.

user2035846
– user2035846

2014-04-28 04:54:16 +00:00
Commented Apr 28, 2014 at 4:54
You could consider weighting the selection of wall removal based on other heuristics such as number of walls in the room and the size of the two sets to join.

user40980
– user40980

2014-04-28 05:11:23 +00:00
Commented Apr 28, 2014 at 5:11
Ah, good point. I'll look into trying that as well.

user2035846
– user2035846

2014-04-28 05:19:05 +00:00
Commented Apr 28, 2014 at 5:19

Add a comment |

Correct minor typos or mistakes
Clarify meaning without changing it
Add related resources or links
Always respect the author’s intent
Don’t use edits to reply to the author

create code fences with backticks ` or tildes ~
```
like so
```
add language identifier to highlight code
```python
def function(foo):
print(foo)
```
put returns between paragraphs
for linebreak add 2 spaces at end
_italic_ or **bold**
indent code by 4 spaces
backtick escapes `like _so_`
quote by placing > at start of line
to make links (use https whenever possible)

<https://example.com>

[example](https://example.com)

<a href="https://example.com">example</a>

formatting help »
answering help »