03/29/2024 By geoguru1
I didn't have near the adventure as the previous finder. I know the area pretty well and starting at the suggested parking spot made life pretty easy. A short walk led to the container that was pretty easy to find. While the solution to the puzzle was not at the top of my brain I used and available tool to find the answer and voila had the log in hand. SL Give this one a FAV
03/23/2024 By vegantriathlete
{FTF} @ 2102 (Geez, I guess I used all my brain cells to solve the puzzle and then math was too hard for me; I had originally marked the time 1702, which is what you will see on the log. I could also blame hypothermia induced addition deficiency from my adventure!)
I was at the kitchen table getting ready to work on taxes with my wife when a whole bunch of notifications came through about caches that had been published. I started looking through them and saw this one, which is a D/T that I still need for my FTF fizzy. I was glad to see that it was "close enough" to me that I wanted to make a run for it. I also noted that there was a field puzzle involved. Too bad that I didn't take note that the CO provided suggested parking. Instead, I just got in the car and relied on Google Maps. Those directions took me to Princeton street, which seemed reasonable to me given the name of the cache. I got out of the car and immediately thought to myself, "This is not a 1.5T cache!" Then I noticed that I would have to cross a stream. I realized that I was surely approaching from the wrong place. But, I had a pair of "geocaching" shoes in my car. So, rather than drive to another spot, I decided to grab those shoes, roll up my pants, and wade across the chilly water. I quickly found the cache and then sat down to start working on the puzzle. In short time, I decided that I wanted to take everything back to my car to make solving this one a bit more comfortable and easier to manage instead of trying to position my phone flashlight while I worked out the details. Well, my trip back to my car across the stream resulted in an unexpected swim! Fortunately, the cache (and my phone) remained safe. Also, I had some blankets in the car. So, I put one of them in the driver's seat to protect it from my wet, muddy (and cold) backside. Being that I didn't want to have to ford that stream again, I chose to move my car to another spot with good access to the trail. As it turns out the spot I chose was still not the recommended parking. My cell coverage didn't work great at that spot, either, even though I have a full set of bars. I drove my car around until the signal seemed better and things moved faster. I had a notification set on the cache and figured if somebody else headed out at this late hour and discovered that the cache was not in its hiding spot, they would leave a note on the page. Then I could let them know I was in the area.
I love computers and I love math (even though you might not guess that since I managed to calculate the 24 hour time incorrectly). I loved the concept of this puzzle and had it solved in relatively short order given the difficulty (which, as I claimed above used up my brain power to do the 24 hour time calculation). I loved the actual container for this puzzle. If I could give this more than one favorite I would.
The advice I will give to others: Pay attention to the suitable parking options before you leave. Do this one in the daylight hours. Come prepared with your thinking cap. Be ready to have fun!
03/23/2024 By IgnotusPeverell
Published
A Python at Princeton
| Difficulty: 
| Terrain: 
