I’m not sure how this happened, so I have attached screenshots, but… it appears my first summit of the day was improperly spotted as W4C/EM-051 when it was actually W4C/EM-049 if you chased me before 1400 UTC on 14 Dec 2024.
If anyone can explain how/why the RBN responded this way it would be greatly appreciated.
In the meantime, @SM5LNE , @SP9TKW , @K2JB , @2W0ILQ , and @G3VXJ , you may want to update your chaser logs.
RBNHole is not psychic. You have several spots with overlapping spot windows. By default, the window is S-1 S+3. You have altered the spot window via your comment to S-1 S+2 so between 1300 UTC and 1400 UTC there are two alerts that overlap. RBNHole, not being psychic, will choose the closest alert based on alerted time.
This is all detailed at RBNHole | VK3ARR's SOTA Blog
@VK3ARR I have read the linked post several times, it’s how I learned to spot via RBN in the first place.
It was not evident to me that it would retain the S-1 function if the S+X is altered. I was under the impression that changing the command at all would override the default -1/+3.
Lest I am thought a believer in psychic powers, will S-0 S+3 properly function with the code?
I don’t know whether or not S-0 will work, but I’m not sure that’s what you want anyway. I am often early so I want the default S-1. If you aren’t sure what time you will make it to the summits then use a wildcard alert.
The way to solve this is to use wildcard spots.
s/spots/alerts/
Yes. Alerts not spots 
Often times I will do 13+ miles day hikes that chain multiple summits. I know the order I will arrive at each one, but predicting the exact timeline can be difficult when I have to drive 2.5hr to the trailhead and hike for another 6+ hours. I am more often late than I am early.
I have used this alert strategy many times this year without incident, coincidentally my last hiking trip of 2024 this issue emerged. I suppose another workaround would be to just put 15 min buffers between each alert, so instead of 1200-1400 and 1400-1700, I could have done 1200-1400 and 1415-1700.
Or use wildcard alerts so that you get spotted but not on the wrong summit.
@MM0FMF I understand that, but I’d rather not rely on a kind chaser to spot my summit if I can do it myself with better preparation, or in this case the new information that S-1 is always built into the code regardless of what you input for S+x.
Yes, it should work (modulo I haven’t tried it myself recently). Alternatively, if you don’t want to use wildcards, you could also specify alert time in the middle of the window and use S+/S- appropriately.
The way to look at it is there’s a window, and using the S+/S- stretches a particular side of the window. If you don’t specify an S-, the start side of the window will not be changed. I don’t think it’s intuitive to most users to change a particular default size/start time of the window without notice just because they didn’t specify a parameter. Then people might accuse RBNHole of being psychic 
