Jump to content

arisoft

+Premium Members
  • Posts

    2934
  • Joined

  • Last visited

Everything posted by arisoft

  1. It is as ALR as Adventure Lab bonus caches are. I am pleased that this ALR nonsense was not referred in the archive sweep message. Jigidi puzzles are known to register IP-addresses. (Used for banning abusers) Are Jigidi caches the next victim?
  2. Archive 16/02/2024 Mob caches were published as an experiment using specific technology that required players to be in the same place and to enter a code at the same time to learn the final coordinates. This was an exception to the guidelines at the time and is not a publishable concept today. The original site used for this purpose has been removed, and therefore, HQ has decided to archive all active caches originally intended to be solved using this method. Due to privacy laws, we are not seeking an alternative site at this time. We are respectfully requesting that the cache owner please remove the cache container and contents as soon as possible.
  3. I thought that the player must sign the logbook without ALRs? How is this possible?
  4. You could use a notebook. Writing down the code in your water resistant notebook is similar process than signing the logbook. Instead of writing date and your nickname you write date and the token code. You are not supposed to drown the physical logbook either. Token cache works similar way as virtuals or earth caches where you are supposed to take notes and later use this as a proof. It is true that you don't need them but some cache owners may consider them more practical than logbooks and pay for this service.
  5. In the long run I should change my Mobile App from an authorized app to the unauthorized app because it does not make sense that authorized apps do not work properly and the official app is made for entry level users. Currently there are only few anonymous players in the game but with this control the whole idea of authorized developers could be rendered useless.
  6. This is the result, what happens if you have this control, but why you need a such control? There may be a legitimate reason, but it is not disclosed in this thread yet.
  7. The previous thread ends with an important question that I would like an answer to.
  8. No problem, because the code lets you post your log only the date you found the cache, regardless when you finally decide to post it. There is no time-out for the code, because it is always valid only the date you saw it. Let's call this an additional security feature of the token.
  9. It is using an algorithm that can separate valid codes from not valid codes. Every token generates different series of codes that the algorithm can verify. The algorithm can tell when the codeword was displayed on the token.
  10. Yes you do. Instead of posting OAR, your Found it log states "Found it,TftC!". That means that everything is fine and you are happy with the experience. I guess it's not what you thought.
  11. This explains a lot. As a cache owner you are supposed to have decent tools. This is why you can not publish a cache with the Mobile App. Due to limitations of your toolset, you have missed some vital information you need. You logged a Note when trying to Enable your cache after you Disabled it. This is a clear mistake, although I understand how it could happen under the circumstances. Now, after you have told that you should use Enable for enabling the listing, you should understand that you made a mistake here. If you don't understand why this was a mistake, then this may happen again.
  12. I find it hard to believe that you can make such a mistake with seven years of experience. All the time you saw this on the top of your profile page (unless you are using the old one). Just copy the content of the original cache to a new one and publish the cache again as @Tungstène suggested. Problem solved!
  13. It has happened with other physical cache types that FTF finder never logs online. There are some exceptional players who signs the logbook only. In this case the STF finder may only comment about the FTF find they found from the logboook. Challenge checker are not able to tell reliably whether the FTF finder qualifies or not, because the data may not be updated.
  14. It's pure money they got as return by selling these codes or tokens as I suggested. What kind of company choose not to gain revenue?
  15. I know that many players do this. I used the real date when I found the cache until I noticed that it makes me harder situation that others who selected the date arbitrarely depending on they needs. Many challenge checkers do not tell you the date you completed the challenge. Now you may say that "today I found that I have completed the challenge" .
  16. Here in Finland, everybody knows that it is cheating, and almost everyone does it without hesitation. This way to adjust find dates freely is spreading also to other cache types. I am planning to write a note to some traditional cache telling that I may have visited the cache today but I will log it found later when I am sure that I visited the cache. This date adjustusting is just a joke here. This happened after some new challenges that required more cheating than usually. Many years ago Jeremy Irish visited MEGA Finland 2012 and I was there listening when he was on stage. One question the audience asked him was what date a challenge cache should be logged found. Jeremy was surprised by the question and seemed to find the question somewhat strange. In his opinion, it was quite simple. The date when cache has been visited is recorded in the logbook, and it can be logged online when the challenge is fullfilled. He did not bring up the idea that the cache could be logged as found on a day other than the day it was found. The guidelines do not mention dates at all. There is no need to write a date in the logbook when you sign the cache, and there is no date that you should use when logging the find online. Only events are forced to the first date of the event.
  17. We do this kind of cheating a lot in Finland. This kind of cheating is common with virtuals and earth caches too. It lets the finder to use practically any date to log the find. I have sometimes notified in my note to a challenge cache visit that I will check if the challenge is fulfilled later, just to delay the find to adjust it according to my own needs.
  18. I have done this so your statement must be false. A player sent me coordinates where he put my cache due to some reasons at the GZ. I went looking for it and found it. Then I logged "Found", because I legimately found it. This happened a long time ago when it was possible. Afterwards I removed this "Found" to avoid upsetting people with my single "stats abuse".
  19. Here is one local player here who signs some caches and skips some but logs them all on-line. Cache owners are now aware of this habit and delete logs. However, the real effect of being caught is that he is considered a cheater and that stigma cannot be removed.
  20. As referred earlier, some players were used to log "Found" when they found the cache on their cache maintenance tour. I am sure that they comply with this "act of discovery and success" stipulation. Almost every day I am looking for things I have put somewhere and I may find them with act of discovery and success. I am not buying this explanation. I prefer the "stats abuse" explanation. Don't you think that the primary reason to discourage finds to own caches is "stats abuse"? (Regardless of what "stats abuse" means.)
  21. Indeed. In Finland we have a local guideline for them. (Google translation follows)
  22. No, it is not depending at all. The guideline is clear: "You can log caches online as "Found" after you visited the coordinates and signed the logbook." There is nothing about finding at all. It is not obligatory part of the experience by the book. There are some unspoken reasons why "Found" logs are considered disgraceful and prevented to log by the cache owner. I would like to hear these reasons one by one and then figure whether they apply to event caches.
  23. You are absolutely right, but it still happens occasionally by the CO and frequently by other players that are visiting the cache. Experienced players may add extra log sheet to the cache if the logbook is full or damaged to ensure that the visit is recorded correctly, at least temporarily. I have found one cache that works as you suggested. The cache originally had a logbook but the cache was muggled so many times that the CO replaced the cache with a TB. The TB was used as a virtual logbook to sign the logbook before the found was finally logged in the cache page.
  24. I may be twisting words if I say that the host is hosting the event and attendees are attending the event. In most cases, the host is indeed present at the event, actively managing and overseeing the proceedings. They may not be able to fully participate as a guest, as their primary role is to ensure the smooth running of the event and attend to the needs of the guests.
  25. Do you have any reference for this requirement? It is new to me. Many players sign caches they definitely haven't found but they meet the requirements to log a find. In many cases, this happens when a group on geocachers are searching a cache at the same time and only one of them actually finds the cache.
×
×
  • Create New...