This disclosure relates generally to interface-based game-space contest generation.
Traditionally, configuration of a contest is performed by engineers to manually code changes to the backend to execute the contest. Typically, at the end of a contest, administrators manually judge the performance of participating users of the contest, for instance, by evaluating contest activities performed by those users, by comparing scores computed for those users, etc. In addition, the administrators often manually distribute the contest awards based on their judging. Among other issues, these conventional techniques may be associated with human-related errors (e.g., judging errors, awarding errors, etc.) along with delays in award distribution, resulting in user dissatisfaction with the contest experience, higher volume of support calls, and/or other drawbacks.
One aspect of the disclosure relates to a system configured to facilitate interface-based game-space contest generation, in accordance with one or more implementations. In exemplary implementations, one or more performance criteria to be associated with a contest to be provided in a game space, one or more awards to be distributed in association with the contest, one or more qualifications to participate in the contest, and/or other contest-related user inputs may be received via a user interface. Based on these user inputs, a notification that relates to the contest may be provided in the game space. Contest-related activities that are performed in the game space by the users participating in the contest may be monitored. Performance scores of the participating users may be determined based on the performance criteria and the performed activities. The awards may be automatically distributed to individual ones of the participating users in accordance with the performance scores of the individual participating users. In this way, interface-based game-space contest generation may decrease human-related errors (e.g., by providing more accurate performance scoring of performed contest-related activities, awarding the right participating users, etc.), reduce award distribution delays (e.g., by determining the award winners more quickly, distributing the awards upon such determination, etc.), improve user experience relating to such contests, lower the number of support calls, and/or provide other benefits.
In some implementations, the system may include one or more servers. The server(s) may be configured to communicate with one or more client computing platforms according to a client/server architecture. The users may access the system via the client computing platforms, for instance, to interact with one or more services.
The server(s) may be configured to execute one or more computer program modules to facilitate interface-based game-space contest generation. The computer program modules may include one or more of a template interface module, a contest implementation module, a performance determination module, an award distribution module, and/or other modules. In some implementations, the client computing platforms may be configured to execute one or more computer program modules that are the same as or similar to the computer program modules of the server(s) to facilitate interface-based game-space contest generation.
The template interface module may be configured to provide a user interface configured to receive user inputs that include one or more performance criteria to be associated with a contest to be provided in a game space, one or more awards to be distributed in association with the contest, one or more qualifications to participate in the contest, and/or other user inputs. The template interface module may be configured to provide the user interface to an administrator to receive the user inputs from the administrator via the user interface. The game space may be configured to facilitate interaction of users with the game space and/or each other by performing operations in the game space in response to commands received from the users.
In certain implementations, the performance criteria may relate to success with respect to the contest to be provided in the game space. The success-related performance criteria may relate to one or more of resource collection, building possession, combat, rescues, or level progress.
In some implementations, the qualifications to participate in the contest may include merit-based qualifications associated with the game space. The merit-based qualifications may relate to one or more of possessed structures, collected resources, combat history, rescue history, or user level.
The contest implementation module may be configured to provide, based on the user inputs, a notification in the game space that relates to the contest. For example, the notification may be provided based on the performance criteria to be associated with the contest, the awards to be distributed in association with the content, and/or the qualifications to participate in the contest that are received as one or more of the user inputs. In various implementations, for instance, the notification may indicate one or more of the users that are qualified to enter the contest based on the qualifications to participate in the contest. In some implementations, the notification may indicate the performance criteria, the awards, and/or the qualifications.
In certain implementations, the contest implementation module may execute the contest in the game space based on the user inputs. The performance determination module may be configured to determine, based on the performance criteria and activities that are performed in the game space by the users that participated in the contest, performance scores of the participating users. The award distribution module may be configured to facilitate automated distribution of the awards to individual ones of the participating users in accordance with the performance scores of the individual participating users.
In various implementations, the award distribution module may be configured such that at least one of the awards is distributed to at least one of the participating users in response to the performance scores of the at least one participating user satisfying one or more performance thresholds.
In certain implementations, the award distribution module may be configured such that the awards are distributed based on one or more predetermined intervals of the contest. In some implementations, the award distribution module may be configured such that a first award of the awards is distributed during a first predetermined interval of the predetermined intervals to a first participating user of the participating users in response to the performance scores of the first participating user satisfying a first performance threshold during the first predetermined interval, and such that a second award of the awards is distributed during a second predetermined interval of the predetermined intervals to the first participating user in response to the performance scores of the first participating user satisfying a second performance threshold during the second predetermined interval.
In certain implementations, the template interface module may be configured to store a template that indicates the user inputs. As such, in some implementations, the contest may be executed in the game space based on the stored template. The contest may, for instance, be executed based on a predetermined schedule, a periodic basis, a manual user activation, and/or other trigger using the user inputs indicated in the stored template.
These and other features, and characteristics of the present invention, as well as the methods of operation and functions of the related elements of structure and the combination of parts and economies of manufacture, will become more apparent upon consideration of the following description and the appended claims with reference to the accompanying drawings, all of which form a part of this specification, wherein like reference numerals designate corresponding parts in the various figures. It is to be expressly understood, however, that the drawings are for the purpose of illustration and description only and are not intended as a definition of the limits of the invention. As used in the specification and in the claims, the singular form of “a”, “an”, and “the” include plural referents unless the context clearly dictates otherwise.
In some implementations, system 100 may include one or more servers 102. Server(s) 102 may be configured to communicate with one or more client computing platforms 104 according to a client/server architecture. The users may access system 100 via client computing platforms 104, for instance, to interact with one or more services.
Server(s) 102 may be configured to execute one or more computer program modules to facilitate interface-based game-space contest generation. The computer program modules may include one or more of a template interface module 106, a contest implementation module 108, a performance determination module 110, an award distribution module 112, and/or other modules. In some implementations, client computing platforms 104 may be configured to execute one or more computer program modules that are the same as or similar to the computer program modules of server(s) 102 to facilitate interface-based game-space contest generation.
Template interface module 106 may be configured to provide a user interface configured to receive user inputs that include one or more performance criteria to be associated with a contest to be provided in a game space, one or more awards to be distributed in association with the contest, one or more qualifications to participate in the contest, and/or other user inputs. Template interface module 106 may be configured to provide the user interface to an administrator to receive the user inputs from the administrator via the user interface.
Along these lines,
As such, in certain implementations, the performance criteria may relate to success with respect to the contest to be provided in the game space. The success-related performance criteria may relate to one or more of resource collection, building possession, combat (e.g., between user characters and/or non-user characters), rescues (e.g., of user characters and/or non-user characters), level progress, and/or other game-space features. For example, with respect to
In some implementations, the qualifications to participate in the contest may include merit-based qualifications associated with the game space. The merit-based qualifications may relate to one or more of possessed structures, collected resources, combat history, rescue history, user level, and/or other game-space features. For example, with respect to
In various implementations, the qualifications to participate in the contest may include non-merit-based qualifications. The non-merit-based qualifications may include contest participation fees, user age requirements, server requirements (e.g., a contest may be limited to users with accounts hosted on particular servers), location requirements (e.g., the contest may be limited to users with characters in particular areas of the game space, users located in particular areas of the real world, etc.), or other non-merit-based qualifications.
In some implementations, the game space may be a virtual space. An instance of the game space may be an instance of the virtual space. A space module may be configured to implement the instance of the virtual space executed by the computer modules. The instance of the virtual space may reflect the state of the virtual space. The instance of the virtual space may be used to push state information to clients for implementation on the clients, may be used to verify state information generated on clients executing expressions of the instance locally, and/or for other purposes. State information may include information about the state of the virtual space such as, without limitation, position information of one or more objects, topography information, object status/shape information, battle information, score information, user or character progress information, user inventory information, progress information for one or more activities or actions, view information describing a view of the virtual space, and/or other information that describes the state of the virtual space. Expressions of the instance executed on the clients facilitate presentation of views on the clients of the virtual space. Expressions of the instance executed on the clients may be configured to simply present views of the virtual space based on the state information (e.g., via streaming view information, object/position information, and/or other state information) received from the space module. Expressions of the instance executed on the clients may include space logic that effectively provides for execution of a limited version of the instance on a client that is synchronized and/or verified with state information received from the space module. The view presented on a given client may correspond to a location in the virtual space (e.g., the location from which the view is taken, the location the view depicts, and/or other locations), a zoom ratio, a dimensionality of objects, a point-of-view, and/or view parameters. One or more of the view parameters may be selectable by the user.
The instance of the virtual space may comprise a simulated space that is accessible by users via clients (e.g., client computing platforms 104) that present the views of the virtual space to a user. The simulated space may have a topography, express ongoing real-time interaction by one or more users, and/or include one or more objects positioned within the topography that are capable of locomotion within the topography. In some instances, the topography may be a 2-dimensional topography. In other instances, the topography may be a 3-dimensional topography. The topography may include dimensions of the space, and/or surface features of a surface or objects that are “native” to the space. In some instances, the topography may describe a surface (e.g., a ground surface) that runs through at least a substantial portion of the space. In some instances, the topography may describe a volume with one or more bodies positioned therein (e.g., a simulation of gravity-deprived space with one or more celestial bodies positioned therein). The instance executed by the computer modules may be synchronous, asynchronous, and/or semi-synchronous.
The above description of the views of the virtual space determined from the instance executed by the space module is not intended to be limiting. The virtual space may be presented in a more limited, or more rich, manner. For example, views of the virtual space may be selected from a limited set of graphics depicting an event in a given place within the virtual space. The views may include additional content (e.g., text, audio, pre-stored video content, and/or other content) that describes particulars of the current state of the place, beyond the relatively generic graphics. For example, a view may include a generic battle graphic with a textual description of the opponents to be confronted. Other representations of individual places within the virtual space are contemplated.
Within the instance of the virtual space executed by the space module, users may control characters, objects, simulated physical phenomena (e.g., wind, rain, earthquakes, and/or other phenomena), and/or other elements within the virtual space to interact with the virtual space and/or each other. The user characters may include avatars. As used herein, the term “user character” may refer to an object (or group of objects) present in the virtual space that represents an individual user. The user character may be controlled by the user with which it is associated. The user controlled element(s) may move through and interact with the virtual space (e.g., non-user characters in the virtual space, other objects in the virtual space). The user controlled elements controlled by and/or associated with a given user may be created and/or customized by the given user. The user may have an “inventory” of virtual goods and/or currency that the user can use (e.g., by manipulation of a user character or other user controlled element, and/or other items) within the virtual space.
The users may participate in the instance of the virtual space by controlling one or more of the available user controlled elements in the virtual space. Control may be exercised through control inputs and/or commands input by the users through client computing platforms 104. The users may interact with each other through communications exchanged within the virtual space. Such communications may include one or more of textual chat, instant messages, private messages, voice communications, and/or other communications. Communications may be received and entered by the users via their respective client computing platforms 104. Communications may be routed to and from the appropriate users through server(s) 102 (e.g., through a space module).
Contest implementation module 108 may be configured to provide, based on the user inputs, a notification in the game space that relates to the contest. For example, the notification may be provided based on the performance criteria to be associated with the contest, the awards to be distributed in association with the content, and/or the qualifications to participate in the contest that are received as one or more of the user inputs. In various implementations, for instance, the notification may indicate one or more of the users that are qualified to enter the contest based on the qualifications to participate in the contest. In some implementations, the notification may indicate the performance criteria, the awards, and/or the qualifications. In this way, users of the game space may be informed of the contest, be incentivized to participate in the contest (e.g., in response to the notification of the awards), become more engaged in the game space (e.g., to become qualified to participate in the contest before a qualification deadline), and/or provide other benefits.
By way of example,
In certain implementations, contest implementation module 108 may execute the contest in the game space based on the user inputs. In one scenario, content implementation module 108 may set the contest period to be from the user-inputted start date/time until the user-inputted end date/time. As an example, activities of the contest may be made available to the participating users during the contest period. As another example, activities of the contest may be activities that can be performed by users (without regard to the contest) in the game space but those activities may be monitored for the participating users in association with the contest during the contest period to determine performance scores of the participating users that perform the activities. Contest-related activities may include collecting resources, constructing or otherwise obtaining buildings, engaging in combat, performing rescues, selling merchandise, collecting items, and/or other activities. In another scenario, user-inputted awards may be distributed to the participating users throughout the duration of the contest period, at the end of the contest period, or at other times in accordance with the determined performance scores of the participating users.
As such, performance determination module 110 may be configured to determine, based on the performance criteria and activities that are performed in the game space by the users that participated in the contest, performance scores of the participating users. Award distribution module 112 may be configured to facilitate automated distribution of the awards to individual ones of the participating users in accordance with the performance scores of the individual participating users. For example, in one use case, the activity may be collecting a specific type of resource (e.g., diamond, gold, silver, platinum, iron, wheat, etc.) and the performance criteria may include having the most amounts of the specific type of resource collected during the contest period. As such, participating users that have collected more of the specific type of the resource than other participating users during the contest period may be assigned higher performance score than those other participating users. Thus, awards may be automatically distributed to a certain number of the participating users that collect the most amounts of the specific type of resource during the contest period (e.g., at the end of the contest period, at one or more intervals during the contest period, etc.). The awards may include virtual items, virtual currency, buildings, resources, access to other contests, access to regions in the game space, access to activities in the game space, respect, multipliers (e.g., 10× respect), level increase, and/or other awards.
In various implementations, award distribution module 112 may be configured such that at least one of the awards is distributed to at least one of the participating users in response to the performance scores of the at least one participating user satisfying one or more performance thresholds. By way of example, a particular contest in the game space may provide awards to participating users that satisfy a certain performance threshold. In one use case, the particular contest may be configured such that a participating user may be provided with an award associated with the contest if the participating user harvests a specific predetermined amount of resources during the contest period (e.g., harvesting 5000 units of wood, harvesting 2000 units of wheat, etc.). The participating user may, for instance, be provided with the award during or after the contest period in response to determining that the participating user satisfied the specific resource harvesting threshold during the contest period.
In another use case, the participating user may be provided with multiple awards for satisfying multiple performance thresholds. For example, the participating user may be provided with one award after the participating user harvests a first amount of resources (e.g., 5000 units of wood) during the contest period, and a different award after the participating user harvests a second amount of resources (e.g., 12,000 units of wood). In this way, users may be provided with a plurality of incentives to sign up, participate, and/or continue to participate in the game-space contest. The awards may, for instance, be automatically distributed to the participating user in real-time as soon as the participating user completes each set of activities to satisfy the performance thresholds. As such, wait time associated with distribution of the awards may be eliminated or otherwise reduced.
In certain implementations, award distribution module 112 may be configured such that the awards are distributed based on one or more predetermined intervals of the contest. By way of example, a particular contest may last for a period of one week, each day of the contest may represent one time interval of the contest, and award distribution module 112 may be configured to distribute the awards at the end of each day to individual participating users that are determined to have satisfied one or more performance thresholds.
In some implementations, award distribution module 112 may be configured such that a first award of the awards is distributed during a first predetermined interval of the predetermined intervals to a first participating user of the participating users in response to the performance scores of the first participating user satisfying a first performance threshold during the first predetermined interval, and such that a second award of the awards is distributed during a second predetermined interval of the predetermined intervals to the first participating user in response to the performance scores of the first participating user satisfying a second performance threshold during the second predetermined interval.
In one scenario, a particular contest in the game space may last for a period of one week, and each day of the contest may represent one time interval of the contest. The contest may provide awards to participating users for each day that the participating users perform activities that satisfy a performance threshold. For example, a participating user may be provided with 1000 units of wood when the participating user logs into the game space on the first day of the contest (e.g., logging into the game space may be a predefined activity for satisfying a performance threshold). The participating user may be provided with 1500 units of iron when the participating user logs into the game space on the second day of the contest. The participating user may be provided with 2000 units of wheat when the participating user logs into the game space on the third day of the contest, and so on. In this way, among other benefits, contests may enable participating users to develop habits based on the predefined activities (e.g., logging in on a regular basis), encourage a steady stream of activities by participating users, etc.
In various implementations, template interface module 106 may be configured to store a template that indicates the user inputs. As such, in some implementations, the contest may be executed in the game space based on the stored template. The contest may, for instance, be executed based on a predetermined schedule, a periodic basis, a manual user activation, and/or other trigger using the user inputs indicated in the stored template. In one scenario, a game-space contest created via interface-based game-space contest generation that attracted a substantial number of participating users may be reinitiated so that the contest may be repeated in accordance with a predetermined schedule or via a manual user activation of the contest by using the template to provide the user inputs for the contest.
Server(s) 102, client computing platforms 104, external resources 114, and/or other components may be operatively linked via one or more electronic communication links. For example, such electronic communication links may be established, at least in part, via a network such as the Internet and/or other networks. It will be appreciated that this is not intended to be limiting, and that the scope of this disclosure includes implementations in which server(s) 102, client computing platforms 104, external resources 114, and/or other components may be operatively linked via some other communication media.
A given client computing platform 104 may include one or more processors configured to execute computer program modules. The computer program modules may be configured to enable an expert or user associated with client computing platform 104 to interface with system 100 and/or external resources 114, and/or provide other functionality attributed herein to client computing platforms 104. By way of non-limiting example, client computing platform 104 may include one or more of a desktop computer, a laptop computer, a handheld computer, a netbook, a smartphone, a gaming console, and/or other computing platforms.
External resources 114 may include sources of information, hosts and/or providers of virtual spaces outside of system 100, external entities participating with system 100, and/or other resources. In some implementations, some or all of the functionality attributed herein to external resources 114 may be provided by resources included in system 100.
In some implementations, server(s) 102 may include an electronic storage 116, one or more processor(s) 118, and/or other components. Server(s) 102 may include communication lines, or ports to enable the exchange of information with a network and/or other computing platforms. Illustration of server(s) 102 in
Electronic storage 116 may include electronic storage media that electronically stores information. In some implementations, the electronic storage media of electronic storage 116 may include one or both of system storage that is provided integrally (i.e., substantially non-removable) with server(s) 102 and/or removable storage that is removably connectable to server(s) 102 via, for example, a port (e.g., a USB port, a firewire port, etc.) or a drive (e.g., a disk drive, etc.). Electronic storage 116 may include one or more of optically readable storage media (e.g., optical disks, etc.), magnetically readable storage media (e.g., magnetic tape, magnetic hard drive, floppy drive, etc.), electrical charge-based storage media (e.g., EEPROM, RAM, etc.), solid-state storage media (e.g., flash drive, etc.), and/or other electronically readable storage media. Electronic storage 116 may include one or more virtual storage resources (e.g., cloud storage, a virtual private network, and/or other virtual storage resources). Electronic storage 116 may store software algorithms, information determined by processor(s) 118, information received from server(s) 102, information received from client computing platforms 104, and/or other information that enables server(s) 102 and/or client computing platforms 104 to function as described herein. It should be noted that, in certain implementations, electronic storage 116 may be a part of server(s) 102, a part of a given client computing platform 104, and/or a separate component of system 100.
In some implementations, processor(s) 118 is configured to provide information processing capabilities in server(s) 102. As such, processor(s) 118 may include one or more of a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information. Although processor(s) 118 is shown in
It should be appreciated that although modules 106, 108, 110, and 112 are illustrated in
In some implementations, method 400 may be implemented in one or more processing devices (e.g., a digital processor, an analog processor, a digital circuit designed to process information, an analog circuit designed to process information, a state machine, and/or other mechanisms for electronically processing information). The one or more processing devices may include one or more devices executing some or all of the operations of method 400 in response to instructions stored electronically on an electronic storage medium. The one or more processing devices may include one or more devices configured through hardware, firmware, and/or software to be specifically designed for execution of one or more of the operations of method 400.
At an operation 402, user inputs that relate to a contest to be provided in a game space may be received from an administrator via a user interface. The user inputs may include one or more performance criteria to be associated with the contest, one or more awards to be distributed in association with the contest, one or more qualifications to participate in the contest, and/or other user inputs. The game space may be configured to facilitate interaction of users with the game space and/or each other by performing operations in the game space in response to commands received from the users. In certain implementations, the performance criteria may relate to success with respect to the contest. The success-related performance criteria may relate to one or more of resource collection, building possession, combat, rescues, or level progress. In some implementations, the qualifications include merit-based qualifications associated with the game space. The merit-based qualifications may relate to one or more of possessed structures, collected resources, combat history, rescue history, or user level. Operation 402 may be performed by a template interface module that is the same as or similar to template interface module 106, in accordance with one or more implementations.
At an operation 404, a template that indicates the user inputs may be stored. As such, in some implementations, the contest may be executed in the game space based on the stored template. The contest may, for instance, be executed based on a predetermined schedule, a periodic basis, a manual user activation, and/or other trigger using the user inputs indicated in the stored template. Operation 404 may be performed by a template interface module that is the same as or similar to template interface module 106, in accordance with one or more implementations.
At an operation 406, a notification that relates to the contest may be provided in the game space based on the user inputs. For example, the notification may be provided based on the performance criteria, the awards, and/or the qualifications that are received as user inputs from the administrator via the user interface. In some implementations, the notification may indicate one or more of the users that are qualified to enter the contest. Operation 406 may be performed by a contest implementation module that is the same as or similar to contest implementation module 108, in accordance with one or more implementations.
At an operation 408, the contest may be executed in the game space based on the user inputs. For example, the contest may be executed based on the performance criteria, the awards, and/or the qualifications that are received as user inputs from the administrator via the user interface. Operation 408 may be performed by a contest implementation module that is the same as or similar to contest implementation module 108, in accordance with one or more implementations.
At an operation 410, activities that are performed in the game space by the users participating in the contest may be monitored. Operation 410 may be performed by a performance determination module that is the same as or similar to performance determination module 110, in accordance with one or more implementations.
At an operation 412, performance scores of the participating users may be determined based on the performance criteria and the performed activities of the participating users. Operation 412 may be performed by a performance determination module that is the same as or similar to performance determination module 110, in accordance with one or more implementations.
At an operation 414, automated distribution of the awards to individual ones of the participating users may be facilitated in accordance with the performance scores of the individual participating users. Operation 414 may be performed by an award distribution module that is the same as or similar to award distribution module 112, in accordance with one or more implementations.
In certain implementations, with respect to operation 414, the automated distribution may be facilitated such that the awards are distributed to the individual participating users based on one or more predetermined intervals of the contest. In some implementations, the automated distribution may be facilitated such that a first award of the awards is distributed during a first predetermined interval of the predetermined intervals to a first participating user of the participating users in response to the performance scores of the first participating user satisfying a first performance threshold during the first predetermined interval, and such that a second award of the awards is distributed during a second predetermined interval of the predetermined intervals to the first participating user in response to the performance scores of the first participating user satisfying a second performance threshold during the second predetermined interval.
Although the present invention has been described in detail for the purpose of illustration based on what is currently considered to be the most practical and preferred implementations, it is to be understood that such detail is solely for that purpose and that the invention is not limited to the disclosed implementations, but, on the contrary, is intended to cover modifications and equivalent arrangements that are within the spirit and scope of the appended claims. For example, it is to be understood that the present invention contemplates that, to the extent possible, one or more features of any implementation can be combined with one or more features of any other implementation.
Number | Name | Date | Kind |
---|---|---|---|
5816918 | Kelly et al. | Oct 1998 | A |
5933813 | Teicher | Aug 1999 | A |
5964660 | James | Oct 1999 | A |
6142472 | Kliebisch | Nov 2000 | A |
6190225 | Coleman | Feb 2001 | B1 |
6402619 | Sato | Jun 2002 | B1 |
6604008 | Chudley | Aug 2003 | B2 |
6745236 | Hawkins | Jun 2004 | B1 |
6850900 | Hare | Feb 2005 | B1 |
6928474 | Venkatesan | Aug 2005 | B2 |
7050868 | Graepel | May 2006 | B1 |
7076453 | Jammes | Jul 2006 | B2 |
7156733 | Chiang | Jan 2007 | B2 |
7192352 | Walker | Mar 2007 | B2 |
7197352 | Gott | Mar 2007 | B2 |
7326115 | Baerlocher | Feb 2008 | B2 |
7533336 | Jaffe | May 2009 | B2 |
7660740 | Boone | Feb 2010 | B2 |
7698229 | Hsu | Apr 2010 | B2 |
7813821 | Howell | Oct 2010 | B1 |
7819749 | Fish et al. | Oct 2010 | B1 |
8016668 | Hardy | Sep 2011 | B2 |
8066571 | Koster et al. | Nov 2011 | B2 |
8105156 | Walker et al. | Jan 2012 | B2 |
8147340 | Brunet de Courssou et al. | Apr 2012 | B2 |
8157635 | Hardy | Apr 2012 | B2 |
8187101 | Herrmann | May 2012 | B2 |
8226472 | Van Luchene | Jul 2012 | B2 |
8231453 | Wolf et al. | Jul 2012 | B2 |
8231470 | Feeney et al. | Jul 2012 | B2 |
8246439 | Kelly et al. | Aug 2012 | B2 |
8272934 | Olive et al. | Sep 2012 | B2 |
8272951 | Ganz | Sep 2012 | B2 |
8272956 | Kelly | Sep 2012 | B2 |
8282491 | Auterio | Oct 2012 | B2 |
8287367 | Hall et al. | Oct 2012 | B2 |
8287383 | Etter | Oct 2012 | B1 |
8287384 | Auterio | Oct 2012 | B2 |
8292743 | Etter | Oct 2012 | B1 |
8313372 | Naicker et al. | Nov 2012 | B2 |
8317584 | Aoki et al. | Nov 2012 | B2 |
8323110 | Shibamiya et al. | Dec 2012 | B2 |
8328642 | Mosites et al. | Dec 2012 | B2 |
8332260 | Mysen | Dec 2012 | B1 |
8332544 | Ralls | Dec 2012 | B1 |
8348762 | Willis | Jan 2013 | B2 |
8348767 | Mahajan | Jan 2013 | B2 |
8348768 | Auterio et al. | Jan 2013 | B2 |
8360858 | LaRocca | Jan 2013 | B2 |
8360866 | VanLuchene | Jan 2013 | B2 |
8360867 | Van Luchene | Jan 2013 | B2 |
8360868 | Shvili | Jan 2013 | B2 |
8366544 | Walker | Feb 2013 | B2 |
8366550 | Herrmann et al. | Feb 2013 | B2 |
8382572 | Hoffman | Feb 2013 | B2 |
8388427 | Yariv | Mar 2013 | B2 |
8401913 | Alivandi | Mar 2013 | B2 |
8408989 | Bennett et al. | Apr 2013 | B2 |
8475262 | Wolf et al. | Jul 2013 | B2 |
8506394 | Kelly et al. | Aug 2013 | B2 |
8533076 | Chu | Sep 2013 | B2 |
8583266 | Herbrich et al. | Nov 2013 | B2 |
8636591 | Hawk | Jan 2014 | B1 |
8758119 | BronsteinBendayan | Jun 2014 | B1 |
8784214 | Parks et al. | Jul 2014 | B2 |
8821260 | Desanti | Sep 2014 | B1 |
8831758 | Chu | Sep 2014 | B1 |
8843557 | Ranade | Sep 2014 | B2 |
8851978 | Koh | Oct 2014 | B1 |
8920243 | Curtis | Dec 2014 | B1 |
8961319 | Pieron | Feb 2015 | B1 |
8968067 | Curtis et al. | Mar 2015 | B1 |
9007189 | Curtis et al. | Apr 2015 | B1 |
9138639 | Ernst | Sep 2015 | B1 |
9256887 | Santini | Feb 2016 | B2 |
9257007 | Santini | Feb 2016 | B2 |
9259642 | McNeill | Feb 2016 | B1 |
9286510 | Soohoo | Mar 2016 | B2 |
9317993 | Hardy | Apr 2016 | B2 |
9375636 | Wakeford | Jun 2016 | B1 |
9403093 | Harrington | Aug 2016 | B2 |
9406201 | Englman | Aug 2016 | B2 |
9452356 | Tsao | Sep 2016 | B1 |
9452364 | Curtis | Sep 2016 | B1 |
9463376 | Kim | Oct 2016 | B1 |
9468851 | Pieron | Oct 2016 | B1 |
9610503 | Pieron | Apr 2017 | B2 |
9626475 | Schultz | Apr 2017 | B1 |
9656174 | McLellan | May 2017 | B1 |
9669313 | Pieron | Jun 2017 | B2 |
9682314 | Kim | Jun 2017 | B2 |
20020023039 | Fritsch | Feb 2002 | A1 |
20020059397 | Feola | May 2002 | A1 |
20020094863 | Klayh | Jul 2002 | A1 |
20020095327 | Zumel | Jul 2002 | A1 |
20020115488 | Berry et al. | Aug 2002 | A1 |
20020119824 | Allen | Aug 2002 | A1 |
20020165794 | Ishihara | Nov 2002 | A1 |
20020183105 | Cannon et al. | Dec 2002 | A1 |
20020193162 | Walker et al. | Dec 2002 | A1 |
20030008713 | Ushiro et al. | Jan 2003 | A1 |
20030032476 | Walker | Feb 2003 | A1 |
20030157978 | Englman | Aug 2003 | A1 |
20030174178 | Hodges | Sep 2003 | A1 |
20030190960 | Jokipii et al. | Oct 2003 | A1 |
20040002387 | Grady | Jan 2004 | A1 |
20040068451 | Lenk | Apr 2004 | A1 |
20040143852 | Meyers | Jul 2004 | A1 |
20040199471 | Hardjono | Oct 2004 | A1 |
20040215524 | Parkyn | Oct 2004 | A1 |
20040224745 | Bregenzer | Nov 2004 | A1 |
20040225387 | Smith, III | Nov 2004 | A1 |
20040267611 | Hoerenz | Dec 2004 | A1 |
20050096117 | Katz et al. | May 2005 | A1 |
20050114223 | Schneider | May 2005 | A1 |
20050165686 | Zack | Jul 2005 | A1 |
20050255914 | McHale | Nov 2005 | A1 |
20060030407 | Thayer | Feb 2006 | A1 |
20060058103 | Danieli | Mar 2006 | A1 |
20060100006 | Mitchell | May 2006 | A1 |
20060155597 | Gleason | Jul 2006 | A1 |
20060200370 | Ratliff | Sep 2006 | A1 |
20060217198 | Johnson | Sep 2006 | A1 |
20060287102 | White et al. | Dec 2006 | A1 |
20070021213 | Foe et al. | Jan 2007 | A1 |
20070077988 | Friedman | Apr 2007 | A1 |
20070105615 | Lind | May 2007 | A1 |
20070111770 | Van Luchene | May 2007 | A1 |
20070129147 | Gagner | Jun 2007 | A1 |
20070155485 | Cuddy et al. | Jul 2007 | A1 |
20070191101 | Coliz | Aug 2007 | A1 |
20070191102 | Coliz et al. | Aug 2007 | A1 |
20070213116 | Crawford et al. | Sep 2007 | A1 |
20070233585 | Ben Simon | Oct 2007 | A1 |
20070281285 | Jayaweera | Dec 2007 | A1 |
20080004093 | Van Luchene | Jan 2008 | A1 |
20080032787 | Low | Feb 2008 | A1 |
20080076527 | Low | Mar 2008 | A1 |
20080113815 | Weingardt | May 2008 | A1 |
20080124353 | Brodeur | May 2008 | A1 |
20080154798 | Valz | Jun 2008 | A1 |
20080171599 | Salo et al. | Jul 2008 | A1 |
20080194318 | Kralicky | Aug 2008 | A1 |
20080200260 | Deng | Aug 2008 | A1 |
20080214295 | Dabrowski | Sep 2008 | A1 |
20080234043 | McCaskey | Sep 2008 | A1 |
20080268946 | Roemer | Oct 2008 | A1 |
20080275786 | Gluck | Nov 2008 | A1 |
20090011812 | Katz | Jan 2009 | A1 |
20090017886 | McGucken | Jan 2009 | A1 |
20090036199 | Myus | Feb 2009 | A1 |
20090048918 | Dawson | Feb 2009 | A1 |
20090061982 | Brito | Mar 2009 | A1 |
20090082099 | Luciano, Jr. et al. | Mar 2009 | A1 |
20090204907 | Finn | Aug 2009 | A1 |
20090208181 | Cottrell | Aug 2009 | A1 |
20090210301 | Porter | Aug 2009 | A1 |
20090234710 | Belgaied Hassine | Sep 2009 | A1 |
20090280905 | Weisman | Nov 2009 | A1 |
20090315893 | Smith et al. | Dec 2009 | A1 |
20100022307 | Steuer et al. | Jan 2010 | A1 |
20100035689 | Altshuler | Feb 2010 | A1 |
20100041472 | Gagner | Feb 2010 | A1 |
20100050088 | Neustaedter | Feb 2010 | A1 |
20100070056 | Coronel | Mar 2010 | A1 |
20100094841 | Bardwil | Apr 2010 | A1 |
20100099471 | Feeney et al. | Apr 2010 | A1 |
20100107214 | Ganz | Apr 2010 | A1 |
20100113162 | Vemuri et al. | May 2010 | A1 |
20100174593 | Cao | Jul 2010 | A1 |
20100198653 | Bromenshenkel | Aug 2010 | A1 |
20100210356 | Losica | Aug 2010 | A1 |
20100227682 | Reville et al. | Sep 2010 | A1 |
20100228606 | Walker | Sep 2010 | A1 |
20100241491 | Eglen | Sep 2010 | A1 |
20100306015 | Kingston | Dec 2010 | A1 |
20110045898 | Anderson | Feb 2011 | A1 |
20110065511 | Mahan | Mar 2011 | A1 |
20110092271 | Nguyen | Apr 2011 | A1 |
20110092273 | Cerbini | Apr 2011 | A1 |
20110111841 | Tessmer | May 2011 | A1 |
20110112662 | Thompson | May 2011 | A1 |
20110113353 | Koh | May 2011 | A1 |
20110118002 | Aoki | May 2011 | A1 |
20110145040 | Zahn | Jun 2011 | A1 |
20110212756 | Packard | Sep 2011 | A1 |
20110218033 | Englman et al. | Sep 2011 | A1 |
20110227919 | Bongio et al. | Sep 2011 | A1 |
20110250954 | Braund | Oct 2011 | A1 |
20110256936 | Walker et al. | Oct 2011 | A1 |
20110281638 | Bansi | Nov 2011 | A1 |
20110281654 | Kelly | Nov 2011 | A1 |
20110282764 | Borst | Nov 2011 | A1 |
20110300923 | Van Luchene | Dec 2011 | A1 |
20110319170 | Shimura et al. | Dec 2011 | A1 |
20120011002 | Crowe | Jan 2012 | A1 |
20120015714 | Ocko et al. | Jan 2012 | A1 |
20120015715 | Luxton et al. | Jan 2012 | A1 |
20120034961 | Berman et al. | Feb 2012 | A1 |
20120040743 | Auterio | Feb 2012 | A1 |
20120040761 | Auterio | Feb 2012 | A1 |
20120042282 | Wong | Feb 2012 | A1 |
20120046111 | Walker | Feb 2012 | A1 |
20120047002 | Patel | Feb 2012 | A1 |
20120059730 | Jensen | Mar 2012 | A1 |
20120083909 | Carpenter et al. | Apr 2012 | A1 |
20120101886 | Subramanian | Apr 2012 | A1 |
20120108306 | Munsell | May 2012 | A1 |
20120109785 | Karlsson | May 2012 | A1 |
20120115593 | Vann | May 2012 | A1 |
20120122589 | Kelly | May 2012 | A1 |
20120130856 | Petri | May 2012 | A1 |
20120142429 | Muller | Jun 2012 | A1 |
20120156668 | Zelin | Jun 2012 | A1 |
20120157187 | Moshal | Jun 2012 | A1 |
20120166380 | Sridharan | Jun 2012 | A1 |
20120166449 | Pitaliya | Jun 2012 | A1 |
20120178514 | Schulzke | Jul 2012 | A1 |
20120178529 | Collard | Jul 2012 | A1 |
20120197874 | Zatkin | Aug 2012 | A1 |
20120202589 | Kelly | Aug 2012 | A1 |
20120203669 | Borsch | Aug 2012 | A1 |
20120215667 | Ganz | Aug 2012 | A1 |
20120221430 | Naghmouchi | Aug 2012 | A1 |
20120226573 | Zakas et al. | Sep 2012 | A1 |
20120231891 | Watkins, Jr. | Sep 2012 | A1 |
20120244947 | Ehrlich | Sep 2012 | A1 |
20120244950 | Braun | Sep 2012 | A1 |
20120245988 | Pace | Sep 2012 | A1 |
20120256377 | Schneider et al. | Oct 2012 | A1 |
20120265604 | Corner | Oct 2012 | A1 |
20120282986 | Castro | Nov 2012 | A1 |
20120289315 | Van Luchene | Nov 2012 | A1 |
20120289346 | Van Luchene | Nov 2012 | A1 |
20120295699 | Reiche | Nov 2012 | A1 |
20120296716 | Barbeau | Nov 2012 | A1 |
20120302335 | Gregory-Brown | Nov 2012 | A1 |
20120309504 | Isozaki | Dec 2012 | A1 |
20120311504 | Van Os et al. | Dec 2012 | A1 |
20120322545 | Arnone et al. | Dec 2012 | A1 |
20120322561 | Kohlhoff | Dec 2012 | A1 |
20120329549 | Johnson | Dec 2012 | A1 |
20120330785 | Hamick et al. | Dec 2012 | A1 |
20130005437 | Bethke | Jan 2013 | A1 |
20130005466 | Mahajan | Jan 2013 | A1 |
20130005473 | Bethke | Jan 2013 | A1 |
20130005480 | Bethke | Jan 2013 | A1 |
20130006735 | Koenigsberg et al. | Jan 2013 | A1 |
20130006736 | Bethke | Jan 2013 | A1 |
20130012304 | Cartwright | Jan 2013 | A1 |
20130013094 | Parks et al. | Jan 2013 | A1 |
20130013326 | Miller et al. | Jan 2013 | A1 |
20130013459 | Kerr | Jan 2013 | A1 |
20130029745 | Kelly et al. | Jan 2013 | A1 |
20130036064 | Osvald | Feb 2013 | A1 |
20130090173 | Kislyi | Apr 2013 | A1 |
20130090750 | Herrman et al. | Apr 2013 | A1 |
20130123005 | Allen et al. | May 2013 | A1 |
20130124361 | Bryson | May 2013 | A1 |
20130151342 | Citron et al. | Jun 2013 | A1 |
20130178259 | Strause et al. | Jul 2013 | A1 |
20130217453 | Briggs | Aug 2013 | A1 |
20130217489 | Bendayan | Aug 2013 | A1 |
20130226733 | Evans | Aug 2013 | A1 |
20130237299 | Bancel et al. | Sep 2013 | A1 |
20130244767 | Barclay et al. | Sep 2013 | A1 |
20130260850 | Carpe | Oct 2013 | A1 |
20130288757 | Guthridge | Oct 2013 | A1 |
20130288787 | Yoshie | Oct 2013 | A1 |
20130303276 | Weston et al. | Nov 2013 | A1 |
20130303726 | Mozzarelli | Nov 2013 | A1 |
20130324259 | Mccaffrey | Dec 2013 | A1 |
20130339111 | Ross | Dec 2013 | A1 |
20130339228 | Shuster | Dec 2013 | A1 |
20130344932 | Adams et al. | Dec 2013 | A1 |
20140004884 | Chang | Jan 2014 | A1 |
20140011565 | Elias | Jan 2014 | A1 |
20140018156 | Rizzotti et al. | Jan 2014 | A1 |
20140033262 | Anders | Jan 2014 | A1 |
20140038721 | Archer | Feb 2014 | A1 |
20140067526 | Raju | Mar 2014 | A1 |
20140067544 | Klish | Mar 2014 | A1 |
20140073436 | Takagi | Mar 2014 | A1 |
20140087864 | Togashi | Mar 2014 | A1 |
20140089048 | Bruich | Mar 2014 | A1 |
20140100020 | Carroll | Apr 2014 | A1 |
20140106858 | Constable | Apr 2014 | A1 |
20140157314 | Roberts | Jun 2014 | A1 |
20140180725 | Ton-That | Jun 2014 | A1 |
20140206449 | Alman | Jul 2014 | A1 |
20140206452 | Bambino | Jul 2014 | A1 |
20140243065 | Wright | Aug 2014 | A1 |
20140243072 | Santini | Aug 2014 | A1 |
20140274359 | Helava | Sep 2014 | A1 |
20140295958 | Shono | Oct 2014 | A1 |
20140309026 | Inukai | Oct 2014 | A1 |
20140329585 | Santini | Nov 2014 | A1 |
20140337259 | Lamb | Nov 2014 | A1 |
20150011305 | Deardorff | Jan 2015 | A1 |
20150019349 | Milley | Jan 2015 | A1 |
20150065241 | McCarthy | Mar 2015 | A1 |
20150065256 | Cudak | Mar 2015 | A1 |
20150273320 | Pieron | Oct 2015 | A1 |
20150306494 | Pieron | Oct 2015 | A1 |
20150335995 | Mclellan | Nov 2015 | A1 |
20150352436 | Pieron | Dec 2015 | A1 |
20160121219 | Kim | May 2016 | A1 |
20160236094 | Pieron | Aug 2016 | A1 |
20160361654 | Pieron | Dec 2016 | A1 |
Number | Date | Country |
---|---|---|
1020130137431 | Dec 2013 | KR |
WO 2013059639 | Apr 2013 | WO |
2015013373 | Jan 2015 | WO |
2015153010 | Oct 2015 | WO |
2015168187 | Nov 2015 | WO |
2015179450 | Nov 2015 | WO |
2015196105 | Dec 2015 | WO |
Entry |
---|
Quest item—WoWWiki—Your guide to the World of Warcraft <URL: http://www.wowwiki.com/Quest—Item> Retrieved on Apr. 16, 2014, 1 page. |
PCT International Search Report and Written Opinion for PCT/US2016/017637 dated Apr. 7, 2016, 12 pages. |
“Building Structures”. War2.warcraft.org. Online. Accessed via the Internet. Accessed Aug. 9, 2014. <URL: http://war2.warcraft.org/strategy/verybasics/building.shtml>, 3 pages. |
“Clash of Clans”. Wikipedia.org. Online. Accessed via the Internet. Accessed Aug. 9, 2014. <URL: http://en.wikipedia.org/wiki/Clash of Clans>, 3 pages. |
“Gem calculation formulas”, forum.supercell.net. Online. Accessed via the Internet. Accessed Aug. 9, 2014. <URL: http://forum.supercell.net/showthread.php/23028-Gem-calculation-formulas>, 3 pages. |
“How Town Hall to Level 4”. Forum.supercell.net. Online. Jan. 31, 2013. Accessed via the Internet. Accessed Feb. 21, 2015. URL:http://forum.supercell.net/showthread.php/15052-How-Town-Hall-to-Level-4, 2 pages. |
“Lotro-Wiki.com” (evidence in regards to “Lord of the Rings Oline” MMORPG game), latest Dec. 22, 2011, http://lotro-wiki.com/index.php/Main—Page) (hereinafter referred to as Lotro>, http://lotro-wiki.com/index.php?title=LOTRO—Store&oldid=396550, http://lotro-wiki.com/index.php?title=Quest:A—Little—Extra—Never—Hurts—--—Part—1&oldid=399597, http://lotro-wiki.com/index.php?title=Quest:A—Little—Extra—Never—Hurts—--. |
“Warcraft II: Tides of Darkness”. Wikipedia.org. Online. Accessed via the Internet. Accessed Aug. 9, 2014. <URL: http://en.wikipedia.org/wiki/Warcraft—II:—Tides—of—Darkness>, 10 pages. |
City Coins. CityVille Wikia. Online. Accessed via the Internet. Accessed Aug. 9, 2014. <URL: http://cityville.wikia.com/wiki/City—Coins>, 2 pages. |
“I don't have enough resources/builders to upgrade anything in my village, what can I do?” gamesupport.supercell.net. Online. Accessed via the Internet. Accessed Aug. 9, 2014. <URL: https://gamesupport.supercell.net/hc/en-us/articles/421482-I-don-t-have-enough-resources-builders-to-upgrade-anything-in-my-village-what-can-I-do >, Apr. 23, 2014, 9 pages. |
“Behavioural Analytics & Campaigning”, http://lotaris.com/behavioural.—analytics—and.—Campaigning.htm, screenshot access date May 24, 2012 2:21 PM, 1 page. |
“Digital River World Payments and Lotaris Partner to Extend Mobile Application Licensing and Monetization Capabilities to Software Publishers”, Business Wire Press Release, http://www.marketwatch.com/story/digital-river-world-payments-and-lotaris . . . , posted San Francisco, Mar. 27, 2012 (Business Wire), 8:30 a.m. EDT, printed May 24, 2012 2:32 PM, 3 pages. |
FriskyMongoose “Happy Island Updates”, available Jun. 12, 2012 from https://web.archive.org/web/20120612004417/http://friskymongoose.com/happy-island-updates-new-attractions-decorations-and-limited-edition-item-bundles/, 7 pages. |
Gaia “Black Friday Bundle” available on Nov. 23, 2011, from http://www.gaiaonline.com/forum/community-announcements/black-friday-big-bundles-rare-items/t.76127933/, 5 pages. |
Hamari, Juho, “Game Design as Marketing: How Game Mechanics Create Demand for Virtual Goods”, available on vol. 5, Issue 1, 2010, retrieved from Int. Journal of Business Science and Applied Management—http://www.business-and-management.org/library/2010/5—1--14-29-Hamari,Lehdonvirta.pdf, on May 26, 2015, 16 pages. |
MMO Site “Rose Online Launches the Newest in Game Feature”; available Aug. 11, 2011 from https://web.archive.org/web/20110811231226/http://news.mmosite.com/content/2011-06-21/rose—online—launches—the—newest—in—game—feature.1.shtml, 3 pages. |
TFWiki “teamfortress wiki” available Nov. 5, 2011 retrieved from https://web.archive.org/web/20111105044256/http://wiki.teamfortress.com/wiki/Loadout, 4 pages. |
UBC, “Theory of Auctions” available on Mar. 24, 2012 from https://web.archive.org/web/20120324204610/http:/montoya.econ.ubc.ca/Econ522/auctions.pdf, slide 5, Para. 1.3, 19 pages. |
Wiki “Gaia online”, available on Sep. 9, 2011, https://web.archive.org/web/20110927210155/http://en.wikipedia.org/wiki/Gaia—Online, 8 pages. |
“Digital River World Payments and Lotaris Partner to Extend Mobile Application Licensing and Monetization Capabilities to Software Publishers”, LOTARIS Press Release, http://www.lotaris.com/digital—river—world—payments—and—lotaris—partne . . . , posted Tuesday, Mar. 27, 2012, screenshop access date May 24, 2012, 2:19 PM, 1 page. |
Ozeagle, “What happens if . . . answers about account types” on Lotro forum, Jan. 18, 2011,<https://www.lotro.com/forums/showthread.php?377885-What-happens-if-answers-about-the-account-types> (16 pgs). |
<http://lotro-wiki.com/index.php?title=Ouest:A—Little—Extra—Never—Hurts—--—Part—2&oldid=399366>, <http://lotrowiki.com/index.php?title=Getting—Started&oldid=349681 >. Links are to used articles. (7 pgs) Feb. 26, 2014. |
“Lotro-Wiki.com” (evidence in regards to “Lord of the Rings Oline” MMORPG game),latest Dec. 22, 2011,<http://lotrowiki.com/index.php/Main—Page)(hereinafter referred to as Lotro>,<http://lotrowiki.com/index.php?title=LOTRO—Store&oldid=396550>,<http://lotrowiki.com/index.php?title=Ouest:A—Little—Extra—Never—Hurts—--—Part—1 &oldid=399597> (28 pgs). |
“A Wondrous Drop Event and Double EXP”, [dated Aug. 22, 2012]. From flyff-wiki. [online], [retrieved on Jan. 12, 2016]. Retrievedfrom the Internet <URL:http://flyff-wiki.webzen.com/wiki/A—Wondrous—Drop—Event—and—Double—EXP>. 2 pages. |
“Flyff”, [dated May 25, 2013]. From Wikipedia, The Free Encylopedia. [on line], [retrieved on Jan. 12, 2016]. Retrieved from the Internet<URL:https://en.wikipedia.org/w/index.php?title=Flyff&oldid=556751091 >. 4 pages. |
“Scroll of Amplification R”, [dated Apr. 26, 2012]. From flyff-wiki. [online], [retrieved on Jan. 12, 2016]. Retrieved from the Internet<URL:http://flyff-wiki.webzen.com/wiki/Scroll—of—Amplification—R>. 3 pages. |
Elsword—Wikipedia, the free encyclopedia, URL: en.wikipedia.org/wiki/Elsword [Retrieved Feb. 21, 2013], 6 pages. |
Katkoff, Michail, “Clash of Clans—the Winning Formula”, Sep. 16, 2012, retrieved from Internet on Sep. 30, 2015 from URL <http://www.deconstructoroffun.com/2012/09/clash-of-clans-winning-formula.html>, 13 pages. |
Path of Exile—Forum—Beta General Discussion—Unique Items Compendium 60/71 URL: web.archive.org/web/20120608004658/http://www.pathofexile.com/forum/view-thread/12056 [Retrieved Jun. 24, 2013], 52 pages. |
Number | Date | Country | |
---|---|---|---|
Parent | 13847981 | Mar 2013 | US |
Child | 14480516 | US |