[GeoStL] Re: Milestones - How do you do them?

  • From: Tina Boyle <tina_boyle@xxxxxxxxxxxxx>
  • To: "geocaching@xxxxxxxxxxxxx" <geocaching@xxxxxxxxxxxxx>
  • Date: Sat, 16 Mar 2013 15:03:05 -0500

Well mine got out of order because Midwest Geobash was my 3000. But it didn't 
reflect that way. Oh well doesn't really matter to me. I got the souvenir and I 
am happy! 

I do think there is a way to change your numbers as far as milestones. 

Sent from my iPhone

On Mar 16, 2013, at 1:59 PM, Michael Rogers <mrogers07@xxxxxxxxxxxxx> wrote:

> Well, I do have a reason. I am planning for MOGA 2013 to be my #3,000. I have 
> 47 caches to find before logging the event proper for the milestone. The 
> route I have chosen will make it easy to do without gaming the number in any 
> way, but choosing slightly different routes will net me more caches, but 
> would necessitate me logging MOGA when it comes to cache #3,000 before 
> continuing on. I lean to doing what I have done in the past and log them as 
> they truly are, but I was just curious what others do...
> From: Susan Ring <susanmring@xxxxxxx>
> To: geocaching@xxxxxxxxxxxxx 
> Sent: Saturday, March 16, 2013 1:52 PM
> Subject: [GeoStL] Re: Milestones - How do you do them?
> Are you just curious or are you planning something?
> Anyway, I've only had one big milestone at 1000 (although #100 meant a lot to 
> me).  I wanted it to be the Slurpin' Soup event.   I attended the event and 
> found some other caches all on the same day. It wasn't exactly #1000 but when 
> I logged the group of caches for that day I logged them in the order that 
> would make the event 1000.
> At the rate I cache I won't have to worry about another milestone for a LONG 
> time.
> Susan
> On Mar 16, 2013, at 1:30 PM, Michael Rogers wrote:
>> Just a quick, non-angsty question for my fellow SLAGA folks...
>> If you approach a larger milestone (like 1,000, 2,000, etc.) and you have a 
>> specific cache or event planned for it, are you one more likely to: 
>> 1. Be strict in keeping that cache as that number, meaning that you will 
>> stifle some caching, if necessary, to accomplish that goal precisely, or 
>> 2. Still seek to log the cache or event as the milestone, but are willing to 
>> log some caches out of order to do that, just so you can still cache as you 
>> want.

Other related posts: