updates to azimuth-tracker
commit4543b362d2134fea2c456162134cc73e963337d6
authorRobert <robert@Roberts-MacBook-Pro.local>
dateThu 17 Oct 2019, 16:36 (7 years ago)
parent4762b92
tutorials/ship-troubleshooting.md−1
@@ -86,7 +86,6 @@ This can happen if they have the wrong keys of yours, or if you have the wrong k
8686in the Dojo, where `~sampel-palnet` is the other ship's name. Then, compare it to the scry information that you saved. If that information matches up, it means that the other ship is the problem. If it **doesn't** match up, your ship has wrong information about the other ship. If you have such wrong information, you can fix this by running:
8787
8888```
89−|start %azimuth-tracker
9089:azimuth-tracker|listen ~ %app %azimuth-tracker
9190```
9291