MNofMind
-
Posts
8 -
Joined
-
Last visited
Posts posted by MNofMind
-
-
46 minutes ago, niraD said:
Coordinates checkers don't make sense for all mystery/puzzle/unknown caches.
Agreed, the challenge caches aren't hiding their final location and wouldn't necessarily need/want it.
-
.png)
2
-
-
48 minutes ago, Viajero Perdido said:
Could it be collapsed by default? Click the little gizmo to expand?
It sure takes a lot of space when I'm not ready to look at it.
I will add this to list of feature requests, thanks for the feedback!
-
4
-
-
9 minutes ago, niraD said:
FWIW, while I'm looking forward to seeing this built-in checker maturing over time, I'm going to stick with my previous plan to add a Certitude checker to my puzzle cache before I replace the container and re-enable it.
I think that is a perfectly acceptable option! This is not meant to replace all the existing checkers that have some great features but to provide an in house one that can help protect against the risk of third party checkers deciding to shut down their servers.
-
18 minutes ago, ChileHead said:
Nice to see this native! I know a lot of people have wanted this for years, and this will solve the problems people have had with copying/pasting HTML, forgetting to update final coords on the puzzle or site or both. This should work great for the bulk of the puzzles where the puzzle solution is coordinates, and there is a single physical stage.
If it's not too early to ask for new features:
- Some mysteries have multiple stages. It would be nice to be able to mark 1 or more hidden stages as needing a coordinate checker, and they would all appear on the cache page. You might in fact have stage 1 have the coord checker, but not the final, if the cache is set up as a multi after the puzzle has been solved.
- Add a new field on hidden waypoints to allow entry of a keyword or phrases that is used in the checker instead of coords, that reveals the coords. These are becoming more popular around my area.
Even without these features (and others!) the coord checker could be used in a large percentage of caches. Nice to have the auto update of corrected coordinates too, that's a nice bonus.
Is the "10 tries in 10 minutes" set up per account or per IP address?
It's never too early to ask, we definitely are aware of features that are desired that this first, basic checker won't solve. The attempts is set up on the account with some other checks to see if it's being abused. IP address may come in to play if it's deemed necessary.
-
21 minutes ago, anpefi said:
IMHO it should be one field just like it is now when you manually correct the coordinates.
19 minutes ago, thebruce0 said:Yes, two things:
1. What A-Team said, being able to copy/paste coordinate solutions into a single box, or type them as desired, would be wonderful. Even geochecker.org (was that the one?) went from separate fields to one field. Script can reduce characters to acceptable NSEW# and then validate the content to parse it. ie, whether I enter "N 20 01.234, W 069 59.999" or "n20 01234 w69 59999", the script could parse "n2001234w6959999" (which can also allow for 2 or 3 digit W degrees). Doing that reduction allows for typos and regional variations, as long as the necessary digits are correct. Having one field also means less tabbing or clicking between fields. You do have at least one or two fields like that on gc.com already, such as when publishing a cache via the wizard, the initial coordinate lookup is a single field.
2. re: "If the finder submits the correct coordinates to the checker, it will automatically update the corrected coordinates on the cache page for that finder." Can this be a sticky option? I actually don't use corrected coordinates, I correct them manually in my mobile app so I can keep track of posted and additional/final waypoints distinctly. Maybe have it on by default, but let us disable the auto-correction of the coordinates?
Thanks for this, it was a nice surprise, and a good example of how suggestions and discussions in the forum are heard even if there's no immediate or direct response to suggestions. If it's good and desireable, GS will consider it; it just takes some time.
Thanks for the feedback!
-
6 minutes ago, The A-Team said:
Some third-party checkers provide a one-field option, so you can work out the puzzle separately and then just copy-and-paste the entire coordinates into one field. Is this something you can look at adding in the future? It can be a pain to copy-and-paste portions of coordinates into the separate fields.
I think we are definitely open to those changes and want to hear what people prefer. The thought was that normally the degrees don't change so we would leave it separate.
-
1
-
-
A very minor nit: while the filter is set to show cache type (display DNF OFF), the information hover box displays the cache name twice. This happens in both Firefox and Chrome on win10.
Also, thanks to all the lackeys for all the monitoring and feedback in forums. The detailed release notes and frequent responses to specific issues is very much appreciated.
This has been fixed, no more double cache name in the tooltip. Thanks for the catch!
.png)
Release Notes (Website: Solution Checker) - October 19, 2017
in Geocaching HQ communications
Posted
Hi all, a lot of great feedback and opinions so far. There was definitely talk of having the optional checker be allowed across other types, such as multis/letterbox hybrids so it helps to hear your thoughts. It sounds like having one field is heavily favored, having the corrected coordinates update being potentially options, plus it sounds pretty consistent of which features from popular checkers are being asked for. We don't have anything planned for the next steps as it is better to decide off of what we hear post release.