Fair Play

First and foremost, participants in MiGO contests and promotions need to understand and agree to what MiGO considers to be a "Code of Fair Play", which outlines basic expectations of all who choose to participate in MiGO contests.

General Contest Rules

This section outlines the general rules by which all MiGO geocaching contests hosted on our website or Facebook page will be both designed and executed. These rules do not extend to simple contests that are part of MiGO events.

1. Date and Time:

   All dates and times used in any contest or promotion will be Eastern Standard or Eastern Daylight Time (UTC-5), whatever is in effect.
   

2. Forms:

   Contests may have a common set of forms for entry, playing and completion. Some contests will have a checker hosted on Project-GC.
   
   1. Entry:   If required this will be a form you fill out on the website signaling your intent to play.  
      
   2. Target:   Some contests may also provide players with a target form or list of caches or characteristics for players to find. An example is MiGO BiNGO. 
      
   3. Player:   Some contests may have a form for players to fill out to record their finds or achievements for the contest.
      
   4. Completed:   This will be a form you fill out on the website signaling you have completed the contest.If a target form was provided the completed version will need to be uploaded to this form
   5. Other:  Individual contests may have other files or forms that will be useful to the contest.  They should be listed and described in the same section with the above forms, files and links.

3. Inquiries:

All inquiries to the contest managers must be made using the instructions or links provided on the specific contest page or other designated feedback area accessible to all players.  

4. Eligibility:

   All MiGO contests are open to anyone who wishes to play.     

5. Prizes:

   Prizes for MiGO Contests will be defined for each specific contest. In general, ...
   1. Prizes played for will depend on member level at the time a player's Contest Completed form is turned in.
      
   2. In most, but not all, contests all MiGO members are eligible to win prizes. Exceptions will be documented on specific contest pages. Contest managers will never be eligible for prizes.
      
   3. Lake Superior members will always have an advantage over Lake Huron members. Likewise, Lake Huron members will always have an advantage over St. Clair members, Trial members, Facebook Group members or non-members.
      

6. Finds:

   1. All cache finds must be made on or after the contest start date and before the contest end date and time.
      
   2. All cache finds must be logged on-line with a date as close as practical to the actual find date, prior to submitting the Completed form.
      
   3. All cache types with a GC code are generally eligible to be counted as finds. Exception to this will be identified on the specific contest page.
      
   4. Specific requirements for cache types will be identified on a contest specific basis.
      

7. Adventures:

   1. Adventures Labs are generally not eligible to be counted.
      
   2. Exceptions will be identified on the specific contest page.
      

8. Hides:

   1. To take credit for a hide, a new cache must physically hidden on or after the contest start date and published prior to or on the end date.
      

9. Events:

   1. Events can generally be used for finds (attended) but must be held within the contest period.
      
   2. Events can generally be used for hides but must be held created, published and held within the contest period.
      
   3. Events can not be used for both a find and a hide bye he same player.
      
   4. Any specific requirements for events will be explained on the contest page.
      

References:

When a rule for a specific contest overrides a general contest rule, the general rule that is being overridden should be identified in the contest specific rules. References should be written as ref. GCR# or ref. GCR 2c, for example.

Revision History:

Every revision to this document needs to be documented in the table below!