Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix generation of adjacent elevated bridges #1650

Merged
merged 3 commits into from
Jul 6, 2022

Conversation

olanti-p
Copy link
Contributor

Summary

SUMMARY: Bugfixes "Fixed generation of adjacent elevated bridges"

Purpose of change

As in the title. If 2 (or more) bridges generated next to each other, the code that elevates them would wrongly detect bridgeheads and make an untraversable mess.

Describe the solution

Refine the check, and also clean oter_id rotation API a bit.

Describe alternatives you've considered

Watching people suffer

Testing

I wasn't lucky enough to get an overmap with 2 adjacent bridges show up, so I had to hardcode them in (not present in PR), and the new elevation code seemed to be discerning them properly. Also teleported to bridgeheads, they also seem fine.

@Coolthulhu Coolthulhu self-assigned this Jun 28, 2022
@Coolthulhu
Copy link
Member

so I had to hardcode them in (not present in PR)

I'll have to trust you here. Might be good if we had some way of forcing certain spawns, like an overmap seed instead of having overmapgen use same rng as everything else.

@olanti-p
Copy link
Contributor Author

olanti-p commented Jul 2, 2022

Found a case "in the wild", the bridges look as they should.
image

@Coolthulhu Coolthulhu merged commit f1e59d3 into cataclysmbnteam:upload Jul 6, 2022
@olanti-p olanti-p deleted the fix-parallel-bridgegen branch July 17, 2022 20:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants