IDEAS UNDER CONSIDERATION
-------------------------
- after 3 wrong code entries (ie entering invalid codes) do something terrible
    - could not allow more codes to be entered for some period of time
    - could make nasty noises
    - could shock user with a taser (ok, probably not)
REJECTED
- encode location and puzzle in arrival code so that the gadget can adjust to
    changes in clue/location sequence (ie for skips or additional puzzles)
YES
- provide a means for teams to change batteries
    - ideally we would like to guarantee that batteries will not need to be
        changed
    - for that reason we may dispense with the backlight entirely
    - monitor current usage and deny use of backlight if it is
        possible that the gadget could run out of juice by end of game
    - monitor current usage even without backlight and deny commonly used but
        nonessential functions if it looks like we may run out of juice
        (eg no more video game if they play it nonstop and run down the
        battery)
    - if necessary we can look into providing a way for teams to change the
        batteries
    - it would be nice if teams could change the batteries after the game is
        over.
        - lower priority
        - could use an external battery pack
REJECTED - necesity TBD
- provide a mechanism for downloading scores, clue timing, and other info
    from each team's gadget into a computer at the end of the game
    - possibly show side by side comparison of different teams as they come in
        and download their gadget
IN THE WORKS


OPEN ISSUES
-----------
- number of characters in codes
    - suggestion was:
        - arrival code: 4 characters
        - solution code: 6 characters
    - 4 characters may not provide enough security
ARRIVAL: 6 chars
SOLUTION: approx 6 chars (but any number is ok)
- what is the algorithm for computing a score
TBD
- count down timer? count up timer? Do we tell them what it is counting down to?