various embodiments of the invention are discussed in detail below . while specific implementations are discussed , it should be understood that this is done for illustration purposes only . a person with ordinary skill in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the invention . the present invention is described herein mainly in terms of an individual accessing the internet , such as via an access mechanism , such as a personal computer ( e . g ., a desktop computer , a laptop computer , a tablet computer , etc . ), a mobile phone , a multipurpose mobile device ( e . g ., a smartphone , an ipod , a personal electronic assistant , etc . ), or a video game system ( e . g ., a nintendo wii , a microsoft xbox360 , a sony playstation 3 , etc .). this is not to be construed as limiting as the present invention may be applicable to any electronic network accessible to a user via a network - appropriate device . for example , the present invention may be applied to broadcast networks ( e . g ., cable , satellite , etc . ), mobile networks , interactive television systems , kiosk systems , and any technologies that enable the electronic rendering of web pages . fig1 depicts a general architecture overview of an exemplary internet scavenger hunt network ( ishn ) 100 including an internet scavenger hunt system ( ishs ) 104 according to an embodiment . the amount of representations of each component depicted is for illustrative purposes only and is not to be construed as limiting , as ishn 100 may include more or less instances of each component as determined by implementation . furthermore , although some components are depicted and described herein as separate , this is not to be construed as limiting , and components may be combined per implementation . the components are herein referenced as “ systems ” and “ mechanisms .” this is not to be construed as limiting and it is to be understood that each component may include the necessary hardware , firmware , and / or software to enable the processing , storing , communicating and / or receiving of data . for example , a component may include one or more computer processors , computer servers , data stores , electronic components , storage mediums , memory , etc . the components of ishn 100 may interact with one another via network 102 . although network 102 is typically described herein to be the internet , this is not to be construed as limiting . network 102 may be any applicable electronic network , such as the internet , a mobile network , an intranet , a broadcast network , a private or proprietary network , etc ., or a combination thereof , and may include local area networks ( lans ), wireless local area networks ( wlans ), wide area networks ( wans ), wireless personal area networks ( wpans ), etc . ishn 100 may include ishs 104 , which may be a system configured to enable the storage of scavenger hunt data , the creation of scavenger hunts , and the distribution of scavenger hunts to access mechanisms 108 . ishs 104 may include data store 106 which may maintain hunt data 130 , hunt creator account data 132 , and user data 134 ( including user account data 136 ). a user identifier may be used to reference the user data 134 of a particular user . for example , a user identifier may be a user &# 39 ; s email address , a username , an identification code , a telephone number , other alphanumeric data , etc . a user identifier may reference a user account . user account data 136 may be user data 134 specific to a user , such as credential information ( e . g ., username and password , social network credentials , etc . ), personal information , contact information ( email address , phone number , etc . ), demographic data ( e . g ., sex , age , etc . ), financial account data ( e . g ., credit card information , checking account information , stored value account information , etc . ), user preferences ( e . g ., hunt preferences , privacy preferences , etc . ), etc . a user may create an ishs user account by accessing an ishs web page , by employing an ishs - specific application ( e . g ., ishs software , a smartphone app , hunt utility mechanism 112 , etc . ), etc . in one embodiment , a user account may be generated , accessed , and / or modified via a third party service , such as social network system 138 . hunt data 130 may include data associated with one or more internet scavenger hunts . hunt data 130 for a particular hunt may be referenced by a hunt identifier and may include urls of web pages , hunt name data , hunt description data , hunt step data , hunt clue data , hunt objective data , reward data , team - play data , etc . a hunt identifier may be a url , an alphanumeric code , or any other data that may be used to reference a hunt . hunt data 130 also may include a hunt creator identifier referencing a hunt creator account . hunt creator account data 132 may include data specific to a hunt creator , such as credential information , contact information , web site information , financial account data , hunt creator preferences , social network data , etc . a hunt creator may create a hunt creator account by accessing an ishs web page , by employing an ishs - specific application , via a social network system , etc . or may contact an ishs service provider to have a hunt creator account established . in one embodiment , ishs 104 may be accessible by a variety of hunt creators and data store 106 may maintain hunt data 130 and / or hunt creator account data 132 for each hunt created by each hunt creator . in another embodiment , ishs 104 may be associated with a limited amount of hunt creators , such as a particular sponsor or a particular group of affiliated sponsors , and data store 106 may only contain hunt data 130 and / or hunt creator account data 132 for the particular creator or group of creators . a hunt creator may be an individual or an organization and may be a commercial or non - commercial entity authorized by an ishn service provider to create one or more internet scavenger hunts . for example , a hunt creator may be an entity such as a retailer , a vendor , a reseller , a manufacturer , and / or an advertising or marketing organization . for example , such an entity may sponsor a hunt in order to advertise a good or service ( herein collectively referred to as a “ product ”) and offer a related reward ( e . g ., a discount coupon , a gift card , etc .). although a hunt creator may be a sponsor ( e . g . a commercial entity ), a sponsor may utilize a separate hunt creator to generate and / or manage an internet scavenger hunt on its behalf . as another example , a hunt creator may be an individual who may create a hunt for recreational purposes . as yet another example , a hunt creator may be an employer or an academic organization and such an entity may create a hunt to be used for training and / or educational purposes . ishs 104 may include hunt creation interface mechanism 114 which may enable a hunt creator to generate a scavenger hunt and may enable a hunt creator to perform any hunt creation - related procedure described herein . ishs 104 may include hunt distribution mechanism 116 which may enable user participation by communicating hunt data 130 to access mechanism 108 and may enable any scavenger hunt distribution procedure described herein . in one embodiment , hunt creation interface mechanism 114 and / or hunt distribution mechanism 116 may work in conjunction with other services , such as social networking system 138 , and internet search systems ( e . g ., google , yahoo , etc . ), etc . for example , an application programming interface ( api ) may facilitate interaction between hunt creation interface mechanism 114 and / or hunt distribution mechanism 116 and social networking system 138 . ishn 100 may include one or more social network systems 138 , such as facebook , twitter , google +, an online forum or message board , etc . ishn 100 components , such as ishs 104 or a web site publisher system , may interact with social network system 138 via an api or other functionality . in one embodiment , a user and / or hunt creator may employ ishs 104 via social network system 138 . a user may interact with one or more components of ishn 100 via access mechanism 108 . access mechanism 108 may include hardware , software , and / or firmware configured to enable the viewing and the inputting of information by the user . for example , a user may interact with components of ishn 100 by loading a web page on a personal computer via a web browser , or through a smartphone via its browsing application or via an another app . additionally , access mechanism 108 may be another properly equipped device , such as a television , kiosk , or other presentation system . furthermore , ishn 100 may be accessible via various embodiments of access mechanism 108 and a user may employ any combination of these . for example , a user may access ishn 100 via his mobile phone at one point and later access it via his television . access mechanism 108 may include browser mechanism 110 which may enable the viewing , receipt , and transmission of data via network 102 . for example , browser mechanism 110 may be a web browser , such as , for example , microsoft internet explorer , mozilla firefox , or google chrome . if access mechanism 108 is a multipurpose mobile device ( e . g ., a smartphone ), browser mechanism 110 may be a browsing application or an app configured to access and / or display web pages and / or participate in internet scavenger hunts . browser mechanism 110 may enable a user to participate in an internet scavenger hunt . in one embodiment , browser mechanism 110 may be enabled with hunt utility mechanism 112 to facilitate hunt participation . an exemplary embodiment of hunt utility mechanism 112 is described in relation to fig4 below . hunt utility mechanism 112 may be a browser extension ( sometimes called an “ add - on ”), a toolbar added to browser mechanism 110 , etc . in one embodiment , hunt utility mechanism 112 may be an application that works independently from or in conjunction with browser mechanism 110 . for example , if the user &# 39 ; s access mechanism 108 is a multipurpose mobile device ( e . g ., a smartphone ), hunt utility mechanism 112 may be an app . once installed , the user may activate hunt utility mechanism 112 whenever he wishes to play . for example , hunt utility mechanism 112 may be a browser extension the user clicks on or an app he selects from his smartphone menu . the user may obtain hunt utility mechanism 112 from a hunt service provider web page associated with ishs 104 or a web page associated with a particular hunt creator or sponsor . the web page &# 39 ; s may offer hunt utility mechanism 112 in order to enable the user to participate in hunts from various hunt creators . alternatively , the web page may be specific to one hunt creator or sponsor and hunt utility mechanism 112 may only provide access to that creator &# 39 ; s or sponsor &# 39 ; s hunts . in the latter case , the hunts offered may be related to a particular sponsor &# 39 ; s products . the scavenger hunt web page may also serve to explain the scavenger hunt process to those interested , to provide prizes to participants , to enable hunt creation , to display available hunts , to enable a user to create or join a teams , etc . hunt data 130 , such as clues , objectives , urls , etc ., may be communicated to hunt utility mechanism 112 , which may instruct browser mechanism 110 and / or access mechanism 108 appropriately . for example , browser mechanism 110 may access an appropriate web page , such as web page 118 , web page 120 , or web page 122 , maintained by web site publisher system 124 , web site publisher system 126 , or web site publisher system 128 ( respectively ). a web site publisher system may be any system that enables the distribution of electronic content via a web page . for example , a web site publisher system may include a web server and may enable a user to view a web page via access mechanism 108 . three web pages and three web site publisher systems are depicted in fig1 for illustration purposes only and this is not to be construed to as limiting . ishn 100 may include any number of web pages and / or web site publisher systems . a hunt creator may access ishs 104 via a browser mechanism 110 . for example , a hunt creator may log into a web page associated with ishs 104 . alternatively , a hunt creator may access ishs 104 via a specialized application . a hunt may be designed to advertise an entity &# 39 ; s products by requiring the participants visit web pages pertaining to the entity &# 39 ; s products ( e . g ., product pages , reviews , etc .). additionally , or alternatively , a user may be required to supply one or more objective answers pertaining to the entity &# 39 ; s products ( e . g . “ toyota has the best cars .”). a hunt may be designed to include multiple sponsors , with each sponsor having one or more of its web pages included in the hunt . a scavenger hunt may be based upon any topic , may be as complicated or as simple as the hunt creator desires , and may be targeted toward a variety of audiences . for example , scavenger hunts may be designed to test participants &# 39 ; knowledge ; may be aimed at women , teenagers , gardening enthusiasts , etc . ; and / or may deal with beers of the world , supermodels , fashion , food , or anything else the hunt creator wishes . once a hunt creator has accessed ishs 104 , he may create an internet scavenger hunt . fig2 depicts a flowchart of an exemplary process for creating an internet scavenger hunt via ishs 104 according to an embodiment . the hunt creation process described herein is related in a particular sequence for explanation purposes only and it is not to be construed as limiting . other sequences producing the same result may also be employed . from the hunt creator via access mechanism 108 , ishs 104 may receive a hunt name ( step 202 ) and a hunt description ( step 204 ). for example , the creator may name a sports - related hunt “ sports seek ” and may enter a description detailing the hunt ( e . g ., “ search the web for major league sports teams !”). the description explain the particulars of the hunt , the particulars of the reward to be provided , the hunt requirements , etc . if the hunt creator wishes to enable team play , ishs 104 may receive team play data in order to establish the maximum and / or minimum number of teams allowed to participate ( step 206 ) and the maximum and / or minimum number of players allowed on each team ( step 208 ). alternatively , if the hunt is only for individual players , ishs 104 need not receive team play data and these steps may be omitted or skipped . ishs 104 may receive instruction from the hunt creator to add a hunt step ( step 210 ). ishs 104 may enable a hunt creator to indicate the sequential position of the added hunt step or , alternatively , hunt steps may be ordered in the sequence they are added . ishs 104 may enable the creator to revise a hunt &# 39 ; s step order during or after the hunt creation process . ishs 104 may receive the objective for the added hunt step ( step 212 ). for example , for a hunt step for an american football - related hunt , the objective may be “ green bay packers .” ishs 104 may receive one or more clues to be provided for the objective for the added hunt step ( step 214 ). for example , a clue for the “ green bay packers ” objective may be “ their fans are rather cheesy .” the hunt creator may enter multiple clues if he wishes to offer users additional help . ishs 104 may receive the url associated with the added hunt step ( step 216 ). for example , the url may be “ http :// www . nfl . com .” once the hunt step has been added , ishs 104 may determine whether the added hunt step is the final step of the hunt ( step 218 ). if not , he may continue to add steps until he reaches the final step ( i . e ., repeat steps 210 - 216 ). for example , the hunt creator may indicate if the added step is the final step or ishs 104 may determine whether the creator has reached a hunt step limit . once all the steps have been completed , the user may be allowed to revise the order and make any of adjustments in the hunt steps as needed . in an alternative embodiment , the hunt steps may be randomized or a participant may be allowed to complete the steps non - consecutively . for example , the hunt creator may designate that a participant may skip steps and return to them later . ishs 104 may receive or more rules from the creator and establish these for the hunt ( step 220 ), such as how quickly the hunt must be completed , how many clues are allowed per objective , reward parameters ( e . g ., how the value of the reward may fluctuate based how fast the hunt was completed , the number of clues used , etc . ), etc . when the hunt creator has entered all the necessary information and is satisfied with the hunt , he may indicate this and ishs 104 may enable the hunt for user participation ( step 222 ). the hunt may be assigned a hunt identifier . a hunt creator need not complete hunt creation in one session . he may be enabled to may save his progress and provided hunt data in order to resume hunt creation at a later time . a hunt creator may also access ishs 104 to modify , activate , deactivate , or delete an existing hunt . fig3 a and fig3 b depict a flowchart of an exemplary process for participating in an internet scavenger hunt according to an embodiment . the scavenger hunt described herein describes the ishs 104 as enabling the scavenger hunt via hunt utility mechanism 112 . this is not to be construed as limiting and it is to be understood that other embodiments are possible . in one embodiment , browser mechanism 110 may interact with ishs 104 directly without the use of hunt utility mechanism 112 . additionally , the description herein explain one or more procedures as being handled by ishs 104 and / or hunt utility mechanism 112 . this is not to be construed as limiting as the necessary data processing , management , and storage may be accomplished via ishs 104 , hunt utility mechanism 112 , browser mechanism 110 , and / or access mechanism 108 , as would be appropriate per implementation . when a user wishes to initiate a scavenger hunt , ishs 104 may receive a request to access a user account from the user via access mechanism 108 ( step 302 ). a user may access his user account via hunt utility mechanism 112 , by accessing an ishs web page , via social network system 138 , etc . ishs 104 may determine whether the user has a user account ( step 304 ). for example , the user may be prompted to provide login credentials , ishs 104 may receive credential data maintained by browser mechanism 110 or hunt utility mechanism 112 ( e . g ., tracking cookie information ), etc . and ishs 104 may determine whether there is a corresponding user account . if ishs 104 does not have a corresponding user account , the user may be prompted to create one and , after ishs 104 has received sufficient user data , ishs 104 may create a user account for the user ( step 306 ). once a user account has been created , the user may opt to have hunt utility mechanism 112 store his credential information so that hunt utility mechanism 112 may log him in automatically upon subsequent accesses . in one scenario , hunt utility mechanism 112 may interface with one or more social networking systems 138 , and the user may access his user account via his credentials for such a system . if the user logs in and / or creates a user account via a social networking system 138 , he may not need to provide registration information as ishs 104 may access such data from social networking system 138 . once ishs 104 has accessed the user &# 39 ; s user account ( step 308 ), it may receive from the user one or more account option selections ( step 310 ). for example , the user may choose whether to share reports of his scavenger hunt process via social network system 138 , such as by having his progress automatically reported as updates to his twitter , facebook , and / or google + accounts . a user may indicate the types of scavenger hunts in which he wishes to participate . for example , his account option selections may indicate whether he wishes to participate in sponsored hunts , group hunts , hunts with or without rewards , the maximum or minimum steps involved , etc . the user may only need to establish these options upon his initial use of ishs 104 , although he may adjust an option at a later time , and this step may be omitted once account options have been established ishs 104 may communicate available hunt data to hunt utility mechanism 112 ( step 310 ) and may receive the user &# 39 ; s scavenger hunt selection ( step 312 ). hunt utility mechanism 112 may present a listing of scavenger hunts available to the user and enable access to descriptions , details , instructions , requirements , rewards , etc . for each of the available hunts . the user may select a hunt he has previously started or select a new one . for a hunt the user has already started , hunt utility mechanism 112 may indicate the user &# 39 ; s progress in the hunt ( e . g ., 55 % complete ). in one scenario , a user may select more than one hunt and may participate in multiple hunts in succession or concurrently . a user may choose one hunt for one session and choose a different hunt at the next session , etc . hunt utility mechanism 112 may track and store his progress ( either locally or at ishs 104 ), allowing the user to resume where he left off when he next accesses his user account . in one scenario , a user may be enticed to complete a hunt sooner rather than later by the promise of a greater reward for a more timely completion . before choosing the hunt , the user may review the particulars and requirements and , if he has previously started the hunt , review his progress . after the user has selected a particular hunt and ishs 104 receives the selection ( step 314 ), ishs 104 may activate the hunt for the user ( step 316 ) and the user may participate via hunt utility mechanism 112 . as detailed below , in one embodiment , ishs 104 may not activate the selected hunt if it is a team hunt and insufficient users have selected it . when displaying available hunts , hunt utility mechanism 112 may indicate the number of players needed and number of players that have selected a particular hunt . once the selected hunt has been activated , ishs 104 may communicate the initial web page data , including a url , for the selected scavenger hunt to hunt utility mechanism 112 ( step 318 ) and hunt utility mechanism 112 may instruct browser mechanism 110 to access the associated web page . if the user has chosen to resume a hunt he had previously begun , the initial web page data communicated to hunt utility mechanism 112 may be associated with the last web page he accessed for the hunt . ishs 104 may communicate a clue about the initial objective for the hunt to the user via hunt utility mechanism 112 ( step 320 ). a user may request a clue via hunt utility mechanism 112 or it may be presented automatically . the current web page may be associated with the clue in some fashion and the clue may be presented in a display included in hunt utility mechanism 112 , as a pop - up message , etc . for example , the first clue may be “ the big o ,” the answer may be “ oprah ,” and the current web page may include an article about oprah , a link to a book from oprah &# 39 ; s book club , etc . via hunt utility mechanism 112 , ishs 104 may receive the user &# 39 ; s objective answer once he has entered it via an objective input interface included with hunt utility mechanism 112 ( step 322 ) and ishs 104 or hunt utility mechanism 112 may determine if it is the correct answer ( step 324 ). for example , hunt utility mechanism 112 may access hunt data 130 to determine if the received objective answer is correct or hunt utility mechanism 112 may communicate the objective answer to ishs 104 so that it may analyze the received objective answer . the current hunt &# 39 ; s hunt data 130 may be referenced by the current web page &# 39 ; s url or another hunt identifier . if the user has entered a wrong objective answer , hunt utility mechanism 112 ( or ishs 104 via hunt utility mechanism 112 ) may communicate an alert message ( e . g ., “ try again ”) ( step 326 ) and , in one embodiment , may communicate an additional clue for the current objective ( step 328 ). in another embodiment , the user may not be able to receive an additional clue or may only receive an additional clue after repeated failures . if the user has entered the correct objective , hunt utility mechanism 112 or ishs 104 may determine if the current web page was the final page in the scavenger hunt ( step 330 ). if not , web page data , including a url , for the next web page in the hunt and next objective clue may be communicated to hunt utility mechanism 112 ( steps 332 and 334 ), which may instruct browser mechanism 110 to access the corresponding page and may provide the next objective clue . as aforementioned , hunt steps may be presented in a randomized sequence . additionally , a participant may be allowed to complete the steps non - consecutively , such as by skipping a step and returning to it later . in an alternate embodiment , rather than hunt utility mechanism 112 accessing the next web page in the hunt for the user , the user may be required to determine which url is next by himself . part of the challenge of the scavenger hunt may be locating the one or more of the particular urls that the hunt creator has included as hunt steps , rather than the user being automatically led to each one . for example , the user may use browser mechanism 110 to navigate from one web page to the next and hunt utility mechanism 112 may indicate when he has reached an appropriate url . the user may then analyze the web page for the objective . alternatively , finding the appropriate web page may be the objective in itself and the user may not need to enter a particular objective answer . clues provided to the user may pertain to a particular web page in addition to , or rather than , a particular objective answer . the user may continue with the hunt until he provides the final objective for the final page . in one embodiment , if the user stops the hunt before reaching the final objective , ishs 104 may store his progress and enable the user to resume the hunt at his subsequent access . when it has been determined that the user has completed the final objective , ishs 104 and / or hunt utility mechanism 112 may communicate a message indicating that the hunt has been completed ( step 336 ) and may determine if the user is eligible for a reward per the hunt &# 39 ; s reward parameters ( step 338 ). the reward may be based upon a score reflective of the user &# 39 ; s effectiveness . the score may be based upon the number of objectives found , the length of time needed to complete the hunt , the number of clues needed , etc . if the hunt was a team hunt , as detailed below , ishs 104 may determine if the team &# 39 ; s performance makes them eligible for a reward . in one scenario , a user may be eligible for a reward simply by completing the selected hunt . if the user is eligible for a reward , a reward message may be communicated ( step 340 ). in one scenario , the reward message may simply be a congratulatory message . in another scenario , the reward message may enable the user to receive a monetary reward , such as credit to registered financial account , a credit to a stored value account associated with ishs 104 or a hunt sponsor , a gift certificate ( delivered electronically or via traditional means ), etc . if permitted per the user &# 39 ; s established account options , a congratulatory message may be presented via social network system 138 ( e . g ., a wall post on facebook or a twitter tweet ). if the user is not eligible for a reward , ishs 104 , via hunt utility mechanism 112 , may communicate a failure message ( step 342 ). as mentioned , in addition to allowing for a solitary user to participate in a hunt , a hunt may be designed as a group hunt to allow , and possibly require , multiple users to participate . for example , a group hunt may require that a particular number of users participate . this group may be considered a team . in one scenario , a team may include a leadership hierarchy , with one or more members having authority over other team members . a leader member may be allowed to remove other team members ( e . g ., because a member has ceased to participate , is ineffective , is voted out by other team members , etc .). in one scenario , a team may need to maintain a minimum or maximum number of members in order to be eligible for the hunt and / or the associated reward . a hunt may be designed to mandate a particular number of teams in order for the hunt to be active . in order for the hunt to be considered a success and , therefore , for the reward to be provided , a certain quota of objectives may be required to be met . for example , the team may need to complete all of the steps or , for example , 75 % of them . as another example , every member of the team may be required to complete a hunt before it is considered finished . this scenario may provide team members with an incentive to ensure each team member participates . if multiple teams are involved in the same hunt , the first team to finish may be the only one to be rewarded or rewards may be provided to various teams in the relation to how successful each team was ( e . g ., first prize , second prize , etc .). an internet scavenger hunts may be held as competition and the competition may include multiple hunts . an individual or team may not be allowed to proceed to the next hunt until the current hunt has been finished . alternatively , a hunt may be skipped , with the player possibly given the option to return to the hunt later . an internet scavenger hunt may be implemented for various reason . for example , an internet scavenger hunt may be implemented as a team - building exercise ( e . g ., for co - workers ), a knowledge test ( e . g ., an accreditation process , a quiz , etc . ), a competition , a social network game , a knowledge building exercise ( e . g ., sale team training , school work , learning a language , etc . ), a way to meet people ( e . g ., a singles party hunt , etc .) etc . furthermore , a team scavenger hunt may interact with a group - based service , such a groupon . a scavenger hunt may be scheduled to start at a particular date and / or time . this may be used as a way to market the hunt ( e . g ., “ the horror hunt starts on october 31st at midnight !”). these examples are for illustrative purposes only and it is to be understood that the present invention may be applied to other scenarios as well . fig4 depicts an overview of an exemplary of hunt utility mechanism 112 according to an embodiment . hunt utility mechanism 112 may provide the user with a convenient interface to select and participate in hunts , communicate with other hunt participants , view hunt statistics , etc . the hunt utility mechanism 112 depicted in fig4 is an example of a hunt utility configuration and is not to be construed as limiting . it is to be understood that other configurations may be possible with more , less , or the same elements as those depicted and those described herein . furthermore , although hunt utility mechanism 112 is depicted as a web browser extension , this is not to be construed as limiting , and hunt utility mechanism 112 may be alternatively implemented as an independent application . hunt utility mechanism 112 may include hunt selection interface 402 that may enable a user to select a particular hunt to in which to participate . for example , the hunt selection interface 402 may provide a list of available scavenger hunts via a drop - down menu . if the user is part of a team , he may use hunt selection interface 402 to toggle between all available hunts or only hunts in which his team is participating . hunt selection interface 402 may indicate in which scavenger hunts his team is active , such as via an icon . if a particular scavenger hunt allows for either solo or team play , a user may be required to participate in the hunt in only one fashion ( i . e ., solo or on a team ) to prevent him from receiving double points for the same hunt . hunt information display 432 may provide the user with information regarding his current hunt , such as the name of the hunt , the total number of steps in the hunt , which step he is currently on , the number of steps his team has completed , etc . hunt status interface 404 may enable a user to toggle between participating in the hunt and ceasing or pausing his participation . hunt utility mechanism 112 may only be active when a user is explicitly participating in a scavenger hunt . when a user is participating in a scavenger hunt , hunt utility mechanism 112 may track the urls visited and may alert the user when he has found a hunt web page ( even if accidentally ). if the user is not participating in a hunt , hunt utility mechanism 112 may still function , such as by providing data regarding his team &# 39 ; s progress , enabling the user to interact with team members , etc ., but , per a user &# 39 ; s preferences , it may not be able to track or monitor the user &# 39 ; s web browsing behavior . a user may use team creation interface 406 to create a team . the user may stipulate who may join the team ( e . g ., public , invitation - only , per team leader approval , etc . ), may invite participants ( e . g ., by providing their email addresses , phone numbers , etc . ), set a hunt ranking requirement , etc . the user may be prompted to provide an avatar image , such as a photograph of himself , to represent himself to other team members or other hunt participants in general . the avatar image may be stored in association with his hunt account . in one embodiment , a user may allow his avatar image and / or that of the entire team to be provided to a third party service , such as abillionfaces . com . team joining interface 408 may enable a user to find and join an existing team . for example , team joining interface 408 may provide a list of available teams via , for example , a drop - down menu , or the user may enter the name of a known team or team member . once the user has selected a team , he may readily join if membership is open to all or he may request to join if access is restricted . team members may communicate with one another via messaging interface 418 . messaging interface 418 may enable communication via typed messages , audio communication , video communication , or a combination thereof . location display 420 may indicate the location of other team members . in one embodiment , location display 420 may be a map - like display that allows a user to zoom in on particular locations . in order to preserve player privacy , location display 420 may only display a general location , such as a participant &# 39 ; s city . a participant may also stipulate in his user account the level of location information he wants available and to whom he wants it available . hunt voting interface 422 may enable team members to vote on the hunt in which to participate . for example , hunt voting interface 422 may display five available scavenger hunts and allow each member to cast a vote for his desired hunt . the displayed hunts may be the next ones available , randomly selected , or may include the hunt each team member selected via hunt selection interface 402 . once the majority of the team has selected a particular scavenger hunt , it may begin or each team member may be prompted to start . in one embodiment , in addition to , or instead of , hunt creators providing ishs 104 with clues , users may provide ishs 104 with the clues . a user may use clue providing interface 410 to leave one or more clues regarding a hunt objective . the user may be restricted to leaving a clue only for the web page he is currently viewing or may be enabled to specify the appropriate web page for the clue . a user may use clue providing interface 410 during solo play and leave public clues for other participants and / or may use it during a team hunt to leave clues for other team members . hunt utility mechanism 112 and / or ishs 104 may scan a clue before publishing it in order to prevent a user from explicitly providing the hunt objective answer via the interface . alternatively , a human operator may monitor user - provided clues in order to prevent this . a user may also request a clue for the current web page by selecting clue request interface 412 . once selected , clue request interface 412 may display one or more clues provided by other users or by the hunt creator . a user may provide feedback regarding a received clue via clue feedback interface 414 . for example , if the user feels a clue is particularly useful , he may select “ good clue !” while he may select “ bad clue !” for a clue that was not helpful . as with user - provided clues , hunt utility mechanism 112 and / or a human operator may monitor user feedback to determine whether a user is abusing the system . for example , hunt utility mechanism 112 , ishs 104 , or a human operator may determine if an individual is purposefully providing inaccurate clue feedback or whether a particular user - provided clue is being repeatedly marked as bad ( thereby indicating abuse by the participant that provided the clue ). a user that abuses clue providing interface 410 or clue feedback interface 414 may lose points , be blocked from participating in the hunt ( and possible future hunts ), etc . information entered into messaging interface 418 may be similarly monitored . a user may enter what he believes is the correct objective answer into objective input interface 430 . hunt utility mechanism 112 may then interact with ishs 104 to determine whether it is correct . a participant may receive a score for completing hunt objectives . the score may be represented in various fashions , such as a grade , a percentage , a point total , etc . a user may view his current hunt score via score display 416 . the amount of a score may be based upon how long it took the user to find objectives , how many clues he needed , a minimum and / or maximum point reward , etc . a user &# 39 ; s score may also be increased for providing good clues and / or for providing accurate clue feedback , and , as mentioned , may be penalized for providing bad clues and / or inaccurate user feedback . current page information display 424 may provide the user with various data , such as how many players have been on the current web page before the user , the number and names of team members that have been to the web page , the number and names of team members currently there , etc . timer display 426 may display the time elapsed since the user started the scavenger hunt , the time left remaining before the hunt ends , etc . ad display 428 may display electronic advertisements , such as those provided by a hunt sponsor . these and other aspects of the present invention will become apparent to those skilled in the art by a review of the preceding detailed description . although a number of salient features of the present invention have been described above , the invention is capable of other embodiments and of being practiced and carried out in various ways that would be apparent to one of ordinary skill in the art after reading the disclosed invention . therefore , the description should not be considered to be exclusive of these other embodiments . also , it is to be understood that the phraseology and terminology employed herein are for the purposes of description and should not be regarded as limiting .
a system , method , and computer readable medium for playing a scavenger hunt game via an electronic network , such as the internet . players are enabled to search and find clues distributed amongst multiple electronic locations , such as web pages , in order to reach a final objective . clues lead each player from a starting uniform resource locator to a final url .