bneiman

This is exactly how I feel about it. You're under no obligation to find each stage of a multicache or Wherigo either, but you don't get to collect a find unless you do. I have no desire to start - or apparently, continue - a religious war, so I'll just accept that this is the Way Things Are. Final notes: I work in software development, and this certainly looks to me like what we refer to as a "feature" (always written with double quotes): An unintended behavior or side effect discovered and exploited by users, which must then be preserved forever, and even justified and documented, because of compatibility concerns. Fortunately, I have only completed three AL caches, each of 5 stages, so I have deleted the extraneous 12 "finds" from my totals and will have to remember to do that going forward for each new AL I pursue. That leaves me several finds short of my milestone, so I'll have to go pick a new target for number 3000. I'll start a new thread, either in this forum or one dedicated to ALs, requesting the introduction of a user-specified switch to specify how a given user wants AL stages to be counted, either 1 stage = 1 find, or 1 AL = 1 find. Or if there already is such a thread, and I can find it, I'll voice my support. Thank you all for your responses.

Well, that certainly violates the Principle of Least Astonishment. I wouldn't expect individual waypoints of a Lab cache to count as finds any more than I'd expect individual stages of a multi-cache to count as finds. Can you or anyone else point me to documentation that states that this is the intended behavior?

Today (4/18/21 EDT) I started out with 2996 finds, intending to locate 4 more and make a specific cache my 3000th find. When I sat down to log finds this evening, I was already at 3001 finds. My statistics / milestone page lists my 3000th find as "Flanders", which is the fourth stage of a five-stage Adventure Lab I did during the day ("Historic Kent", in Kent, Connecticut - do Labs have reference numbers?). Apparently the individual stages have been incorrectly accrued as finds in my statistics. Why did this happen, and how can I get it corrected?

Thank you very much, that was exactly the problem.

I'm trying to submit a set of new cache listings with links pointing to each other and to an external website. I submit the page with links like the following <a href=”http://coord.info/GCxxxxx”>cache name (GCxxxxx)</a> <a href=”http://www.townoflloyd.com/pages/lloydny_webdocs/illinoistrail”>Town of Lloyd website</a> but viewing the page source after submission, the links look like <a>cache name (GCxxxxx)</a> <a>Town of Lloyd website</a> The href attribute completely disappears, and of course the links are broken. What's going on?

Took a TB from a cache today, only to find that there was no TB logged as present in the cache. I'd like to log it and move it along, but I don't know how to identify it. I've got the engraved number from the tag, of course, but I don't have the reference number, and you apparently can't search by the engraved number. The hitchhiker is a small replica of the Eiffel Tower, so I did a keyword search within trackables on geocaching.com, but I couldn't correlate it with any of the 54 items turned up by the search. How do I figure out what bug this is? I'll wait a decent period to see if anyone logs it in to the cache where I found it, but if no one does I won't know whom to nudge or from whom to grab it. Bill