> select * from attributes;
+----+----------+---------------------------------+---------------+-------------------+
| id | group_id | attribute_name                  | has_no_option | base_filename     |
+----+----------+---------------------------------+---------------+-------------------+
|  1 |        1 | Dogs                            |             1 | dogs              |
|  2 |        2 | Access/parking fee              |             0 | fee               |
|  3 |        2 | Climbing gear required          |             0 | rappelling        |
|  4 |        2 | Boat required                   |             0 | boat              |
|  5 |        2 | Scuba gear required             |             0 | scuba             |
|  6 |        3 | Recommended for kids            |             1 | kids              |
|  7 |        3 | Takes less than one hour        |             1 | onehour           |
|  8 |        3 | Scenic view                     |             1 | scenic            |
|  9 |        3 | Significant hike                |             1 | hiking            |
| 10 |        3 | Difficult climb                 |             1 | climbing          |
| 11 |        3 | May require wading              |             0 | wading            |
| 12 |        3 | May require swimming            |             0 | swimming          |
| 13 |        3 | Available 24/7                  |             1 | available         |
| 14 |        3 | Recommended at night            |             1 | night             |
| 15 |        3 | Available in winter             |             1 | winter            |
| 17 |        4 | Poisonous plants                |             1 | poisonoak         |
| 18 |        4 | Dangerous animals               |             0 | dangerousanimals  |
| 19 |        4 | Ticks                           |             0 | ticks             |
| 20 |        4 | Abandoned mine                  |             0 | mine              |
| 21 |        4 | Cliff/falling rocks             |             0 | cliff             |
| 22 |        4 | Hunting area                    |             0 | hunting           |
| 23 |        4 | Dangerous area                  |             0 | danger            |
| 24 |        5 | Wheelchair accessible           |             1 | wheelchair        |
| 25 |        5 | Parking nearby                  |             1 | parking           |
| 26 |        5 | Public transportation nearby    |             0 | public            |
| 27 |        5 | Drinking water nearby           |             1 | water             |
| 28 |        5 | Public restrooms nearby         |             1 | restrooms         |
| 29 |        5 | Telephone nearby                |             1 | phone             |
| 30 |        5 | Picnic tables nearby            |             1 | picnic            |
| 31 |        5 | Camping nearby                  |             1 | camping           |
| 32 |        1 | Bicycles                        |             1 | bicycles          |
| 33 |        1 | Motorcycles                     |             1 | motorcycles       |
| 34 |        1 | Quads                           |             1 | quads             |
| 35 |        1 | Off-road vehicles               |             1 | jeeps             |
| 36 |        1 | Snowmobiles                     |             1 | snowmobiles       |
| 37 |        1 | Horses                          |             1 | horses            |
| 38 |        1 | Campfires                       |             1 | campfires         |
| 39 |        4 | Thorns                          |             0 | thorn             |
| 40 |        3 | Stealth required                |             1 | stealth           |
| 41 |        5 | Stroller accessible             |             1 | stroller          |
| 42 |        3 | Needs maintenance               |             0 | firstaid          |
| 43 |        3 | Livestock nearby                |             0 | cow               |
| 44 |        2 | Flashlight required             |             0 | flashlight        |
| 45 |        6 | Lost and Found tour             |             0 | landf             |
| 46 |        1 | Trucks/RVs                      |             1 | rv                |
| 47 |        3 | Field puzzle                    |             1 | field_puzzle      |
| 48 |        2 | UV light required               |             0 | UV                |
| 49 |        2 | May require snowshoes           |             0 | snowshoes         |
| 50 |        2 | May require cross country skis  |             0 | skiis             |
| 51 |        2 | Special tool required           |             0 | s-tool            |
| 52 |        3 | Night cache                     |             1 | nightcache        |
| 53 |        3 | Park and grab                   |             1 | parkngrab         |
| 54 |        3 | Abandoned structure             |             1 | AbandonedBuilding |
| 55 |        3 | Short hike (<1 km)              |             1 | hike_short        |
| 56 |        3 | Medium hike (1 km-10 km)        |             1 | hike_med          |
| 57 |        3 | Long hike (>10 km)              |             1 | hike_long         |
| 58 |        5 | Fuel nearby                     |             1 | fuel              |
| 59 |        5 | Food nearby                     |             1 | food              |
| 60 |        2 | Wireless beacon                 |             0 | wirelessbeacon    |
| 61 |        6 | Partnership cache               |             0 | partnership       |
| 62 |        3 | Seasonal access                 |             1 | seasonal          |
| 63 |        3 | Recommended for tourists        |             1 | touristOK         |
| 64 |        2 | Tree climbing required          |             1 | treeclimbing      |
| 65 |        3 | Yard (private residence)        |             1 | frontyard         |
| 66 |        3 | Teamwork cache                  |             1 | teamwork          |
| 67 |        6 | GeoTour                         |             0 | geotour           |
| 69 |        3 | Bonus cache                     |             0 | bonuscache        |
| 70 |        3 | Power trail                     |             0 | powertrail        |
| 71 |        3 | Challenge cache                 |             0 | challengecache    |
| 72 |        6 | Geocaching.com solution checker |             0 | hqsolutionchecker |
+----+----------+---------------------------------+---------------+-------------------+
70 rows in set (0.001 sec)

