Powered Rails always show north/south
See original GitHub issueIssue Description: Dynmap flat doesn’t seem to be rendering powered rails in the correct orientation. Normal rails are seemingly fine.
-
Dynmap Version: 3.3-beta-4-forge-1.18
-
Server Version: forge 1.18.1 39.0.19
-
Pastebin of Configuration.txt: https://pastebin.com/gNu4nYMu
-
Server Host (if applicable): Selfhosted
-
Other Relevant Data/Screenshots: Custom
worlds.txt
: https://pastebin.com/Ff82iyCv -
Steps to Replicate: Unsure if this issue is happening on other resolutions/iso since this config is gonna take a while to render :p
[X] I have looked at all other issues and this is not a duplicate
[X] I have been able to replicate this
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top Results From Across the Web
North-South minecart rails : r/redstone - Reddit
In a track in this context means, that the rail has rails to both sides that it is connected to.
Read more >Powered Rail - Minecraft Wiki - Fandom
A minecart that enters a powered rail's space from the side turns east or south (depending on the powered rail's orientation), or in...
Read more >What's the south-east rule in Minecraft? - Arqade
When placing rails, or connecting redstone, connections going South and East will take priority over those going North and West.
Read more >[MC-791] Rails are not placed in the direction the player is ...
The report claims: If you place rails not next to another rail of any type, it always faces north-south instead of the way...
Read more >Powered Rail - Better Than Wolves Wiki
Powered rails do not curve like other rails. Curved power rails only exist in the case where the final direction is towards the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
OK - figured this out (95% sure this is true for you too). If you had the latest, as of a few minutes ago, DynmapBlockScan installed, it had a problem where I left on the ‘vanilla’ block scanning (I use it for testing, but its not suitable for production), and the generated mapping for the vanilla blocks was overriding the better (more accurate) internal ones. Net-net, either remove DynmapBlockScan OR update to the latest build - https://dynmap.us/builds/DynmapBlockScan/DynmapBlockScan-3.2-SNAPSHOT-forge-1.18.1.jar
This fixed the issue, thanks @mikeprimm