Guest-friendly game information management system and method

Abstract

It provides an integrated gameplay system. [Solution] The integrated gameplay system includes a gameplay platform, an amusement park, and a controller. The gameplay platform provides access to multiple games, and the amusement park includes attractions that include one or more attraction features. Furthermore, the controller detects the presence of guests on the gameplay platform and / or attractions, identifies the guests, determines guest data based on the guest identification, and, based on the guest data, determines modifications to the arrangement of multiple games on the display interface of the gameplay platform and / or modifications to one or more attraction features. The controller also transmits control signals indicating modifications to the gameplay platform and / or modifications to one or more attraction features.

Description

【Technical Field】 【0001】 [Cross - Reference to Related Applications] This application claims priority and the benefit thereof to U.S. Provisional Patent Application No. 63 / 084,893, entitled "Guest - Facing Game Information Management Systems and Methods", filed on September 29, 2020, the disclosure of which is hereby incorporated by reference in its entirety for all purposes. 【0002】 The present disclosure generally relates to the field of amusement parks. Specifically, embodiments of the present disclosure relate to technologies for customizing centralized game interfaces and amusement park experiences. 【Background Art】 【0003】 In some entertainment environments such as game platforms, the user interface of the game platform can uniformly display available games or archived games within the archive to each user. That is, the game platform can provide the same composition of games on the user interface when accessing the game platform. For example, the user interface can provide the same top - ranked games, popular games, and archived games to each user. Therefore, each user can identify a particular interesting game after browsing the entire database or list of available games or archived games on the user interface. 【0004】 In some cases, games and / or users can be associated with a theme park. For example, a user accessing a game platform may also be a user visiting a theme park. The theme park can provide interactions uniformly, such that the available interactions are the same for each individual in the theme park. For example, these interactions may include the same animations, special effects, and displays for each person visiting the theme park. [Overview of the project] 【0005】 The following summarizes several embodiments that fall within the same scope as the subject matter of the original claims. These embodiments are not intended to limit the scope of the disclosure, but rather to outline some of the disclosed embodiments. In practice, the disclosure may include a variety of forms that are similar to or different from the embodiments shown below. 【0006】 In one embodiment, the integrated game play system includes a game play platform, an amusement park, and a controller. The game play platform provides access to multiple games, and the amusement park includes attractions that include one or more attraction features. Furthermore, the controller detects the presence of guests on the game play platform and / or attractions, identifies the guests, and determines guest data based on the guest identification. In response to determining the guest data, the controller determines, based on the guest data, to modify the organization of the multiple games on the display interface of the game play platform and / or modify one or more attraction features. The controller also transmits control signals indicating modifications to the game play platform and / or modifications to one or more attraction features. 【0007】 In one embodiment, the method includes receiving an indication that a guest is online on the gameplay platform and identifying the guest in relation to user identification. The method also includes determining guest data corresponding to guest park activity in an amusement park related to the gameplay platform based on the user identification. The method also includes modifying gameplay content on the display interface of the gameplay platform based on the guest data. 【0008】 In one embodiment, the method includes receiving sensor data from one or more sensors indicating the presence of a guest in close proximity to one or more attraction features of an amusement park attraction. The method also includes identifying the guest in relation to user identification and determining guest data based on user identification. The method also includes receiving additional guest data from one or more third-party applications, updating the guest data based on the additional guest data from the third-party applications, and modifying the amusement park attraction based on the updated guest data. 【0009】 A better understanding of these and other features, aspects and advantages of this disclosure will be gained by reading the following detailed description while referring to the attached drawings, which indicate the same parts throughout. [Brief explanation of the drawing] 【0010】 [Figure 1] This is a schematic diagram of a gameplay hub according to an embodiment of the disclosure. [Figure 2] This is a schematic diagram of the account page of the guest-enabled interface of the gameplay hub shown in Figure 1, according to an embodiment of the disclosure. [Figure 3] This is a schematic diagram of the notification page of the guest-enabled interface of the gameplay hub shown in Figure 1, according to an embodiment of the disclosure. [Figure 4]This is a schematic diagram of a dialog box that enables the sharing of third-party application data with the gameplay hub shown in Figure 1, according to an embodiment of the present disclosure. [Figure 5] This is a block diagram of a guest-responsive interface and a gameplay hub system for modifying guest interaction in an amusement park, according to embodiments of the present disclosure. [Figure 6] This is a process flow diagram for modifying the guest-enabled interface of the gameplay hub according to an embodiment of the disclosure. [Figure 7] This is a schematic diagram of a gameplay hub having a modified guest-enabled interface according to an embodiment of the present disclosure. [Figure 8] This is a process flow diagram for modifying a guest-responsive interface in an amusement park according to an embodiment of the disclosure. [Figure 9] This is a schematic diagram of a modified amusement park with guest-responsive interaction according to an embodiment of the present disclosure. [Modes for carrying out the invention] 【0011】 The following describes one or more specific embodiments of this disclosure. For the sake of brevity, this specification may not describe all features of the embodiments. In developing any such embodiments, as can be seen in any engineering or design project, it should be understood that numerous implementation-specific decisions must be made to achieve the developer's specific objectives, such as compliance with system-related and business-related constraints, which may vary by implementation. Furthermore, while such development efforts can be complex and time-consuming, it should nevertheless be understood as routine design, fabrication, and manufacturing for an average engineer interested in this disclosure. 【0012】 When describing elements of various embodiments of this disclosure, the articles “a,” “an,” and “the” are intended to mean that there are one or more of these elements. The terms “comprising,” “including,” and “having” are intended to be comprehensive and mean that there may be further elements other than those listed. Furthermore, any reference in this disclosure to “one embodiment,” “a certain embodiment,” or “several embodiments” should not be interpreted as excluding the existence of further embodiments, including the features described. The use of the terms “approximately” or “near” should be understood as including something close to the target (e.g., design, value, quantity) within any preferred or assumed margin of error (e.g., within 0.1%, 1%, 5%, 10%, and 25%). 【0013】 As used herein, “Gameplay Hub” can mean a platform for accessing one or more game applications that may include any of the following types of entertainment applications: arcade games, word games, immersive experiences, role-playing games, quiz games, and social interacting games. For example, a mobile-based or web-based platform may enable access to a database of various online games. In addition to or instead of this, a Gameplay Hub may also enable access to third-party applications, as well as third-party data related to guests (e.g., social media data, work-related data, health-related data, etc.), amusement park data related to guests, and other entertainment-related data related to guests. In other words, a Gameplay Hub may have multiple data sources and provide access to these data sources. Furthermore, as used herein, “guest-facing” can mean something that provides a display for guests to observe, interacts with guests, or communicates with guests, such as through a display interface, animated figures, or attraction features. Furthermore, as used herein, “guest” or “user” can mean synonymously any person accessing a Gameplay Hub or an entertainment environment such as an amusement park. Furthermore, as used herein, “guest data” may include data related to the guest, such as data from one or more sources (e.g., a gameplay hub, amusement park, third-party application, etc.). Guest data is associated with a unique user identifier (ID) and can be identified using this user ID. For example, a guest-enabled display interface for a gameplay hub can enable interaction with the guest through selectable buttons, dialog boxes, and fill-in-the-blank text fields on the interface.As another example, guest-responsive amusement park features could include interactive rides, or animated park figures that interact with guests by asking them about the rides they rode that day. Data indicating interactions (for example, that a guest rode two specific rides) can be stored in a database as guest data associated with a specific user ID. 【0014】 As mentioned above, a gameplay hub (e.g., a game platform) may include an interface that uniformly displays available games, archived games, and top-ranked games, so that the game selection is uniform or nearly uniform for each guest or user. In other words, the gameplay hub displays games without considering guest-specific data, such as data indicating guest preferences. For example, a first guest might prefer playing horror-themed games, while a second guest might prefer racing-themed games. Also, the first guest might be older and play more frequently than the second guest. Therefore, both the first and second guests may spend considerable time searching lists or browsing multiple web pages to find games that interest them. 【0015】 Furthermore, both the first and second guests may visit an amusement park associated with a gameplay hub (e.g., owned by the same entity). The interactions these guests choose to have at the amusement park can differ. For example, the first guest might participate in the amusement park's annual Halloween event, while the second guest might visit the amusement park monthly and spend most of their time in a specific area of ​​the park (e.g., a car-themed zone). Similar to games uniformly organized on the gameplay hub's display interface, the amusement park can also contain uniform interactions for guests. That is, the features or interactions of the amusement park may be the same for each guest regardless of their preferences. Consequently, such interactions may not be perceived as personalized or tailored to the guest. 【0016】 Furthermore, since guests have access to both the gameplay hub and the amusement park, data within each entertainment environment can be correlated. For example, a first guest's participation in a Halloween event may indicate a preference for spooky or horror-themed entertainment. Thus, the gameplay hub can use this information to appropriately organize its games and / or themes. It is desirable to integrate data from the gameplay hub and the amusement park to understand guests and use this information to refine the game organization on the gameplay hub interface and / or interactions in the amusement park. By integrating data, the gameplay hub and the amusement park can avoid a series of lengthy surveys that may be used to obtain the same guest information in each entertainment environment. Also, since the gameplay hub and the amusement park can be correlated, it is desirable to provide a single platform (e.g., a portal) that allows users to view, edit, and / or supplement data on guest activity in the gameplay hub and the amusement park. 【0017】 While the examples provided herein specifically address certain aspects of gameplay hubs and amusement parks that facilitate modification (e.g., customization) of the organization of games and account information on the gameplay hub, and / or modification of interactions within the amusement park, the techniques of this disclosure may also be applicable to other conditions and / or contexts. Therefore, these examples should be understood as reflecting real-world examples of gameplay hubs and / or amusement parks to provide a context that aids in explanation, and should not be considered as limiting the further applicability of the techniques. For example, the disclosure should be understood as applicable to further situations where customization of objects displayed on an interface and / or customization of interactions can be used to facilitate training (e.g., instructions regarding amusement park operations, game management, or employee job duties). 【0018】 Based on the above, Figure 1 is a schematic diagram of the gameplay hub 10. The gameplay hub 10 may include one or more game portals and can be accessed through a guest-enabled display interface 11, such as a web page on a display or a mobile application. As described in detail herein, the display interface 11 (e.g., a guest-enabled display interface) may include visual and / or selectable components that enable a guest (e.g., a user) to interact with the gameplay hub 10. The display interface 11 may display organized game and guest information. The guest information may include a unique user identifier (ID) 12, a play score 18, and / or account-related information including an account tab 14 and a notification tab 16. 【0019】 User ID 12 (e.g., 10359) may include a unique combination of letters, numbers, and / or symbols that identify a guest profile associated with the guest. Guests can select User ID 12 as long as it is available (e.g., not currently being used by another guest), and / or the gameplay hub 10 can assign User ID 12. Accessing the gameplay hub 10 using User ID 12 instead of Personally Identifiable Information (PII) can protect the guest's identity. The gameplay hub 10 may store guest data (e.g., in one or more databases) and tag it with User ID 12 so that the gameplay hub 10 and / or the amusement park can retrieve guest data using the unique User ID 12. As an example, guest data may include tracked guest activity of User ID 12 within the gameplay hub 10 (e.g., tracked guest game activity), such as games played, game scores, and access frequency. In addition to or instead of this, as illustrated with reference to Figure 7, the amusement park associated with the gameplay hub 10 can also store guest data and tag the user ID 12. As another example, the amusement park can track the guest activities of the same user ID 12 within the amusement park, such as the duration of the amusement park visit, the rides accessed, and the zones accessed (e.g., tracking guest park activities). Furthermore, in some examples, the gameplay hub 10 can also retrieve data from third-party applications associated with the guest, tag the user ID 12, and then store it as guest data. 【0020】 The gameplay hub 10 and / or the amusement park can use the user ID 12 to retrieve guest data and use that guest data to modify interactions to be specific to the guest. In this way, the gameplay hub 10 can curate guest-related information from activities both on the gameplay hub 10 and in the amusement park, as well as from third-party applications. 【0021】 A play score 18 (e.g., 5,000 points) can include a metric that measures a guest's play performance for one or more games. In the following description, a play score measured in points will be described, but the systems and methods described herein can also include play scores measured in units such as coins, tokens, and skill levels (e.g., beginner, intermediate, advanced). Also, in the following description, a single play score 18 will be described, but the systems and methods described herein can also include one or more play scores 18 that correlate to one or more games. In some embodiments, a guest can earn points based on, but not limited to, exceeding a level within a particular game, unlocking features within a particular game, and / or playing on the game play hub 10 for a certain number of days within a particular period (e.g., one week, one month, and one year). In some embodiments, the play score 18 can include the score of a game that was actively played and / or the total play score 18 of all games played within a time frame (e.g., after the user activated an account on the game play hub 10). Additionally, the play score 18 can be publicly displayed to some guests (e.g., each guest currently playing the same game as the guest) or to each guest of the game play hub 10 for competition within the game play hub 10. In addition to or instead of earning points based on activities within the game play hub 10, a guest can also earn points based on activities at the amusement park. As an example, a guest can earn points by visiting a particular ride associated with a recently played game. A guest can also exchange these points for items, gift cards, and tickets, etc. within the amusement park and / or the game play hub 10. 【0022】 The account tab 14 and the notification tab 16 can be selectable tabs that open a new window on the display interface 11 when selected (e.g., by clicking using a computer mouse or tapping on a touch screen), causing the game play hub 10 to open. In the following description, two account-related information tabs will be described, but the systems and methods described herein can also include one or more (e.g., three, four, and five, etc.) account-related information tabs corresponding to subcategories of account-related information. In some embodiments, the account tab 14 and the notification tab 16, and / or the data related to the account tab 14 and the notification tab 16 can be integrated into a single tab. In addition or alternatively, the display interface 11 can also display guest-related information on the main display interface 11 together with the compiled game (e.g., without tabs). Briefly, as described in detail with respect to FIG. 2, the account tab 14 can include, but is not limited to, account-related information such as a user ID 12, a related email address, a guest name, or a screen name (e.g., different from the user ID 12 used to access the account on the game play hub 10), a history of games played (e.g., after a guest creates an account and / or within a specific period such as six months, one year, and five years, etc.), and / or a history of play scores related to the game. 【0023】 In short, as will be explained in detail with respect to Figure 3, the notification tab 16 may include notifications that show a history of guest activity or information related to guest activity. For example, these notifications may include a history of play scores 18 (e.g., current and same-year play scores 18) and / or a history of related guest activity at the amusement park (e.g., event tickets purchased at the same time last year). In some embodiments, notifications may include further questions or requests based on history. That is, the gameplay hub 10 may ask questions tailored to the game history and / or amusement park activity specific to user ID 16, rather than requesting general information. For example, the notification tab 16 may request information related to fears based on a notification indicating that a guest associated with a unique user ID 16 has purchased tickets for the next Halloween event at the amusement park. The notification tab 16 may request the same information based on a notification indicating that the guest has recently played a horror-themed game. 【0024】 As will be explained in detail with respect to Figure 4, the Gameplay Hub 10 can communicate with a Third-Party Application Programming Interface (API) that enables the Gameplay Hub 10 to communicate with third-party applications. Specifically, this API can function as an intermediary that sends requests from the Gameplay Hub 10 to a third-party application (e.g., a third-party system), receives information from the third-party application, and sends the information back to the Gameplay Hub 10. In this way, the Gameplay Hub 10 can access third-party information that would not otherwise be available through the Gameplay Hub 10. Guests can enable or disable the Gameplay Hub 10 from accessing such data, for example, through the account tab 14 or the device settings (e.g., used to access the Gameplay Hub 10). As an example, the Gameplay Hub 10 on a mobile application can access third-party applications on the mobile device, such as social media applications, medical applications, and banking applications, if the guest grants access. The Gameplay Hub 10 can use such information to learn about the guest. Third-party data may indicate preferences, including, but is not limited to, favorite animals, favorite amusement park characters, favorite names, medical conditions, disabilities, and / or information related to the guest's family. Based on this data, the Gameplay Hub 10 can recommend games and / or rides, and automatically populate answers or recommended answers to questions asked in the Notifications tab 16. In this way, the Gameplay Hub 10 can determine preferences using the Accounts tab 14, Notifications tab 16, third-party applications, tracked guest game activity, and / or tracked guest park activity.As described herein, the gameplay hub 10 can use accumulated data from various sources, integrate the data to determine guest preferences and information, and use this guest data to customize the display interface 11 for a particular guest and / or customize the interaction in the amusement park. 【0025】 In the illustrated embodiment, the display interface 11 displays multiple games organized by commonality or topic. In the illustrated embodiment, the display interface 11 displays a default organization, which can be modified based on guest data, as will be described in detail with respect to Figure 7. In the following description, game topics including recommended games, popular games, and archived games represent a particular embodiment, but the systems and methods described herein may also include other game topics (e.g., best games by category or theme, suggestions by age group or gender, etc.). Here, games are organized by topics: recommended games 20, popular games 22, and archived games 24. Recommended games 20 may include a recommended game set 26 in the organized game list, which includes a first game (e.g., game 1), a second game (e.g., game 2), and a third game (e.g., game 3). In some embodiments, the recommended games 20 may include the most frequently played games within a specific period (e.g., on a specific day), the popular games 22 may include the most frequently played game set 28 to date, and the archived games 24 may include game sets 30 that have been played previously but for which no game data exists (e.g., the game icon remains in the library after the game data has been deleted). 【0026】 The display interface 11 can display a specific number of games (such as one, three (illustrated), and five) within each topic. Guests can continue browsing to find the next most relevant games within a topic (e.g., the fourth and fifth games) (as indicated by the ellipsis). Furthermore, the position of the games, such as from left to right, can indicate relevance. For example, the first game in the leftmost position of the recommended game set 26 may include the most recommended game, and the third game may include the third most recommended game among the recommended games 20. The gameplay hub 10 can similarly organize popular games 22 and archived games 24. 【0027】 Figure 2 is a schematic diagram of the account tab 14 on the display interface 11. As described above, the account tab 14 contains general information and / or preferences related to the guest corresponding to the user ID 12. The general information about user ID 12 can be organized separately for the user profile 52 and game history 68. As described above, the display interface 11 is guest-responsive and interactive. Therefore, the guest can enter information in the editable fields 53 below the profile 52 and game history 68. In the illustrated embodiment, the profile 52 includes the guest name 54, age 56, favorite color 58, favorite amusement park visit time 60, favorite game 62, interest in annual events 64, email address 66, and other information or preferences 67 that the guest may choose to share with the gameplay hub 10. 【0028】 The game history 68 may include games played by the guest after creating an account in the gameplay hub 10. In the illustrated embodiment, the game history 68 shows the history of a first game 70 (game 1) and a second game 78 (game 5). Specifically, for the first game 70, the game history includes the last played date 72 of the first game (e.g., December 1, 2019), the first game score 74 (e.g., 2500), and other days 76 on which the first game was played (e.g., January 5, 2019 and April 10, 2019). For the second game 78, the game history includes the last played date 80 of the second game (e.g., November 10, 2019), the second game score 82 (e.g., 5000), and other days 84 on which the second game was played (e.g., March 8, 2019 and February 11, 2019). 【0029】 The account tab 14 may include further general information and / or preferences related to the user ID 12 (indicated by an ellipsis). For example, the further general information can be automatically generated based on additional information learned about the guest, such as information provided by the guest through the notification tab 16. Since the display interface 11 is guest-responsive and interactive, field 53 is editable and can be manually modified by the guest. In some embodiments, the gameplay hub 10 can automatically fill in field 53 (e.g., using machine learning), and the guest can change the text as needed. As an example, the gameplay hub 10 can automatically fill in preferred amusement park visit times 60 based on the guest's frequency of visiting the amusement park during a particular season or month. However, the guest may also prefer to visit at different times and can therefore manually enter the correct information. The gameplay hub 10 can request additional information related to the guest to accurately determine the guest's preferences, which can then be used to modify the display interface 11. 【0030】 Figure 3 shows a block diagram of the notification tab 16 on the display interface 11 for illustrative purposes. As described above, these notifications may be based on guest data from the gameplay hub (e.g., tracked guest game activity), information from the account tab 14, guest data from the amusement park (e.g., tracked guest park activity), and / or data from third-party applications. Here, the notification includes a first notification 102 (Participated in Clown World 10 times in 2019) indicating that the guest participated in Clown World in 2019. The notification also includes a second notification 104 (Purchased tickets for the next Halloween event) indicating that the guest purchased tickets for the next Halloween event at the amusement park. The notification also includes a third notification 106 (Play Score (2019) - 7,000) indicating that the cumulative play score for 2019 is 7,000. The notification also includes a fourth notification, Notice 108 (New Halloween Event Game Arriving in October 2020), indicating that new games that guests may be interested in are arriving in October 2020. 【0031】 In some embodiments, a notice may include sub-information 110, which includes sub-notifications and / or questions relating to the notice. In the illustrated embodiment, a second notice 104 indicating that a guest has purchased Halloween event tickets includes the purchase date, October 5, 2019; the event date, October 30, 2019; the total number of tickets purchased, four; and sub-information 110 indicating the guest's history of past Halloween events attended (e.g., attended Halloween events on October 1, 2018, October 10, 2017, and October 8, 2013). 【0032】 The gameplay hub 10 may request additional information from the guest regarding a second notice 104 and / or related to the sub-information 110, based on the information related to this sub-information 110. Since the second notice 104 is generally related to a ticket for a Halloween event, the gameplay hub 10 may request additional information about the Halloween event, such as what scares the guest (e.g., what they find scary), and additional information about the ticket, such as the expected time of attendance on the event day (e.g., what time they plan to attend). The display interface 11 may include a field 53 for interacting with the guest and receiving input about these questions. In a further embodiment, the gameplay hub 10 may respond to guest input and request additional information based on that input. That is, the display interface 11 may be dynamic, and the gameplay hub 10 may provide questions that narrow the scope of what the guest answers based on their answers to previous questions. Similarly, the third notice 106 may include sub-information 112, and the gameplay hub 10 may request additional information from the guest regarding the third notice 106 and / or related to the sub-information 112. 【0033】 In this way, the gameplay hub 10 can learn detailed information about the guest and easily modify the organization of gameplay content on the display interface 11 and / or interactions in the amusement park to be specific to that guest. Rather than asking a variety of pre-questions (e.g., are you planning to attend any events at the amusement park this year?), the gameplay hub 10 determines guest preferences and / or additional information about the guest by asking narrowed-scope questions using data obtained from various sources (e.g., game history played on the gameplay hub 10, account tab 14, data from the amusement park, and third-party systems). Therefore, there may be a set of questions that can be automatically executed using contextual information in order to efficiently determine narrowed-scope questions. The notification tab 16 may also include further general information and / or preferences related to the user ID 12 (as indicated by the ellipsis). 【0034】Figure 4 is a schematic diagram of a dialog box 124 on the display interface 121 of a guest mobile device 120 that enables data sharing from a third-party application. The guest can access the gameplay hub 10 through a mobile application on the guest mobile device 120. The display interface 121 can display one or more mobile applications 122, including the gameplay hub mobile application 123. As shown in the figure, when the gameplay hub mobile application 123 is selected 125, a dialog box 124 appears on the home screen of the guest mobile device 120. The dialog box 124 can prompt the user to allow or deny access for the gameplay hub 10 to communicate with third-party applications on the guest mobile device 120 (e.g., social media applications, medical applications, banking applications, etc.) via third-party APIs (e.g., via the gameplay hub mobile application 123). In further embodiments, the guest can allow or deny the Gameplay Hub 10 access to third-party applications on the guest mobile device 120 through settings on the guest mobile device 120, within the Gameplay Hub 10, and / or on different screens of the display interface 121. In some embodiments, the guest can allow access to some third-party applications while denying access to others. In addition to or instead of this, the guest may also allow the Gameplay Hub 10 to access other information stored on or accessible from the guest mobile device 120 (e.g., stored in the memory of the guest mobile device 120 and / or in a cloud computing system), and the Global Positioning System (GPS). The guest can also set notification date and time preferences, such as the time frame for receiving notifications.Therefore, the gameplay hub 10 can access the same amount of available information that the guest has enabled access to through the gameplay hub 10. 【0035】 In some examples, the gameplay hub 10 may determine that guest data obtained from a third-party application is reliable (e.g., within a confidence threshold). For example, the gameplay hub 10 may communicate with a social media application via a third-party API to determine that a guest has a family of four, one of whom is a child. The gameplay hub 10 may not request additional information based on the reliability of the social media application and / or data from other sources that confirm the accuracy of the information from the social media application (e.g., sub-information 110 indicating that four tickets were purchased, presumably for the family of four). In further embodiments, the gameplay hub 10 may request further information about the guest from the social media application. For example, the gameplay hub 10 may ask the guest for the child's name and / or request permission for the amusement park to use the child's name for interactions within the amusement park. 【0036】 In some embodiments, guests can also control the scope of access granted to third-party applications and other information accessible on or via the guest mobile device 120. For example, guests can control settings on the guest mobile device 120 or provide (e.g., input) further preference-based information, such as a preference to stop tracking the guest when the guest enters a specific zone of the amusement park (e.g., denying access to GPS), a preference to request restrictions on interaction with animated characters in specific parts of the amusement park or at specific times, and a preference to indicate the clothing they plan to wear during their next amusement park visit (e.g., the color of their clothing). Thus, the gameplay hub 10 avoids requiring answers to pre-questions (e.g., how many people are in your household?) by accessing permitted data sources or received preference information. 【0037】 To illustrate the system controlling the gameplay hub 10 and / or the amusement park, Figure 5 shows a gameplay system 150 that modifies gameplay content on the gameplay hub 10 and / or interactions in the amusement park. As shown, the gameplay system 150 includes a park sensor 152, a controller 154, park features (e.g., attraction features) 156, the gameplay hub 10, a guest mobile device 120, and a third-party application 186. It should be understood that the illustrated system is for illustrative purposes only, and according to the disclosed embodiments, some features and components may be omitted and various other features and components may be added to facilitate performance. 【0038】 The controller 154 may include an input device 168, a processor 170, a memory 172, and a communication circuit 174. The input device 168 can receive input data from the park sensor 152, the gameplay hub 10, a third-party application 186, and a guest mobile device 120. In the following description, the gameplay hub 10, the third-party application 186, and the guest mobile device 120 are described as independent components of the gameplay system 150 that provide data to the input device 168, but these components can also be integrated with the gameplay hub 10 or (as indicated by the dashed line) communicate with the gameplay hub 10. Based on the input data received by the input device 168, the controller 154 can modify the gameplay content on the gameplay hub 10 and / or the park's interactions (e.g., features) as described above. 【0039】 In the amusement park environment, the controller 154 can control park features 156, including a display 178, a lighting effects system 180, animated figures 182, and / or a sound effects system 184. The amusement park may include attractions throughout the park, such as rides, virtual game rooms, picnic areas, and restaurants, which may include one or more of the park features 156. For example, a ride may include a lighting effects system 180, animated figures 182, and / or a sound effects system 184, and the amusement park pathways may include animated figures 182 and a display 178. Furthermore, the amusement park may be divided into multiple zones organized by theme and / or age group. For example, a zone organized by a particular theme may focus heavily on a specific subject related to that theme, or may revolve around such a subject. 【0040】 As will be explained in detail with respect to Figure 7, the controller 154 can control park features 156 to provide customized interactions tailored to the guest, for example. For example, the controller 154 can control the speakers of the sound effects system 184 on the ride to generate audio relevant to a particular guest. For example, this audio could include a recognizable, unique sound (e.g., a favorite song) and / or the guest's name. The modified (e.g., customized) audio can be based on guest data. As another example, the controller 154 can control the lighting effects system 180 to project specific animations during the ride (e.g., on the walls of the ride's tunnel) based on guest data. For example, the gameplay system 150 can obtain guest data indicating the guest's fears from the gameplay hub 10 and use this data to modify the animations projected by the lighting effects system 180 (e.g., projecting a spider because the guest is afraid of spiders). In this way, the controller 154 can control and modify the amusement park interactions to provide a customized experience based on guest data. Specifically, the presence of a guest in or near the park feature 156 can trigger the controller 154 to modify the park feature 156 based on guest data. The gameplay system 150 can detect guests using one or more of the park sensors 152. 【0041】 The park sensor 152 may include one or more radio frequency identification (RFID) tags 158, one or more cameras 160, one or more weight sensors 162, one or more electronic readers 164, and / or one or more proximity sensors 166. The park sensor 152 may be placed or positioned in an area where the presence of guests is expected, such as on a ride cart or on the ride track of a ride. The RFID tags 158 can communicate with the electronic readers 164 to indicate the presence of guests. Specifically, the RFID tags 158 can be incorporated into a ride, such as on the ride track of a ride or on a ride cart (e.g., inside, on the side, or at the entrance of the ride cart). Thus, the electronic readers 164 can be positioned to scan the RFID tags 158. As an example, the electronic readers 164 may be placed on the ride track so that when a ride cart passes over the electronic readers 164, the RFID tags 158 on the ride cart can be scanned to indicate that a guest is on the ride. In some embodiments, the RFID tag may include a guest-worn RFID tag 158 associated with a specific user ID 12. Thus, input data from the electronic reader 164 can indicate the presence of a guest associated with user ID 12 when the guest-worn RFID tag 158 is scanned. The controller 154 can then retrieve guest data based on user ID 12 and modify the park features 156 accordingly. 【0042】 As described above, amusement parks can also track guest park activities, such as ride history and interactions. For example, tracked guest park activities (e.g., guest-worn RFID tags 158) can indicate that a guest stayed in a particular zone of the park for most of their visit. Tracked guest park activities can also indicate that a guest rode a particular ride more frequently than others. Based on this guest data, the gameplay system 150 can determine the guest's preferences (e.g., favorite zones and rides in the park) and use this to update gameplay content on the gameplay hub 10 and / or interactions in the park. For example, the gameplay system 150 can recommend games related to the guest's favorite zones and / or rides on the display interface 11 of the gameplay hub 10. 【0043】 In further embodiments, the camera 160 can be positioned or located within an area based on the expected presence of guests, such as in locations where a vehicle cart on a vehicle is visible. The camera 160 can determine the presence of guests based on the images or videos it captures. Specifically, the camera 160 can perform facial recognition and / or body recognition to determine the presence of guests. In some embodiments, the camera 160 can instead provide images and / or videos as input data to the controller 154, which can then perform facial recognition and / or body recognition. Furthermore, in some embodiments, the controller 154 can identify a specific guest based on the input data. That is, the controller 154 can match images and / or videos with images of the guest. The guest's images can be images stored in memory 172, images associated with user ID 12, and / or images obtainable through a third-party application 186 (e.g., a guest profile image on a social media application). 【0044】 In addition to or instead of the above, a weight sensor 162 may also indicate the presence of a guest. The weight sensor 162 is mounted on the vehicle track and can indicate the presence of a vehicle cart on the vehicle track based on a predetermined weight. Similarly, a proximity sensor 166 may be placed or positioned in close proximity to an area where the presence of a guest is expected. The proximity sensor 166 can detect the presence of a nearby object without physical contact by using an electromagnetic field, light and / or sound. The proximity sensor 166 can emit an electromagnetic field or electromagnetic radiation (e.g., infrared) beam to determine changes in the field or feedback signal. The proximity sensor 166 may be placed near the loading point of the vehicle cart and / or on the seat of the vehicle cart to accurately detect the presence of a nearby object as a guest. In general, the RFID tag 158 and / or camera 160 can be used alone or in conjunction with other park sensors 152 (e.g., weight sensor 162 and / or proximity sensor 166) to detect the presence of a guest and / or identify the guest. 【0045】 The gameplay hub 10 can also provide input data to the input device 168, including data from the account tab 14 (e.g., guest name 54) and / or data from the notification tab 16 (e.g., guest fear level). That is, as described with respect to Figures 2 to 4, the gameplay hub 10 can provide guest data such as tracked guest game activity in the gameplay hub 10, guest preferences based on data determined using various data sources, and / or answers to questions asked in response to notifications. 【0046】 In addition to or instead of this, a third-party application 186 may also provide input data to the input device 168. That is, the third-party application 186 may share data with the gameplay system 150 when guest permission is granted. The third-party application 186 may include systems related to third parties, including entities that do not have a direct relationship with the gameplay system 150. The third-party application 186 may provide third-party data from one or more third parties collected through third-party websites, mobile applications and / or other platforms. As stated above, the third-party application 186 may include, but is not limited to, social media applications, medical applications and / or banking applications. Therefore, the third-party data from the third-party application 186 may include data related to social media applications, medical applications and / or banking applications. 【0047】 The guest mobile device 120 can also provide input data to the input device 168. The guest mobile device 120 can share device data with the gameplay system 150 when permitted by the guest. The device data includes, but is not limited to, images and videos stored in or accessible by the guest mobile device 120, the GPS location of the guest mobile device 120, tracking data determined by the guest mobile device 120 (e.g., steps per day, average screen time, etc.), and / or setting preferences (e.g., large text, color theme, enabling specially accessible features, etc.). 【0048】 The gameplay system 150 includes a monitoring system 157 and a service desk 159. In the following description, the monitoring system and the service desk are described as independent components of the gameplay system 150, but these components may communicate with each other (for example, as indicated by dashed lines) or be integrated into a single system (for example, the service desk 159 being part of the monitoring system 157). The monitoring system 157 can be a management system that monitors the park sensor 152, park features 156, and the gameplay hub 10. For example, the monitoring system 157 may monitor control signals that modify the park features 156, transmitted from the controller 154 in response to the presence and identification of a guest. Specifically, the monitoring system 157 can ensure that the park sensor 152, park features 156, and the gameplay hub 10 function as expected and / or provide the modified features to a particular guest as expected. In some embodiments, the monitoring system 157 may also track ride wait times or queues to maintain expected throughput. 【0049】 Furthermore, the monitoring system 157 can also control or reconfigure the controller 154 if it is not functioning as expected (e.g., there are many errors in the control signals). In this way, the monitoring system 157 can reset or recalibrate the park sensor 152, park features 156 and gameplay hub 10, and / or override the display or organization of gameplay content and / or modified park features 156 for a particular guest (as initially determined by the controller 154). The monitoring system 157 can reset the modified gameplay content and / or modified interaction algorithms of the controller 154. In some embodiments, the monitoring system 157 and the controller 154 can be implemented as a single controller. 【0050】 In some embodiments, if a service desk 159, which may include human or virtual service agents, discovers any issue with the modified gameplay content, gameplay hub 10, modified interactions, and / or park features 156 other than those determined by the controller 154, it may manually stop the modified gameplay content and / or modified interactions via a stop mechanism (e.g., a button) to override the control signals of the controller 154. As described above, guests can be tracked (e.g., via guest-worn RFID tags 158), so the service desk 159 can monitor guest activity and use this to address unexpected delays or unexpected features in the amusement park. For example, tracked activity may indicate an unexpected delay or queue, and / or unexpected behavior by a roller coaster, by showing that a guest attempted to ride a particular roller coaster but remained stationary or nearly stationary in the roller coaster zone for a certain period exceeding a threshold period. In some embodiments, unexpected activity may alert the service desk 159 to resolve the issue. 【0051】 The controller 154 can enable the communication circuit 174 to interact with various electronic devices such as the monitoring system 157, the service desk 159, the gameplay hub 10, and / or the park feature 156. The monitoring system 157 and / or the service desk 159 can communicate with the controller 154 to receive and / or transmit information (as indicated by the double arrows) to ensure that the gameplay hub 10 and / or the park feature 156 are operating as expected. In addition to or instead of this, the controller 154 can also enable the communication circuit 174 to interact with components of the park feature 156. For example, the communication circuit 174 can enable the controller 154 to communicately connect to networks such as a personal area network (PAN), a local area network (LAN), and / or a wide area network (WAN). Accordingly, in some embodiments, the controller 154 can process data from the input device 168, determine the presence of a specific guest and identify that guest, determine guest data associated with the guest from each user ID 12, determine modifications to the gameplay content, determine modifications to the interactions in the amusement park to facilitate a customized experience for the guest, and communicate the modifications to the gameplay hub 10 and / or park features 156 via the communication circuit 174. For example, after processing sensor data from the input device 168, the processor 170 can determine a control signal that enables the communication circuit 174 to wirelessly transmit control data to the gameplay hub 10 and / or park features 156 to activate the modifications. In other embodiments, the communication circuit 174 can be connected to the gameplay hub 10 and / or park features 156 via a wired connection. 【0052】 The processor 170 may include one or more processing units that receive input signals from an input device 168 related to the presence and / or identification of a guest, and use these input signals to determine modified gameplay content and / or modified interactions of park features 156 of the gameplay hub 10 using the techniques described herein. The memory 172 may include one or more tangible non-temporary machine-readable media. For example, such machine-readable media may include RAM, ROM, EPROM, EEPROM, or optical disk storage, magnetic disk storage or other magnetic storage devices, or any other media that can be used to hold or store a desired algorithm (e.g., program code) in the form of machine-executable instructions or data structures and that can be accessed by the processor 170 or other processor-based devices. Specifically, the processor 170 may include a processing core that executes machine-executable instruction algorithms stored in the memory 172. The processor 170 may also include a processor-side interface for software applications running on the processing core to interact with hardware components on the vehicle associated with the processor 170, such as a display 178, a lighting effects system 180, an animated figure 182, and / or a sound effects system 184. Memory 172 can store guest data corresponding to tracked guest game and amusement park activities, as well as corresponding guest preferences (determined, for example, by manual input from the guest and / or by processing an algorithm). Memory 172 can store the guest data after tagging it with a user ID 12 so that it can be retrieved later. That is, the gameplay system 150 can retrieve data related to a guest by looking up the ID 12 and using the associated guest data. 【0053】 As an example in an amusement park environment, the stored algorithms may include, but are not limited to, an algorithm for determining the presence of a guest based on sensor data from park sensor 152; an algorithm for identifying a specific guest (e.g., by processing sensor data from camera 160 to perform face recognition and / or by processing sensor data from RFID tag 158 associated with user ID 12); an algorithm for obtaining guest data for user ID 12; an algorithm for determining modifications to interactions within the park based on guest data; and an algorithm for providing modified images, sounds, lighting effects, or animations (e.g., stored in memory 172) based on guest data (e.g., indicating preferences or guest information). In this way, the controller 154 can determine the presence of a specific guest and control the park feature 156 accordingly, for example, when a specific guest is within a predetermined range of the park feature 156 and / or when it is determined that the guest is facing the park feature 156. Modifications to interactions may include modifications to interactions on rides, but may also include interactions on the ground in the amusement park. 【0054】 In the Gameplay Hub 10 environment, the stored algorithms may include, but are not limited to, an algorithm for authenticating login information (e.g., a combination of username and password), an algorithm for allowing a guest to log in to Gameplay Hub 10, an algorithm for determining a user ID 12 associated with the login information, an algorithm for retrieving guest data for user ID 12, an algorithm for determining that a guest logged in from a mobile application or web browser, an algorithm for requesting guest data from a third-party application 186, an algorithm for requesting guest data from a mobile device 120, an algorithm for providing notifications on the notification tab 16, an algorithm for requesting additional information or confirmation of information regarding the account tab 14 and / or the notification tab 16, an algorithm for determining modifications to gameplay content based on guest data, and an algorithm for providing modifications to gameplay content. At least some of these modifications may include game organization, game order within a category or topic, and notifications and questions within the notification tab 16. 【0055】 To illustrate the process of providing modified gameplay content, Figure 6 shows a flowchart of the process 200 for customizing gameplay content on the guest-enabled display interface 11 of the gameplay hub 10. While the process 200 is described using a specific sequence of actions, it should be understood that the actions described may be performed in a different order than shown, and some actions may be skipped or not performed at all. Generally, at least some of the steps of the process 200 can be performed at least partially by the gameplay system 150 of Figure 5. Specifically, these steps can be performed at least partially by the processor 170 of the gameplay system 150, which executes instructions stored in a tangible, non-temporary computer-readable medium such as memory 172. In another or further embodiment, at least some of the steps of the process 200 may also be performed by any other preferred component or control logic, etc. 【0056】 Processor 170 can identify guests (process block 202) in order to customize gameplay content to suit a particular guest. Specifically, processor 170 can identify guests based on a user ID 12 associated with the guest account. Processor 170 can determine the user ID 12 when a guest logs into the gameplay hub 10 and accesses their guest account. For example, a guest can log into the gameplay hub 10 as described above using a username and password. In some cases, the username and user ID 12 may be the same. In other cases, the user ID 12 may not be the same as the username, but may be related to the username. 【0057】 Accordingly, after a guest logs into the gameplay hub 10, the processor 170 can determine guest data based on the user ID 12 associated with the login credentials (process block 204). The guest data may include guest-related information (e.g., searchable via the user ID 12) that indicates preferences and guest information. The guest data may include tracked guest game activity within the gameplay hub 10 (e.g., frequently played games, themes of games played, etc.) and / or tracked guest park activity in the amusement park (e.g., most frequently visited amusement park zones, most frequently ridden rides, most frequently visited attractions, etc.). In some embodiments, the guest data may be stored in memory 172, and the processor 170 can retrieve the guest data using the user ID 12. 【0058】 In some embodiments, to collect sufficient guest data, the processor 170 may optionally check guest data (process block 206) through, for example, the account tab 14 and / or the notification tab 16 (as indicated by the dashed box). As described above with respect to Figure 5, the processor 170 may determine guest data through the gameplay hub 10 and / or the amusement park. For example, guest data from the amusement park may indicate that the guest has purchased a ticket for the Halloween event at the amusement park. The processor 170 may request information about the purchased ticket in order to check or determine further preference-based information about the guest, in particular to provide a customized interaction during the Halloween event. As described above with respect to Figure 3, the processor 170 may check or request such information through the notification tab 16. Specifically, the processor 170 may request additional information about the Halloween event within the notification tab 16 in order to determine preference-based information about the guest. For example, in response to receiving guest data indicating that the guest has purchased a ticket for the Halloween event, the processor 170 may request information about the guest's fears. 【0059】 In addition to or instead of this, the processor 170 may optionally receive guest data from a third-party application 186 and / or a guest mobile device 120 (process block 208) (as indicated by the dashed box). As described with respect to Figure 5, the guest may enable the gameplay system 150 to access or receive guest data from the third-party application 186 and / or the mobile device 120. Guest data may include data related to the guest on the third-party application 186, such as data from social media applications, banking applications, medical applications, and other applications that may reside on the same device as the gameplay hub 10 (e.g., the mobile device 120 as a mobile phone). In addition to or instead of this, the processor 170 may also receive guest data indicating preferences from the mobile device 120, such as font or text size, favorite digital icons or images used to express emotions in messages (e.g., ghost icons), and GPS. In some embodiments, the guest may access the gameplay system 150 from non-mobile computer devices such as web browsers on a desktop computer, laptop, and tablet. In this embodiment, when the guest enables the gameplay system 150 and receives its own data, the processor 170 receives guest data from these devices. 【0060】 After receiving guest data from the third-party application 186 and / or mobile device 120, the processor 170 can confirm and update the guest data based on the third-party application 186 and / or mobile device 120 (process block 210). That is, if the third-party application 186 and / or mobile device 120 provides additional or different data that is different from the guest data currently stored, the processor 170 can update the guest data and corresponding preferences. Based on the updated preferences, the processor 170 can modify the gameplay content that the guest perceives as unique or customized to them (process block 212). 【0061】 Specifically, the processor 170 can update gameplay content on the guest-enabled display interface 11 based on guest data (e.g., initially retrieved guest data or updated guest data). Figure 7 shows the modified display interface 11 of the gameplay hub 10 for illustrative purposes. As shown, in contrast to the display interface 11 of Figure 1, which provided a uniform game display to the guest, multiple games are organized based on guest data. That is, the gameplay content is modified for the guest based on guest data indicating the guest's preferences. 【0062】 The recommended game set 26 for recommended game 20 includes the 5th game, the 1st game, and the 6th game in the organized game list of the gameplay hub 10. Thus, the processor 170 can update recommendations based on guest data, rather than recommending the 1st, 2nd, and 3rd games, which can be based on the most frequently played games by the guest or all guests, as described with respect to Figure 1. For example, if a guest may have recently visited the amusement park, the processor 170 can recommend the 5th game, which may be related to the amusement park, as a top pick. Similarly, the processor 170 can also update the popular game set 28 for popular game 22 and the archived game set 30 for archived game 24 based on guest data. Thus, the processor 170 can change the gameplay content of the gameplay hub 10 based on guest data (e.g., indicating guest preferences). Since guest data can change when guest activity changes within the gameplay hub 10 and / or the amusement park, the gameplay content can be dynamically modified. For example, the processor 170 can periodically determine guest data in order to precisely adjust the gameplay content and / or interactions in the amusement park on the display interface 11 of the gameplay hub 10 to match the latest guest data. 【0063】 Referring again to Figure 6, the processor 170 can store guest data for user ID 12 (for example, in memory 172) (process block 214). That is, the processor 170 can receive new or additional data indicating preferences from the various sources mentioned above and store this data for the guest. The processor 170 can tag the data with user ID 12 when storing it so that it can be retrieved later to determine the guest data and update the gameplay content accordingly. 【0064】 To illustrate the process of providing modified interactions in an amusement park, Figure 8 shows a flowchart of process 220 for customizing guest-responsive interactions in an amusement park. Process 220 is described using a specific sequence of actions, but it should be understood that the actions described may be performed in a different order than shown, and some actions may be skipped or not performed at all. In general, at least some of the steps of process 220 can be performed at least partially by the gameplay system 150 of Figure 5. Specifically, these steps can be performed at least partially by the processor 170 of the controller 154, which executes instructions stored in a tangible, non-temporary computer-readable medium such as memory 172. In another or further embodiment, at least some of the steps of process 220 may also be performed by any other preferred component or control logic, etc. 【0065】 The processor 170 can identify guests (process block 222) in order to customize gameplay content to suit a particular guest. Specifically, the processor 170 can identify guests based on user ID 12. For example, input device 168 can provide sensor data to the processor 170, which can use the sensor data to determine the presence of a guest and / or identify the guest. For instance, the processor 170 can determine both the presence and identification of a guest using sensor data obtained from scanning a wearable RFID tag 158 of a guest corresponding to user ID 12. In addition to or instead of this, the processor 170 can also determine both the presence and identification of a guest by performing face and / or body recognition analysis on an image captured by camera 160 and then associating this image with a specific guest and the corresponding user ID 12. 【0066】 As described in detail with respect to Figure 6, the processor 170 can determine guest data based on the user ID 12 associated with the identified guest (process block 224). That is, the processor 170 can obtain guest data by user ID 12 that indicates guest preferences, tracked guest game activity within the gameplay hub 10, tracked guest park activity in the amusement park, etc. In some embodiments, as described in detail with respect to Figure 6, the processor 170 can optionally receive guest data from a third-party application 186 and / or mobile device 120 (as indicated by the dashed box) (process block 226). This allows for more granular determination of guest preferences and information. In such embodiments, the processor 170 can update guest data based on the third-party application 186 and / or mobile device 120 (processor block 228). 【0067】 The processor 170 can modify park interactions (process block 230) based on guest data (e.g., initially retrieved guest data and / or updated guest data) so that guests perceive the interactions as unique or customized to them. Specifically, the processor 170 can modify guest-responsive attractions to provide guests with a customized experience. This customized experience may include, for example, a customized in-park experience that reflects a theme setting indicated as of interest by guest data (e.g., a superhero theme), and additional options for in-park entertainment based on progress in adventure games (e.g., achieving a certain level in the game). 【0068】 Figure 9 illustrates a schematic diagram of a theme park 250 with modified guest-responsive interactions and attractions. Specifically, the theme park 250 includes one or more park features 156 (e.g., displays 178, lighting effects 180, animated figures 182, and / or sound effects systems 184) that can be modified for specific guests in various attractions, zones, pathways, or other areas or surrounding areas of the theme park 250. In the illustrated embodiment, the theme park 250 includes several attractions such as a tunnel ride attraction 252a, a virtual game room attraction 252b, a restaurant attraction 252c, a roller coaster attraction 252d, and a water attraction 252e. Different embodiments of the animated figures 182 (e.g., 182a-182d) can be found throughout the theme park, and the processor 170 can modify the interaction with each of these animated figures so that guests perceive it as a response directed at a specific guest. For example, the restaurant attraction 252c and the tunnel ride attraction 252a may include a display 178 that displays an image of the animated figure 182. The processor 170 may react to the detection of a specific guest, such as detecting a specific guest using a proximity sensor 166 that detects the presence of a human and a camera 160 that identifies a specific guest, and may cause the animated figure 182 to react based on guest data. Furthermore, a virtual embodiment or hologram of the animated figure (e.g., animated figure 182b) in a virtual game within the virtual game room 252b may also react in a similar manner. 【0069】 For example, the processor 170 can determine that a guest is currently on the tunnel ride attraction 252a based on sensor data, for example, from an RFID tag 158. As shown in the figure, the ride cart 262 of the tunnel ride attraction 252a may contain one or more RFID tags 158. As the ride cart 262 moves along the ride track 260, an electronic reader 164 on the ride track 260 can read the RFID tags 158 to indicate the presence of the ride cart 262. Based on the presence of the ride cart 262 and its movement along the ride track 260, the processor 170 can determine that the guest is within a threshold of interest, such as within a distance of one or more park features 156 that can be modified to interact with the guest. In addition to or instead of this, a weight sensor 162 placed on the ride track 260 may also indicate the presence of the ride cart 262 by detecting a weight exceeding a threshold when the ride cart 262 moves over the weight sensor 162. 【0070】 After determining that a ride cart 262 is present and that there is a high probability of a guest being present, further park sensors 152, such as the camera 160 and / or guest-wearable RFID tag 158, can transmit data to the processor 170 (e.g., via the input device 168 in Figure 5) to assist in guest identification. For example, the processor 170 can perform image analysis to match an image with an image corresponding to user ID 12. The processor 170 can also analyze RFID tag data in addition to or instead of the camera 160 to associate the data with user ID 12. In some embodiments, the processor can determine and identify the presence of a guest using the camera 160 and / or RFID tag 158, rather than first determining the presence of a guest based on, for example, the weight of the ride cart 262. 【0071】 The processor 170 identifies a guest, determines guest data for user ID 12, and can then modify the interaction of the tunnel ride attraction 252a based on the guest data. In the illustrated embodiment, the guest data may indicate that the guest has purchased a ticket for a Halloween event at the amusement park and that the guest is afraid of clowns. Specifically, the processor 170 can determine that the guest has answered a question regarding ticket purchase in the notification tab 16 of the gameplay hub 10 and can request additional information accordingly. For example, the processor 170 may request information about fears from a particular guest and indicate that the guest is afraid of clowns. Thus, the processor 170 can modify the park features 156 accordingly. Therefore, the processor 170 of the gameplay system 150 can modify the park features 156 in the amusement park 250 based on the guest data determined through the gameplay hub 10. 【0072】 As shown in the figure, in addition to the animated figure on the display 178, the processor 170 can animate the animated figure 182a to make faces or gestures that scare the guest, for example, based on guest data. In some embodiments, the animated figure 182a can be connected to or integrated with a sound effects system 184. Thus, the processor 170 can control the sound effects system 184 to provide audio that scares the guest. For example, the animated figure 182a may say the guest's name as determined based on guest data, ask about a game the guest played earlier in the week, repeat information about a Halloween event the guest attended, ask about family by name, or make comments about the amusement park zone the guest visited. As an example, guest data (e.g., the number of tickets purchased for amusement park 250) may indicate that the guest is visiting amusement park 250 with two other family members, and the processor 170 may then look up data about the other two family members (e.g., the names of family members tagged on a social media application). The processor 170 can analyze video data from camera 160 showing that a guest is riding in a ride cart 262 with other guests while riding in the tunnel ride attraction 252a, and determine that the other guests are family. In some embodiments, the processor 170 can perform further image analysis to verify the identity of the other guests by matching the video data with images on social media applications. Thus, the processor 170 can treat the other guests by their respective names and provide customized interactions for the guest and / or related guests. However, as mentioned above, guests can also control the data shared with the gameplay system 150, and therefore the degree of interactivity can correspond to the degree of data shared. For example, due to these limitations, the processor 170 can also restrict interactions so that only the guest is treated by name, and other family members are not. 【0073】 The tunnel ride attraction 252a may also include other sound effects systems 184 that the processor 170 modifies based on guest data. For example, the processor 170 can cause the sound effects system 184 to play audio (e.g., a theme song) related to the guest's favorite game on the gameplay hub 10. The processor 170 can also cause the lighting effects system 180 to project a clown's face inside the tunnel of the tunnel ride attraction 252a based on guest data. In some embodiments, the park feature 156 can change dynamically based on whether a particular guest is located within a threshold distance from the park feature 156. The processor 170 can modify the park feature 156 based on a particular guest based on the guest's position relative to the park feature 156. For example, the processor 170 can modify the left-side park feature 156 of the tunnel ride attraction 252a for a guest located to the left of the ride cart 262, and modify the right-side park feature of the tunnel ride attraction 252a for a guest located to the right of the ride cart 262. Similarly, if a tracked guest moves out of the range of the park feature 156 and another guest moves into the range of the park feature 156 (for example, if a ride cart 262 moves along the ride track 260), the processor 170 may stop modifying the park feature 156 for this different guest (for example, projecting a spider into the tunnel for the guest on the next ride cart 262). 【0074】 As another example, the processor 170 can also modify the animated figure 182d based on the identified guest within the threshold range 183 that is closest to the animated figure 182d. As shown in the figure, the processor 170 can direct the animated figure 182d to react to the first guest in the guest group 254 that is within the threshold range 183. The processor 170 can stop the interaction and / or switch (for example, to a second guest that is within the threshold range 183) after the first guest has moved out of the threshold range 183 and / or after interacting with the guest for a predetermined period of time. The processor 170 can also generate various interactions depending on the combination of preferences of the group and the individuals within the group (e.g., a first interaction when a first guest is present, a second interaction when a second guest is present, a third interaction when both the first and second guests are present, etc.). For example, when overlapping interests are identified among the majority of group members, those interests can be used to provide interactions, random selection or combinations of interactions can be chosen based on the preferences of the individuals in the group, and interactions can be cycled based on group preferences. In some embodiments, if a guest is within the threshold range 183 but is not facing the animated figure 182d, the processor 170 can cause the animated figure 182d to turn and provide a modified interaction. As described in detail with respect to Figure 5, the monitoring system 157 and / or service desk 159 can monitor the processor 170 of the amusement park 250 and the gameplay system 150 to ensure that amusement park operations are completed as expected. 【0075】 Referring again to Figure 8, the processor 170 can store guest data for user ID 12 (process block 232). That is, the processor 170 can receive new or additional data indicating preferences from the various sources described above and store this data for the guest. For example, new data may include guest activities (e.g., reactions) and / or services provided to the guest related to the changed park features 156 (e.g., the service desk 159 resolved that the queue for a ride the guest visited was unexpectedly long). The processor 170 can tag the data with user ID 12 when storing it so that it can be retrieved later to determine the guest data and update the park interactions accordingly. In this way, the gameplay system 150 can integrate guest activities in the amusement park 250 and guest activities in the gameplay hub 10 to provide guest-specific, guest-responsive interactions. 【0076】 While this specification illustrates and describes only a few features of the present disclosure, many modifications and changes will come to mind for those skilled in the art. Therefore, it should be understood that the appended claims are intended to include all such modifications and changes in accordance with the true spirit of this disclosure. Furthermore, it should be understood that any features illustrated or described in the above-mentioned figures can be combined in any suitable manner. 【0077】 The claimed technologies described herein refer to and apply to tangible objects and specific examples of a practical nature that are not abstract, intangible, or purely theoretical, but which certainly improve the art. Furthermore, if any of the claims appended to the end of this specification contain one or more elements designated as "...means for performing [function]" or "...steps for performing [function]," such elements should be interpreted in accordance with 112(f) of the United States Patent Act. On the other hand, any claim containing elements designated in any other form should not be interpreted in accordance with 112(f) of the United States Patent Act. [Explanation of Symbols] 【0078】 10 Gameplay Hubs 11 Display Interfaces 12 User ID 14 Account Tab 16. Notifications tab 18 Play Score 20 Recommended Games 22 Popular Games 24 Games in the Archive 26 Recommended Game Sets 28 Popular Game Sets 30 game sets within the archive

Claims

[Claim 1] It is an integrated gameplay system, A gameplay platform configured to provide access to multiple games, An amusement park that includes an attraction that has one or more attraction features, Controller and The controller includes, The presence of guests in the aforementioned gameplay platform, the aforementioned attraction, or a combination thereof is detected. Identify the aforementioned guest, Based on the identification of the aforementioned guest, the guest data is determined, In response to determining the guest data, based on the guest data, the system determines modifications to the arrangement of the multiple games on the display interface of the gameplay platform, modifications to one or more attraction features, or a combination thereof. A control signal is transmitted indicating a modification of the gameplay platform, a modification of one or more attraction features, or a combination thereof. It is configured in such a way. Integrated gameplay system. [Claim 2] The aforementioned controller, Track guest gaming activity on the aforementioned gameplay platform, Track guest park activities at the aforementioned amusement park, The tracked guest game activities and the tracked guest park activities are stored as guest data. The integrated gameplay system according to claim 1, configured as described above. [Claim 3] The integrated gameplay system according to claim 1, wherein the controller is configured to request data indicating guest preferences from the gameplay platform, the amusement park, a third-party application, a mobile device associated with the guest, or a combination thereof, in order to determine the guest data. [Claim 4] The integrated gameplay system according to claim 1, wherein the controller is configured to request data indicating guest preferences from third-party applications, including social media applications, medical applications, banking applications, global positioning system applications, or a combination thereof, in order to determine the guest data. [Claim 5] The integrated gameplay system according to claim 1, wherein the modification of one or more attraction features correlates with preferences related to the guest and other guests detected together with the guest. [Claim 6] The integrated gameplay system according to claim 1, wherein the gameplay platform requests additional information related to the guest data on the gameplay platform in order to update the guest data. [Claim 7] The integrated gameplay system according to claim 1, wherein the granularity of the guest data correlates with restrictions set for the sharing of data from the gameplay platform, the amusement park, or a combination thereof. [Claim 8] The aforementioned controller, Track guest park activities, The tracked guest park activities are provided to the amusement park's service desk. The integrated gameplay system according to claim 1, configured as described above. [Claim 9] The integrated gameplay system according to claim 1, wherein the one or more attraction features include animated figures, lighting effects, sound effects, displays, or a combination thereof. [Claim 10] The integrated gameplay system according to claim 1, wherein the controller is configured to determine, based on sensor data from one or more sensors located in close proximity to the one or more attraction features, that the guest is within a threshold distance from the one or more attraction features in order to detect the presence of the guest. [Claim 11] The integrated gameplay system according to claim 10, wherein the one or more sensors include a radio frequency identification (RFID) tag, a camera, a weight sensor, an electronic reader configured to read the RFID tag, or any combination thereof. [Claim 12] The integrated gameplay system according to claim 1, wherein the modification of the arrangement of the plurality of games on the display interface and the modification of the one or more attraction features correlate with one or more fears associated with the guest. [Claim 13] The integrated gameplay system according to claim 1, wherein the gameplay platform is configured to provide one or more notifications related to the amusement park. [Claim 14] A method for modifying gameplay content, Guests receive an indication that they are online on the gameplay platform, Identifying the aforementioned guest in a manner related to user identification, Based on the user identification, determine guest data corresponding to guest park activities at the amusement park related to the gameplay platform, Based on the aforementioned guest data, modify the gameplay content on the display interface of the gameplay platform, Methods that include... [Claim 15] Receiving additional guest data from third-party applications, guest-related mobile devices, or a combination thereof, Before modifying the aforementioned gameplay content, update the guest data based on the aforementioned additional guest data, The method according to claim 14, including the method described in claim 14. [Claim 16] The updated guest data is tagged with the user identification, The updated guest data is stored as the guest data, The method according to claim 15, including the method described in claim 15. [Claim 17] The method of claim 15, further comprising verifying the guest data with the guest on the gameplay platform before updating the guest data. [Claim 18] The method according to claim 14, wherein the guest data includes information entered on the gameplay platform, and modifying the gameplay content includes providing a theme based on the guest data. [Claim 19] A method for modifying amusement park attractions, The system receives sensor data from one or more sensors indicating the presence of guests in close proximity to one or more attraction features of amusement park attractions, Identifying the aforementioned guest in a manner related to user identification, Determining guest data based on the aforementioned user identification, Receiving additional guest data from one or more third-party applications, Updating the guest data based on the additional guest data from the third-party application, Modify the amusement park attractions based on the updated guest data, Methods that include... [Claim 20] The method according to claim 19, wherein the modification includes at least a change to the animated figures, lighting effects, sound effects, displays, or combination thereof of the amusement park attraction.

Images