Help me think this game through, it might not
work out.
We are thinking of releasing a keep-away bug. It's goal will be to keep out of the hands of a specific user. It must stay in bounds, but keep moving as quickly as possible to avoid being caught! There will be an out-of-bounds rule of course. There must also be a quick-log, (must log) and quick-release rule (12 hours?).
If (when) caught, it should be re-released with a new user specified. This user should also be researched enough to know that the same out-of-bounds is appropriate for them. Also, they should be an active user.
Players will be notified by email of course. Since some teamwork may be involved to help it along, a few emails to some very active cachers to get it started moving along might help.
If the area is too small, it will be too easy. If it's too large, then the potential for frustration by the player looking for it might exists. Imagine travelling 4 hours driving to a site where it was logged only to miss it by minutes. Then again, maybe the game lasts longer because the player waits for it to move closer to them. If it happens to stay in a far place for a few days, the "team" might figure to leave it where it is, but then the long drive becomes more worthwhile...hmmm
Not sure this would work. Worth a try? Maybe it's already been tried (newbie here)?
