/snr seems to behave as the non existent /cnr command. In other words, /snr (Select Nearest Resource) behaves like a cycle.
I have a hotkey of:
1) Text Command: /snr
2) Action Command: Gather
I would expect if i run and stand beside a node, that I should immediately start harvesting the resource I'm standing beside (nearest to), when I click this hotkey. But sometimes I will attempt to harvest a farther away node (and sometimes its too far away to harvest). So this command behaves like a cycle nearest node, not a select nearest node.
But I can keep clicking the hotkey and it starts targeting the nearest resource, then the next farthest away nearest resource, then back and forth (cycling). It cycles the two nearest nodes. I'm not getting the intended behavior like I would expect when using this. Select nearest node should be simply, the nearest node nearest you, no matter how many times you click hotkey or issue /snr
Please make it so /snr only targets the nearest node, no matter what (eliminate how it cycles the two nearest nodes).
While I kind of like the cycling, if you want to do that, then please create a new slash command /cnr (Cycle Nearest Resource).
I actually feel, you should just simply rename /snr and create/overwrite it to a new command of /cnr.
Then fix the current /snr to where it doesn't cycle.