In MeshCore One there is a trace bonus feature where you can have it auto-generate the return path. That'd be really nice in RT's trace tool.
It reverses the chain. So if I put in Repeater1, it does nothing. If I put in Repeater1 and Repeater2, it adds Repeater1 on the end (if the option is checked, still free to do adhoc routes). If I do R1, R2, R3, it adds R2, R1 on the end.
Based on discussion in Discord.
In MeshCore One there is a trace bonus feature where you can have it auto-generate the return path. That'd be really nice in RT's trace tool.
It reverses the chain. So if I put in Repeater1, it does nothing. If I put in Repeater1 and Repeater2, it adds Repeater1 on the end (if the option is checked, still free to do adhoc routes). If I do R1, R2, R3, it adds R2, R1 on the end.
<!-- github-sync-id:4641436359 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Based on discussion in Discord.
In MeshCore One there is a trace bonus feature where you can have it auto-generate the return path. That'd be really nice in RT's trace tool.
It reverses the chain. So if I put in Repeater1, it does nothing. If I put in Repeater1 and Repeater2, it adds Repeater1 on the end (if the option is checked, still free to do adhoc routes). If I do R1, R2, R3, it adds R2, R1 on the end.
Added.