Patent Application
20160332074
The invention relates generally to video games, and more particularly to a system and method for providing dynamically variable maps in a video game.
In most video games, a map is provided that defines the playable space available to one or more game players. A map may also be referred to as, for example, an area, a stage, a world, a zone, a location, or another similar descriptor. While the particular nature of a map may depend on the type of video game, some non-limiting examples of maps may include a building layout (e.g., one or more floors), a city layout, a forest, a fort, a battlefield, a racetrack, etc. Numerous other examples exist.
In those instances where the same map(s) are played repeatedly in a video game without variety or the introduction of new maps, game players may grow tired of playing the video game after a short period of time.
A lack of maps, or a lack of variety in the maps provided, may result in additional drawbacks for multiplayer video games in which two or more players typically play in a match during a gameplay session in a cooperative or adversarial relationship. One disadvantage of having fewer maps in a multiplayer game (in addition to boredom), is that an appropriate-sized map may not be available for every possible number of players. For instance, a map of a larger scale that is designed (or optimal) for twenty total players in a gameplay session may be too large or challenging (and therefore unsatisfying) for two teams of two players each (four total players). Likewise, a smaller scale map that is designed (or optimal) for eight total players in a gameplay session may be too constrained for two teams of ten players (twenty total players). In either instance, the enjoyment of gameplay may be diminished, resulting in frustrated or discouraged players.
Another example of a drawback associated with a limited number or variety of maps in a multiplayer game is that veteran players may develop more familiarity with available map(s), and hence an unbalanced advantage, over newer players. As such, novice or lower-skilled players, for instance, may feel that they are continually at a disadvantage.
Currently, a “brute force” approach exists to providing game players with more map variety, which is to generate more maps. One disadvantage of this approach is the time and expense required for video game developers to create entirely new maps. Creating new maps may require, among other things, a formidable amount of development time that may negatively impact a developer's ability to provide additional content and/or new titles to consumers. In addition, the new maps must be delivered to the game players' systems, adding additional costs and resources.
Another approach to providing map variety is to limit the availability of certain maps to garners to pre-announced times. For example, a map which might normally be disabled during peak multiplayer gameplay hours may be made available to players at a time when player counts might otherwise be low. This approach, however, also provides disadvantages. For instance, the map that is made available is still a separate map that requires time and expense to create. Further, having a given map available for a limited time period still requires players to play the other available maps in a frequent manner until the pre-announced times, which may result in a poor or unsatisfying player experience.
These and other drawbacks exist with current maps in video games.
The invention addressing these and other drawbacks relates to a system and method for providing dynamically variable maps in a video game.
A dynamically variable (or modifiable) map is a map that defines a playable space available to one or more game players in a video game, and that may be altered from an initial (or first) configuration to a modified (or second) configuration, and so on, during a gameplay session to thereby change the playable space available to the players. In the description that follows, for brevity, the term “map” may be used in lieu of “dynamically variable map.”
According to an aspect of the invention, a map may comprise one or more map features (or attributes) including, for example, a map boundary (or perimeter), one or more static map objects, and one or more dynamic map objects.
A map boundary may define (in whole or in part) an area of playable space available to one or more game players during a gameplay session. As described herein, the map boundary, may be scalable (e.g., may expand or contract) or be otherwise altered during a gameplay session to change the area of available playable space.
Static map objects comprise objects that are typically stationary and may include, without limitation, objects such as a building, a wall, furniture, a tree, a large boulder, a body of water, a mountain, etc. The type of static map objects that may be presented on a map may differ depending on the type of video game.
Dynamic map objects are objects that may be movable from one position to another, or from one state to another. For instance, a vehicle may comprise a dynamic map object, as may a door or drawbridge that is capable of being moved from an open position (or state) to a closed position (or state). Similar to static map objects, the type of dynamic map objects that may be presented on a map may differ depending on the type of video game. In some instances, a dynamic map object may be moved or manipulated to change the area of (or otherwise alter aspects of) the available playable space.
In certain implementations, some static map objects may be considered dynamic map objects if they are capable of being (or are) moved or manipulated during gameplay. For example, a large boulder may comprise a static map object. However, the large boulder may also be considered a dynamic map object if it is capable of being (or is) moved or manipulated by one or more characters or equipment during a gameplay session.
According to an aspect of the invention, various configurations of playable space of a single map may be obtained by dynamically modifying the map boundary, one or more static map objects, and/or one or more dynamic map objects during a gameplay session. More particularly, a map may transform from an initial (or first) configuration to a modified (or second) configuration, and so on, during a gameplay session by altering the map boundary, and/or the location, position, size, number, state, etc. of one or more of static map objects, and/or dynamic map objects based on trigger events that occur during gameplay.
Examples of trigger events may include, but are not limited to, a change in a number of players in the gameplay session (e.g., the number of players exceeds or falls below a predetermined threshold), a change in a number of game players playing a particular player role (e.g., a number of a certain type of player roles in a match exceeds or falls below a predetermined threshold), the pace or frequency of gameplay actions/events exceeding or falling below a predetermined threshold, the commencement of a competition or newly available mission that takes place in a map, an inference that one or more players are unhappy with the current configuration of a map or otherwise would prefer variety (e.g., by monitoring unexpected attrition/rage quitting, or through explicit in-game voting or other feedback), or a change in other gameplay information, among other examples.
Trigger events may be system-defined (e.g., defined by the game logic) or user-defined (e.g., through one or more user interfaces prior to the commencement of a gameplay session). It should be appreciated that trigger events may be different for different maps, different video games, and/or for different maps utilized in the same video game. In some implementations, a collection of defined trigger events may be accessed and selectively applied to individual maps. In other implementations, trigger events may be created or customized for particular maps.
According to an aspect of the invention, a matchmaking engine may identify one or more players that are waiting to be matched (grouped), such as players whose in-game avatars are waiting in a virtual game lobby to join a gameplay session. The gameplay session may comprise any type of gameplay session including, without limitation, a real gameplay session and/or a practice gameplay session (e.g., associated with a “practice” or “training” mode of a game).
In one implementation, a player may be added to a gameplay session immediately if there is an opening. In another implementation, one or more gameplay sessions may be dynamically combined to create a single gameplay session involving the aggregate of all players in each of the original gameplay sessions. A gameplay session may be dynamically split to create two or more gameplay sessions, where a matchmaking engine may determine which players from the original sessions are grouped and placed into the resulting two or more gameplay sessions.
In one implementation, the matchmaking engine may generate one or more matches by grouping two or more of the identified players. The number of players placed in each match (contest) may depend on a number of players waiting to be matched, a number of players needed for a game session (e.g., a number of players needed to form a team or start a match), a number of players that can be accommodated by a game session, and/or other information. Different matches may include different combinations of different players, which may include different numbers of players.
The matchmaking engine may use known or hereafter-developed matchmaking techniques to generate a match by grouping players in an effort to produce the most satisfying player experiences. Game profiles, player profiles, match variables, and other factors may be considered when generating matches.
For clarity, it should be appreciated that the process of “matching” players refers to the grouping of players, and that “matched” players comprise players that have been grouped together (either in a cooperative or adversarial relationship) for a gameplay session by, for example, the matchmaking engine. Further, a “match” may also refer to a contest that is the subject of a gameplay session.
According to an aspect of the invention, a map selection engine may select, generate, or otherwise obtain a map for a match of a gameplay session. In some implementations, the map selection engine may select and retrieve one or more maps from among a collection of pre-generated maps stored, for instance, in one or more databases. Alternatively, the map selection engine may generate one or more maps, or dynamically modify one or more existing maps, in real-time (“on the fly”) for a gameplay session to change the playable space by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s).
In some implementations, a map (whether selected, generated, or modified) may have an initial (or first or beginning) configuration based on gameplay session information. Gameplay session information may describe various game characteristics of a gameplay session that may influence the quality of gameplay. For example, gameplay session information may include, without limitation, a number of players, a composition of teams (e.g., number and/or types of roles in each team), duration of gameplay (e.g., how long a given gameplay session is expected to last), types of matches (e.g., team death match, capture the flag, etc.), and/or other information related to a gameplay session. In another implementation, a map may be selected for a match randomly.
In other implementations, one or more players may select the map to be played in a match of the gameplay session. For instance, before the start of a match, one or more players may vote on the map to be used during the gameplay session.
According to an aspect of the invention, once one or more players have been matched, and a map has been selected, generated, and/or modified, a gameplay session may commence. Gameplay may be monitored in real-time for the detection of a trigger event (e.g., by a trigger detection engine, or other game logic).
According to an aspect of the invention, when a trigger event is detected during gameplay, a map may be dynamically modified (from its initial configuration) as described in detail below. In some implementations, depending on the type of trigger event, detection of the trigger event alone may be sufficient to dynamically modify the map. In other implementations, the gameplay event or action that produced (or resulted in) the triggering event must persist for a predetermined period of time (e.g., a modification waiting period) before the map is dynamically modified. This avoids changing the map frequently when near trigger thresholds, since players may find this confusing or disruptive depending on the game or map design.
In some instances, two or more trigger events may occur during gameplay (and be detected) at substantially the same time. For example, both a number of players and a number of player roles of a certain type may exceed a predetermined threshold at substantially the same time. In such an instance, either or both of the detected trigger events may result in a dynamic modification of the map. For example, in one implementation, the most significant trigger event, as defined by game logic or a user, may be used to dynamically modify a configuration of the map. Alternatively, each trigger event may be used to dynamically modify a configuration of the map. In some implementations, the occurrence of multiple trigger events may reduce the waiting period to dynamically modify the map. For example, if one or more additional trigger events occur during the modification waiting period, the modification waiting period may be truncated. In other implementations, if two or more significant trigger events are detected within a predetermined (e.g., short) period of time, the dynamic map modification may occur immediately without a modification waiting period. Other configurations may be implemented.
In one implementation, a map management engine may dynamically modify a configuration of the map to improve the gameplay experience based on the type of trigger event. Dynamic modification of a map may comprise any one or more of: altering the boundary (or perimeter) of the map by, for example, increasing or decreasing the boundary such that the boundary respectively defines a larger or smaller area of playable space, and/or opening up or closing (or otherwise altering) one or more portions of the boundary; altering the location, position, size, number, state, etc. of one or more static map objects on the map; altering the location, position, size, number, state, etc. of one or more dynamic map objects on the map; scaling the entire map by increasing or decreasing the size of the map and its constituent objects (including any static map objects, dynamic map objects, virtual characters or avatars depicting players, etc.) to increase or decrease the area of available space, respectively; adding or removing non-player characters (NPC) or other artificial intelligence (AI) controlled avatars to the gameplay experience; combining all or a portion of the map with all or a portion of one or more additional maps; and/or modifying the attributes of existing map objects or terrain such that player interaction is fundamentally impacted. As a result of the dynamic modification of the map, the map may transform from its initial (or first or beginning) configuration to a modified (or new or second) configuration.
The following are illustrative and non-limiting examples of the various ways in which a map may be dynamically modified in real-time during gameplay in response to certain trigger events. While the examples described herein may reference various game levels or modes, characters, roles, game items, etc. associated with a First-Person-Shooter (FPS) game, it should be appreciated that any such examples are for illustrative purposes only, and are not intended to be limiting. The system and method described in detail herein may be used in any genre of multiplayer video game, without limitation.
In one implementation, a map be dynamically modified in real-time, during gameplay, based on a trigger event associated with a change in a number of players in the gameplay session (e.g., the number of players exceeds or falls below a predetermined threshold).
As one example, if a number of players during a gameplay session falls below a predetermined number (e.g., a lower or first threshold), the map management engine may switch the state of one or more dynamic map objects (e.g., close a doorway, block a hallway, remove a bridge, etc.) of the map to selectively close off regions of the map, thereby decreasing the available playable space of the map. In this regard, the remaining players may be forced to play in a smaller area which may, depending on the nature of the game, increase encounters with other players to foster more exciting action and gameplay. In some implementations, when a region of a map is selectively closed off (or otherwise dynamically altered), player avatars may be transported out of the non-playable area to another area of the map (e.g., to a standard safe spawn site). Alternatively, player avatars may be spawned elsewhere after a death (or other game event), and the region of the map to be closed may be closed once no more player avatars are in the region.
Conversely, if a number of players during a gameplay session exceeds a predetermined number (e.g., a higher or second threshold number), the map management engine may switch the state of one or more dynamic map objects (e.g., open a doorway, unblock a hallway, add/open a bridge, etc.) of the map to selectively open up additional regions of the map, thereby increasing the available playable space of the map.
In one implementation, a map may be dynamically modified in real-time, during gameplay, based on a trigger event associated with a change in a number of game players playing a particular player role. Player roles may, of course, differ based on the particular video game.
As a non-limiting example, a player role in a First-Person-Shooter game may comprise that of a sniper. During a gameplay session, if a number of players in the sniper role decreases to a number equal to or below a first (or lower) pre-determined threshold number, the map management engine may, as a result of the triggering event, add or provide ladders to (newly added or existing) sniper perches to the map or improve long-distance sight lines by removing occluding objects in order to incentivize players to switch to a sniper role to provide more balanced gameplay. In another example, the map may shrink or remove various map-based sniper advantages based on the inference that current players favor close-quarters gameplay.
By contrast, if a number of players in the sniper role increases during a gameplay session to a number equal to or above a second (or higher) pre-determined threshold number, the map management engine may, as a result of the triggering event, remove ladders and/or remove sniper perches and/or add occluding objects which reduce sight lines from the map in order to deter players from selecting the sniper role.
The types of static and/or dynamic map objects that may be added to or removed from (or be otherwise altered on) a map may differ based on the type and nature of various player roles in various video games.
In one implementation, a map may be dynamically modified in real-time, during gameplay, based on a trigger event associated with the pace or frequency of certain gameplay actions or events.
Referring once again to the example of a First-Person-Shooter game, excitement during gameplay may, for example, be based on the frequency of the occurrence of a particular event such as a firefight. As such, during a gameplay session, if the frequency of firefights decreases to a value equal to or below a first (or lower) pre-determined threshold value, the map management engine may, as a result of the triggering event, alter the area of playable space on the map by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s) to provide more opportunities for firefights and increase the pace of play.
By contrast, if the frequency of firefights increases during a gameplay session to a value equal to or above a second (or upper) pre-determined threshold value, the map management engine may, as a result of the triggering event, alter the area of playable space on the map by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s) to reduce the number of firefights and slow down the pace of play.
The various types of game actions or events that may be used as a triggering event may, of course, differ based on the particular video game.
In addition to the foregoing examples, a map may be dynamically modified in real-time, during gameplay, based on a trigger event associated with changes in other gameplay state information including, without limitation, types of matches (e.g., team death match, capture the flag, etc.), elapsed time or remaining time in a gameplay session, and/or other information related to a gameplay session.
These and other objects, features, and characteristics of the system and/or method disclosed herein, as well as the methods of operation and functions of the related objects 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.
The invention described herein relates to a system and method for providing dynamically variable maps in a video game.
Exemplary System Architecture
Computer System 110
Computer system 110 may be configured as a gaming console, a handheld gaming device, a personal computer (e.g., a desktop computer, a laptop computer, etc.), a smartphone, a tablet computing device, and/or other device that can be used to interact with an instance of a video game.
Referring to
Depending on the system configuration, map management application 120 (or portions thereof) may be part of a game application, which creates a game instance to facilitate gameplay. Alternatively or additionally, map management application 120 may run on a device such as a server 150.
Map management application 120 may include instructions that program computer system 110. The instructions may include, without limitation, a matchmaking engine 122, a map selection engine 124, a trigger detection engine 128, a map management engine 130, and/or other instructions 132 that program computer system 110 to perform various operations, each of which are described in greater detail herein. As used herein, for convenience, the various instructions will be described as performing an operation, when, in fact, the various instructions program the processors 112 (and therefore computer system 110) to perform the operation.
Peripherals 140
Peripherals 140 may be used to obtain an input (e.g., direct input, measured input, etc.) from a player. Peripherals 140 may include, without limitation, a game controller, a gamepad, a keyboard, a mouse, an imaging device such as a camera, a motion sensing device, a light sensor, a biometric sensor, and/or other peripheral device that can obtain an input from a player. Peripherals 140 may be coupled to a corresponding computer system 110 via a wired and/or wireless connection.
Server 150
Server 150 may include one or more computing devices.
Referring to
Depending on the system configuration, map management application 120 (or portions thereof) may be part of a game application, which creates a game instance to facilitate gameplay. Alternatively or additionally, portions or all of map management application 120 may run on computer system 110 or server 150.
Map management application 120 may include instructions that program server 150. The instructions may include, without limitation, a matchmaking engine 122, a map selection engine 124, a trigger detection engine 128, a map management engine 130, and/or other instructions 132 that program server 150 to perform various operations, each of which are described in greater detail herein. As used herein, for convenience, the various instructions will be described as performing an operation, when, in fact, the various instructions program the processors 152 (and therefore server 150) to perform the operation.
Although each is illustrated in
Furthermore, it should be appreciated that although the various instructions are illustrated in
The description of the functionality provided by the different instructions described herein is for illustrative purposes, and is not intended to be limiting, as any of instructions may provide more or less functionality than is described. For example, one or more of the instructions may be eliminated, and some or all of its functionality may be provided by other ones of the instructions. As another example, processor(s) (112, 152) may be programmed by one or more additional instructions that may perform some or all of the functionality attributed herein to one of the instructions.
Storage Devices 114
The various instructions described herein may be stored in one or more storage devices, such as storage device (114, 154), which may comprise random access memory (RAM), read only memory (ROM), and/or other memory. The storage device may store the computer program instructions (e.g., the aforementioned instructions) to be executed by processor (112, 152) as well as data that may be manipulated by processor (112, 152). The storage device may comprise floppy disks, hard disks, optical disks, tapes, or other storage media for storing computer-executable instructions and/or data.
Network 102
The various components illustrated in
In
Databases 160
The various databases 160 described herein may be, include, or interface to, for example, an Oracle™ relational database sold commercially by Oracle Corporation. Other databases, such as Informix™, DB2 (Database 2) or other data storage, including file-based, or query formats, platforms, or resources such as OLAP (On Line Analytical Processing), SQL (Structured Query Language), a SAN (storage area network), Microsoft Access™ or others may also be used, incorporated, or accessed. The database may comprise one or more such databases that reside in one or more physical devices and in one or more physical locations. The database may store a plurality of types of data and/or files and associated data or file descriptions, administrative information, or any other data.
The foregoing system architecture is exemplary only and should not be viewed as limiting. Other system configurations may be used as well, as would be appreciated by those having skill in the art.
As noted above, a multiplayer video game is a video game in which two or more players play in a gameplay session in a cooperative or adversarial relationship. Multiplayer video games have exploded in popularity due, in part, to services such as Microsoft's Xbox LIVE® and Sony's PlayStation Network® which enable garners all over the world to play with or against one another. Typically, when a player logs in to a game system or platform to play a multiplayer video game, the player may engage in a gameplay session in which he or she is matched with other players to play together (on the same team or as opponents).
In some instances, a given server 150 may be associated with a proprietary gameplay network system, such as, without limitation, Microsoft's Xbox LIVE® and Sony's PlayStation Network®, and/or another type of gameplay network system. In this implementation, a given computer system 110 may be associated with a particular type of gaming console. Other types of computer systems 110 using other types of gameplay networks may be used as well.
Referring to
While aspects of the invention may be described with reference to multiplayer video games, it should be recognized that the features and functionality described herein are equally applicable to a single player video game.
Generating Matches
According to an aspect of the invention, matchmaking engine 122 may identify one or more players that are waiting to be matched, such as players whose in-game avatars are waiting in a virtual game lobby to join a gameplay session. The gameplay session may comprise any type of gameplay session including, without limitation, a real gameplay session and/or a practice gameplay session (e.g., associated with a “practice” or “training” mode of a game).
In one implementation, a player may be added to a gameplay session immediately if there is an opening. In another implementation, one or more gameplay sessions may be dynamically combined to create a single gameplay session involving the aggregate of all players in each of the original gameplay sessions. A gameplay session may be dynamically split to create two or more gameplay sessions, where a matchmaking engine may determine which players from the original sessions are grouped and placed into the resulting two or more gameplay sessions.
In one implementation, matchmaking engine 122 may generate one or more matches by grouping two or more of the identified players. The number of players placed in each match may depend on a number of players waiting to be matched, a number of players needed for a game session (e.g., a number of players needed to form a team or start a match), a number of players that can be accommodated by a game session, and/or other information. Different matches may include different combinations of different players, which may include different numbers of players.
Matchmaking engine 122 may use known or hereafter-developed matchmaking techniques to generate a match (e.g., interchangeably referred to herein as “matchmaking”) by grouping players in an effort to produce the most satisfying player experiences. Game profiles, player profiles, match variables, and other factors may be considered when generating matches.
Exemplary Map
According to one implementation of the invention, map selection engine 124 may select, generate, or otherwise obtain a map for a match of a gameplay session.
Map boundary 304 may define (in whole or in part) an area of playable space 302 available to one or more game players during a gameplay session. As described in greater detail below, map boundary 304 may be scalable (e.g., may expand or contract) or be otherwise altered during a gameplay session to change the area of playable space 302.
Examples of static map objects 306 may include, without limitation, objects that are typically stationary such as a building, a wall, furniture, a tree, a large boulder, a body of water, a mountain, etc. The type of static map objects 306 presented on map 300 may of course differ depending on the type of video game.
Dynamic map objects 308 are objects that may be movable from one position to another, or from one state to another. For instance, a vehicle (e.g., a race car, truck, spaceship, etc.) may comprise a dynamic map object 308. A door or drawbridge that is capable of being moved from an open position (or state) to a closed position (or state), or a river whose water level changes to make it passable or impassable, etc. may also comprise a dynamic map object 308. The type of dynamic map objects 308 presented on map 300 may differ depending on the type of video game. In some instances, a dynamic map object may be moved or manipulated to change the area of (or otherwise alter aspects of) playable space 302 (as described in greater detail below).
In certain implementations, some static map objects 306 may be considered dynamic map objects if they are capable of being (or are) moved or manipulated during gameplay. For example, a large boulder may comprise a static map object 306. However, the large boulder may also be considered a dynamic map object 308 if it is capable of being (or is) moved or manipulated by one or more characters or equipment during a gameplay session.
According to an aspect of the invention, one or more of boundary 304, static map object(s) 306, and/or dynamic map object(s) 308 may collectively comprise a configuration of playable space 302 available to players during a gameplay session. The configuration of available playable space 302 may therefore be altered during a gameplay session by changes to boundary 304, and/or the location, position, size, number, state, etc. of one or more of static map object(s) 306, and/or dynamic map object(s) 308.
As one non-limiting example, map 300 may comprise one or more regions 310 (e.g., region A, region B, region C, etc.). Map 300 may comprise a floor plan of a building, regions A-C may comprise separate rooms, dynamic map objects 308 may comprise doors, and static map objects 306 may comprise pieces of furniture. The total area of playable space 302 may comprise rooms A, B, and C if all of doors 308 are open, or are unlocked and capable of being opened. By contrast, doors 308 may be locked between rooms A and B, or rooms B and C. Accordingly, floor plan 300 may be dynamically configured or modified such that total area of playable space 302 comprises room A, room B, room C, rooms A and B, rooms B and C, or rooms A, B, and C. As yet another example, one or more pieces of furniture (or static map objects) 306 may be moved into a position to block an open door 308 such that the same effect is achieved as if door 308 were closed or locked.
As the foregoing clearly demonstrates, various configurations of playable space 302 may be achieved by dynamically modifying a single map 300.
In one implementation, as described in greater detail below, the configuration of the playable space 302 may be altered during a gameplay session by changes to boundary 304, and/or the location, position, size, number, state, etc. of one or more of static map object(s) 306, and/or dynamic map object(s) 308 based on trigger events that occur during gameplay.
Map Selection or Generation—Initial Configuration
As noted above, map selection engine 124 may select, generate, or otherwise obtain a map for a match of a gameplay session. For example, in some implementations, map selection engine 124 may select and retrieve one or more maps from among a collection of pre-generated maps stored, for instance, in database 160. Alternatively, map selection engine 124 may generate one or more maps, or dynamically modify one or more existing maps, in real-time (“on the fly”) for a gameplay session to change the playable space by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s), as described above.
In some implementations, a map (whether selected, generated, or modified) may have an initial (or first or beginning) configuration based on gameplay session information. Gameplay session information may describe various game characteristics of a gameplay session that may influence the quality of gameplay. For example, gameplay session information may include, without limitation, a number of players, a composition of teams (e.g., number and/or types of roles in each team), duration of gameplay (e.g., how long a given gameplay session is expected to last), types of matches (e.g., team death match, capture the flag, etc.), and/or other information related to a gameplay session. In another implementation, a map may be selected for a match randomly.
In other implementations, one or more players may select the map to be played in a match of the gameplay session. For instance, before the start of a match, one or more players may vote on the map to be used during the gameplay session.
Trigger Events & Trigger Event Detection During Gameplay
According to an aspect of the invention, once a gameplay session has commenced, gameplay may be monitored in real-time for the detection of a trigger event (e.g., by trigger detection engine 128, or other game logic) that may cause the map to be dynamically modified (from its initial configuration) in order to improve the gameplay experience.
Examples of trigger events may include, but are not limited to, a change in a number of players in the gameplay session (e.g., the number of players exceeds or falls below a predetermined threshold), a change in a number of game players playing a particular player role (e.g., a number of a certain type of player roles in a match exceeds or falls below a predetermined threshold), the pace or frequency of gameplay actions/events exceeding or falling below a predetermined threshold, the commencement of a competition or newly available mission that takes place in a map, an inference that one or more players are unhappy with the current configuration of a map or otherwise would prefer variety (e.g., by monitoring unexpected attrition/rage quitting, or through explicit in-game voting or other feedback), or a change in other gameplay information, among other examples.
As a non-limiting example, matchmaking engine 122 may match one or more players into a map being used in a current gameplay session. The addition of the one or more players may comprise the trigger event that results in the dynamic modification of the map.
According to an aspect of the invention, trigger events may be system-defined (e.g., defined by the game logic) or user-defined (e.g., through one or more user interfaces prior to the commencement of a gameplay session). It should be appreciated that trigger events may be different for different maps, different video games, and/or for different maps utilized in the same video game. In some implementations, a collection of defined trigger events may be accessed and selectively applied to individual maps. In other implementations, trigger events may be created or customized for particular maps. Various configurations may be implemented.
According to an aspect of the invention, when a trigger event is detected during gameplay (e.g., by trigger detection engine 128, or other game logic), a map may be dynamically modified (from its initial configuration) as described in detail below. In some implementations, depending on the type of trigger event, detection of the trigger event alone may be sufficient to dynamically modify the map. In other implementations, the gameplay event or action that produced (or resulted in) the triggering event must persist for a predetermined period of time (e.g., a modification waiting period) before the map is dynamically modified. This avoids changing the map frequently when near trigger thresholds, since players may find this confusing or disruptive depending on the game or map design.
In some instances, two or more trigger events may occur during gameplay (and be detected) at substantially the same time. For example, both a number of players and a number of player roles of a certain type may exceed a predetermined threshold at substantially the same time. In such an instance, either or both of the detected trigger events may result in a dynamic modification of the map. For example, in one implementation, the most significant trigger event, as defined by game logic or a user, may be used to dynamically modify a configuration of the map. In some implementations, the occurrence of multiple trigger events may reduce the waiting period to dynamically modify the map. For example, if one or more additional trigger events occur during the modification waiting period, the modification waiting period may be truncated. In other implementations, if two or more significant trigger events are detected within a predetermined (e.g., short) period of time, the dynamic map modification may occur immediately without a modification waiting period. Other configurations may be implemented.
Dynamic Map Modification
According to an aspect of the invention, when trigger detection engine 128 detects a trigger event, map management engine 130 may dynamically modify a configuration of the map to improve the gameplay experience based on the type of trigger event.
Dynamic modification of a map may comprise any one or more of the following:
As a result of the dynamic modification of the map, the map may transform from its initial (or first or beginning) configuration to a modified (or new or second) configuration. Further, each detected trigger event that occurs during a gameplay session may cause map management engine 130 to dynamically modify a most recent (e.g, second) configuration of the map to a further modified (or new or third) configuration.
The following are illustrative and non-limiting examples of the various ways in which a map may be dynamically modified in real-time during gameplay in response to certain trigger events.
Number of Players
In one implementation, a map be dynamically modified in real-time, during gameplay, based on a trigger event associated with a change in a number of players in the gameplay session (e.g., the number of players exceeds or falls below a predetermined threshold).
As one example, if a number of players during a gameplay session falls below a predetermined number (e.g., a lower or first threshold), map management engine 130 may switch the state of one or more dynamic map objects (e.g., close a doorway, block a hallway, remove a bridge, etc.) of the map to selectively close off regions of the map, thereby decreasing the available playable space of the map. In this regard, the remaining players may be forced to play in a smaller area which may, depending on the nature of the game, increase encounters with other players to foster more exciting action and gameplay. In some implementations, when a region of a map is selectively closed off (or otherwise dynamically altered), player avatars may be transported out of the non-playable area to another area of the map (e.g., to a standard safe spawn site). Alternatively, player avatars may be spawned elsewhere after a death (or other game event), and the region of the map to be closed may be closed once no more player avatars are in the region.
Conversely, if a number of players during a gameplay session exceeds a predetermined number (e.g., a higher or second threshold number), map management engine 130 may switch the state of one or more dynamic map objects (e.g., open a doorway, unblock a hallway, add/open a bridge, etc.) of the map to selectively open up additional regions of the map, thereby increasing the available playable space of the map.
An example is illustrated in
During gameplay, upon detection that the number of players in the gameplay session has decreased from 16 players to a number equal to or below a first (or lower) pre-determined threshold number (e.g., 8 players), map management engine 130 may, as a result of the triggering event, switch dynamic map objects 408 to a closed state (or remove them altogether), thereby reducing the available playable space of the map to comprise only Region B as shown in map 400B of
By contrast, during gameplay, upon detection that the number of players in the gameplay session has increased from 16 players to a number equal to or above a second (or upper) pre-determined threshold number (e.g., 20 players), map management engine 130 may, as a result of the triggering event, switch dynamic map objects 408 to an open state (and/or add new dynamic map objects), thereby increasing the available playable space of the map to comprise Regions A, B, and C as shown in map 400C of
In this regard, the map may by dynamically modified in real-time during a gameplay session such that various configurations of the map (such as those illustrated in
In one implementation, the gameplay session (which players may join or leave in progress) may comprise an unbounded gameplay session such as that disclosed in co-pending, and concurrently filed, U.S. patent application Ser. No. ______, entitled “System and Method for Providing Continuous Gameplay in a Multiplayer Video Game Through an Unbounded Gameplay Session” (Attorney Docket No. 017594-0435434), which is hereby incorporated by reference herein in its entirety.
Types of Player Roles
In one implementation, a map may be dynamically modified in real-time, during gameplay, based on a trigger event associated with a change in a number of game players playing a particular player role. Player roles may, of course, differ based on the particular video game.
As a non-limiting example, a player role in a First-Person-Shooter game may comprise that of a sniper. During a gameplay session, if a number of players in the sniper role decreases to a number equal to or below a first (or lower) pre-determined threshold number, map management engine 130 may, as a result of the triggering event, add or provide ladders to (newly added or existing) sniper perches to the map or improve long-distance sight lines by removing occluding objects in order to incentivize players switch to a sniper role to provide more balanced gameplay. In another example, the map may shrink or remove various map-based sniper advantages based on an inference that current players favor close-quarters gameplay.
By contrast, if a number of players in the sniper role increases during a gameplay session to a number equal to or above a second (or higher) pre-determined threshold number, map management engine 130 may, as a result of the triggering event, remove ladders and/or remove sniper perches and/or add occluding objects which reduce sight lines from the map in order to deter players from selecting the sniper role.
The types of static and/or dynamic map objects that may be added to or removed from (or be otherwise altered on) a map may differ based on the type and nature of various player roles in various video games.
Pace or Frequency of Gameplay Actions/Events
In one implementation, a map may be dynamically modified in real-time, during gameplay, based on a trigger event associated with the pace or frequency of certain gameplay actions or events.
Returning back to the non-limiting example of a First-Person-Shooter game, excitement during gameplay may, for example, be based on the frequency of the occurrence of a particular event such as a firefight. As such, during a gameplay session, if the frequency of firefights decreases to a value equal to or below a first (or lower) pre-determined threshold value, map management engine 130 may, as a result of the triggering event, alter the area of playable space on the map by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s) to provide more opportunities for firefights and increase the pace of play.
By contrast, if the frequency of firefights increases during a gameplay session to a value equal to or above a second (or upper) pre-determined threshold value, map management engine 130 may, as a result of the triggering event, alter the area of playable space on the map by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s) to reduce the number of firefights and slow down the pace of play.
The various types of game actions or events that may be used as a triggering event may, of course, differ based on the particular video game.
Gameplay State Information
In addition to the foregoing examples, a map may be dynamically modified in real-time, during gameplay, based on a trigger event associated with changes in other gameplay state information including, without limitation, types of matches (e.g., team death match, capture the flag, etc.), elapsed time or remaining time in a gameplay session, and/or other information related to a gameplay session. For example, in some implementations, if the elapsed time of a gameplay session reaches a predetermined threshold, a map may be dynamically modified in any one or more of the manners described herein for variety. Numerous configurations may be implemented.
Exemplary Flowchart
In an operation 502, one or more trigger events may be defined. Trigger events may be system-defined (e.g., defined by the game logic) or user-defined (e.g., through one or more user interfaces prior to the commencement of a gameplay session). It should be appreciated that trigger events may be different for different maps, different video games, and/or for different maps utilized in the same video game. Examples of trigger events may include, but are not limited to, a change in a number of players in the gameplay session (e.g., the number of players exceeds or falls below a predetermined threshold), a change in a number of game players playing a particular player role (e.g., a number of a certain type of player roles in a match exceeds or falls below a predetermined threshold), the pace or frequency of gameplay actions/events exceeding or falling below a predetermined threshold, the commencement of a competition or newly available mission that takes place in a map, an inference that one or more players are unhappy with the current configuration of a map or otherwise would prefer variety (e.g., by monitoring unexpected attrition/rage quitting, or through explicit in-game voting or other feedback), or a change in other gameplay information, among other examples.
In an operation 504, one or more players, such as players whose in-game avatars are waiting in a virtual game lobby to join a gameplay session, may be matched. In one implementation, a matching engine may use known or hereafter-developed matchmaking techniques to generate a match by grouping players in an effort to produce the most satisfying player experiences. Game profiles, player profiles, match variables, and other factors may be considered when generating matches.
In an operation 506, a map selection engine may select, generate, or otherwise obtain a map for a match of a gameplay session. In some implementations, one or more maps may be selected and retrieved from among a collection of pre-generated maps stored, for instance, in one or more databases. Alternatively, the map selection engine may generate one or more maps, or dynamically modify one or more existing maps, in real-time (“on the fly”) for a gameplay session to change the playable space by altering one or more of the map's boundary, static map object(s), and/or dynamic map object(s).
In some implementations, a map (whether selected, generated, or modified) may have an initial (or first or beginning) configuration based on gameplay session information. Gameplay session information may describe various game characteristics of a gameplay session that may influence the quality of gameplay. For example, gameplay session information may include, without limitation, a number of players, a composition of teams (e.g., number and/or types of roles in each team), duration of gameplay (e.g., how long a given gameplay session is expected to last), types of matches (e.g., team death match, capture the flag, etc.), and/or other information related to a gameplay session. In another implementation, a map may be selected for a match randomly.
In yet other implementations, one or more players may select the map to be played in a match of the gameplay session. For instance, before the start of a match, one or more players may vote on the map to be used during the gameplay session.
In an operation 508, a gameplay session may commence. The gameplay session may comprise any type of gameplay session including, without limitation, a real gameplay session and/or a practice gameplay session (e.g., associated with a “practice” or “training” mode of a game).
In an operation 510, gameplay may be monitored in real-time for the detection of a trigger event (e.g., by a trigger detection engine, or other game logic).
If no trigger event is detected in operation 510, a determination may be made as to whether the gameplay session should continue. If so, processing may resume at operation 508. If not, the gameplay session may terminate in an operation 516.
If a trigger event is detected in operation 510, the map (provided in operation 506) may be dynamically modified (from its initial configuration) in an operation 512.
In operation 512, a map management engine may dynamically modify a configuration of the map to improve the gameplay experience based on the type of trigger event. Dynamic modification of a map may comprise any one or more of: altering the boundary (or perimeter) of the map by, for example, increasing or decreasing the boundary such that the boundary respectively defines a larger or smaller area of playable space, and/or opening up or closing (or otherwise altering) one or more portions of the boundary; altering the location, position, size, number, state, etc. of one or more static map objects on the map; altering the location, position, size, number, state, etc. of one or more dynamic map objects on the map; scaling the entire map by increasing or decreasing the size of the map and its constituent objects (including any static map objects, dynamic map objects, virtual characters or avatars depicting players, etc.) to increase or decrease the area of available space, respectively; adding or removing non-player characters (NPC) or other artificial intelligence (AI) controlled avatars to the gameplay experience; combining all or a portion of the map with all or a portion of one or more additional maps; and/or modifying the attributes of existing map objects or terrain such that player interaction is fundamentally impacted.
As a result of the dynamic modification of the map, the map may transform from its initial (or first or beginning) configuration to a modified (or new or second) configuration. Gameplay may then continue in operation 508.
Other implementations, uses and advantages of the invention will be apparent to those skilled in the art from consideration of the specification and practice of the invention disclosed herein. The specification should be considered exemplary only, and the scope of the invention is accordingly intended to be limited only by the following claims.