• The scripts are limited to the use of about 1024 MB of memory, running on a dedicated server.
• The maximum execution time is 30 seconds. A timeout should now return such error message.

static PGC_LUA_Sandbox::CreateHTMLTable($data)

• You write a checker that checks if User X has Y finds in country Z.
• You then create a tag that refers to the GC-code of a challenge that requires the user to have 1000 finds in Sweden. You then create a config that passes the parameter Y = 1000 and Z = Sweden as well (see below for more information about configs).

{"count":"1000", "country":"Sweden"}

array() {
  profileName => string
  profileId => string
  config => array
  gccode => string
  environmentSettings => array {
    cli => bool
    token => string (32 byte md5)
    maxMemoryUsage => int (bytes)
    maxExecutionTime => int (seconds)
    sandboxVersion => int (currently 2)
  }
}

local args={...}
conf = args[1].config
profileName = args[1]['profileName']
profileId = args[1]['profileId']

• ok can be true or false, depending on if the given profile name fulfills the requirement or not.
• log can be either false, or contain a string with a log example. Normally this is filled in if the given profile name fulfills the requirements, and the required log data is added here. The log will be prefixed with a hard coded string saying something like:
  XXX has used Project-GC to see if he/she qualifies for this challenge and he/she does.
• html can be either false or contain a HTML blob that will be given back to the user. It could be more detailed feedback information for example. This blob will most likely not be useful to post in a log entry. This is an excellent output field to use when the user has not fulfilled the challenge and the script can give some helpful information.

return { ok = ok, log = log, html = false }

• Scripts that uses parameters should document them in the script description. This will make it easier for others to use your script.
• Use keywords to make it easier to find the script. They can be in any language, or in several languages.
• Don't fetch more data than needed when using GetFinds(). There is a filter, which also with the correct usage can be combined with the config-input. Saves you development time, and saves the servers from memory usage.
• If you implement a checker for a challenge that isn't 100% accurate, which may be for technical reasons, make it very clear in the output. Preferably both in the example log and the html output.
• Use the log output variable for example logs, preferably using Markdown. Monospace lists should use the Markdown indentation of four spaces (with a line of four spaces only before the list as well).
• Script outputs should be in English. You can add an additional language as well, but English is required.
• Use the html output variable for more detailed output. You can actually output pure text here as well, but the line-breaks need to be <br>.
• Don't concat strings inside loops. Add them to tables and then join the table instead. This is enormously faster and less memory consuming. This is very important
• After you have created a tag. Use the verify button to run the tag for the last ten who logged the challenge. Normally they should all be OK.
• After you have created a tag, test it on someone with plenty of finds (>10000) and someone with 0 finds.
• Don't create identical tags using the same script. There is a housekeeping job that will automatically remove duplicates, but keep the original. Creating another tag for the same challenge can be ok though. If it is more correct, or uses a script that gives better output.
• In the tag config use int for integers and strings for strings. Ie, { "required": 100 } is more correct than { "required": "100" }.
• Note that neither region or county names always are unique. For example county Waterloo exists in both Canada and Belgium. The region Central exists in four different countries. Make sure you handle this in your scripts and configurations when needed. Using a region/county filter without providing the country will result in errors in the future.