Road connections for specials always start on land #70682
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Can be removed quickly using a regex replace of
,\s+\{.*"point":\s+\[\s+-?[0-9]+,\s+-?[0-9]+,\s-?[0-9]+\s+\],\s+"locations":\s+\[\s+"land",\s+"road"\s+\]\s+\}
github-actions
bot
added
<Bugfix>
Procyonae
force-pushed
the
RoadConnectionsStartOnLand
branch
from
60d6550 to
1bca8cc
Compare
github-actions
bot
added
the
BasicBuildPassed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Bugfixes "Road connections for specials always start on land"
Purpose of change
Workaround for #22133, a neater solution would still be nice
Describe the solution
Describe alternatives you've considered
Testing
Teled along a winding river from my starting OM to (87, 1978, 0) without finding a single borked bridge before getting bored
Additional context
While this appears to add quite a mess to specials.json for a workaround the whole lot can be removed with a single regex replace of
,\s+{.*"point":\s+[\s+-?[0-9]+,\s+-?[0-9]+,\s-?[0-9]+\s+],\s+"locations":\s+[\s+"land",\s+"road"\s+]\s+}
with notepad++ for example