Programs and Information Processing Systems
The program enhances user engagement by enabling location-based information sharing and character acquisition through real-world exploration and social interactions, addressing the lack of interest in existing services.
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- COLOPL
- Filing Date
- 2024-12-25
- Publication Date
- 2026-07-07
AI Technical Summary
Existing services lack the ability to enhance user engagement and interest through location-based interactions and information sharing.
A program that enables a user to receive specific information related to a specific location in the real space and share it with others when predetermined conditions are met, allowing for the initiation of events and the collection of partial information to complete rumor information, which can lead to the acquisition of game characters.
Enhances user engagement and interest by providing interactive location-based experiences, allowing users to collect information and characters through real-world exploration and social sharing, improving the enjoyment of location-based games.
Smart Images

Figure 2026112815000001_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to a program and an information processing system.
Background Art
[0002] Conventionally, a technology capable of providing a service according to the position of a user in the real space has been known (for example, Patent Document 1).
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] The present invention aims to improve the interestingness of services.
Means for Solving the Problems
[0005] In order to solve the above problems, the program of the present invention causes a computer to function as control means for giving a user specific information related to a specific position in the real space, and then enabling the specific information to be given to another user when a predetermined sharing condition is satisfied between the user and the other user.
Effects of the Invention
[0006] According to the present invention, the interestingness of services is improved.
Brief Description of the Drawings
[0007] [Figure 1] It is a diagram for explaining each component of the information processing system. [Figure 2] It is a hardware configuration diagram of the information processing system. [Figure 3]This is a functional block diagram of an information processing system. [Figure 4] This diagram illustrates specific examples of encounter locations and events. [Figure 5] This is a diagram to illustrate specific examples of rumor information. [Figure 6] This is a diagram illustrating a specific example of the gacha lottery process. [Figure 7] This is a diagram illustrating a concrete example of shared processing. [Figure 8] This diagram illustrates a concrete example of how partial information is disseminated. [Figure 9] These are simulated diagrams of specific examples of the gameplay screen and the rumor list screen. [Figure 10] These are simulated diagrams of specific examples of the confirmation screen and distribution status screen. [Figure 11] This is a simulated diagram of a specific example, such as a screen displaying the pass-by log. [Figure 12] This diagram illustrates a concrete example of the process of generating processed content information. [Figure 13] This is a conceptual diagram of a specific example of a machining table. [Figure 14] This is a simulated diagram of a specific example, such as an upload screen. [Figure 15] This is a flowchart of each process of the control device. [Figure 16] This is a diagram illustrating a variation. [Figure 17] This diagram illustrates other variations. [Modes for carrying out the invention]
[0008] Figure 1 is a diagram illustrating the various components of the information processing system 1000. The information processing system 1000 consists of a server device 100 and a terminal device 200. As shown in Figure 1, the server device 100 and the terminal device 200 can communicate with each other via a network N. The network N is assumed to be, for example, the internet.
[0009] The terminal device 200 can be carried by a user, and for example, a smartphone, a personal computer, and a portable game console can be adopted. Further, the terminal device 200 stores various programs including application programs. In reality, a plurality of terminal devices 200 communicate with the server device 100. However, in FIG. 1, for the sake of explanation, one terminal device 200 is extracted and shown.
[0010] The terminal device 200 is configured to be able to acquire position information in the real space. Specifically, the terminal device 200 includes a GPS (Global Positioning System) receiver and is configured to be able to receive GPS signals. The above GPS signals include position information indicating the position of the terminal device 200 on the horizontal plane. In the present embodiment, the position of the terminal device 200 on the horizontal plane of the real space Sr may be described as the "user position Pr" (see FIG. 1). The above user position Pr can be estimated to indicate the position of the user who holds the terminal device 200.
[0011] The server device 100 provides the terminal device 200 with various information used when the terminal device 200 executes an application program. Specifically, by the cooperation of the terminal device 200 and the server device 100, a service that uses the user's position information in the terminal device 200, for example, a game that uses the user's position information (referred to as a position information game) can be executed. In FIG. 1, an example in which the server device 100 is composed of one server device is shown, but the server device 100 may be composed of a plurality of server devices (systems).
[0012] FIG. 2 is a hardware configuration diagram of the information processing system 1000. As described above, the information processing system 1000 includes the server device 100 and the terminal device 200. As shown in FIG. 2, the terminal device 200 includes a processing device 201, a storage device 202, a communication device 203, a display device 204, a GPS receiver 205, an acceleration azimuth sensor 206, and a camera 207. Each of the above components is communicably connected via a system bus.
[0013] The processing device 201 controls the entire terminal device 200. The above processing device 201 may be composed of one or more processors. Specifically, the processing device 201 may be composed of one or more types of processors such as a CPU (Central Processing Unit), GPU (Graphics Processing Unit), DSP (Digital Signal Processor), FPGA (Field Programmable Gate Array), or ASIC (Application Specific Integrated Circuit).
[0014] The storage device 202 stores various programs including a basic program and an application program PGx. As the storage device 202, known recording media such as a semiconductor recording medium and a magnetic recording medium may be adopted. Also, the storage device 202 may be composed of one recording medium or a plurality of recording media. The application program PGx is pre-downloaded and installed in the terminal device 200. Further, the storage device 202 stores various game data (data indicating an item given to a user, data indicating the status of a user character, etc.) used in the location information game.
[0015] The display device 204 is configured to include a display panel 204a and a touch panel 204b. The display panel 204a is, for example, a flat display composed of an organic EL (Electro Luminescence). The touch panel 204b is configured to be able to detect a touch operation of a user. Specifically, the touch panel 204b is provided overlaid on the display panel 204a and receives a touch operation on the image displayed on the display panel 204a.
[0016] The GPS receiver 205 receives GPS signals from GPS satellites. The acceleration direction sensor 206 is composed of a combination of various sensors, including a compass for detecting direction, an accelerometer, and a gyroscope. The communication device 203 communicates with the server device 100 via the network N. The camera 207 includes an image sensor and generates an image by converting incident light entering through the lens into an electrical signal.
[0017] The server device 100 comprises a processing unit 101, a storage device 102, and a communication device 103. Each of these components is connected via a system bus for communication. The processing unit 101 controls the entire server device 100. The processing unit 101 of the server device 100, like the processing unit 101 of the terminal device 200 described above, may consist of one or more processors. Specifically, the processing unit 101 may consist of one or more types of processors, such as a CPU, GPU, DSP, FPGA, or ASIC.
[0018] The storage device 102 stores various programs, including the basic program and the game management program PGy. For the storage device 102 of the server device 100, known recording media such as semiconductor recording media and magnetic recording media may be used. The storage device 102 may consist of one recording media or multiple recording media. Furthermore, the storage device 102 stores various game data used in location-based games (such as data indicating items assigned to the user and data indicating the status of the user character) in association with the user's identifier. The communication device 103 communicates with the terminal device 200 via the network N.
[0019] Figure 3 is a functional block diagram of the information processing system 1. As shown in Figure 3, the information processing system 1 of this embodiment is composed of a management device 10 and a terminal device 20. For example, the terminal device 200 described above functions as a terminal device 20 by executing the application program PGx. Also, the server device 100 described above functions as a management device 10 by executing the game management program PGy. Each of these components can communicate via the network N.
[0020] The management device 10 is configured to include control means 11 and storage means 12. For example, the above-mentioned storage device 102 functions as the storage means 12. However, the terminal device 20 may be configured to have some or all of the functions of the management device 10.
[0021] The management device 10 (control means 11) provides the user with specific information (partial information dp1-4 described later) related to a specific location in the real space Sr (encounter spot res described later), and then, when predetermined sharing conditions are met between the user and other users, it makes it possible to provide the specific information to the other user. Specifically, the specific information consists of multiple (for example, four) parts of information dp (1-4). When the user has collected multiple parts of information dp (completed rumor information Dx described later), the control means 11 makes it possible to start an event related to the specific location (encounter event described later). The above configuration will be described in detail later.
[0022] The management device 10 can initiate an event (encounter event) related to a specific location (see Figure 4(b) below) if the user is located at a specific location (the user is located at the encounter spot res), even if the user has not acquired specific information (even if the rumor information Dx in Figure 5 has not been completed). If the user has acquired specific information, the management device 10 can initiate an event related to that specific location even if the user is not located at the specific location (see Figure 10(d) below). The above configuration will be described in detail later.
[0023] In the above configuration, the system may be configured such that a specific location (encounter spot res) changes after a predetermined period of time (for example, about one week). Furthermore, in the above configuration, the new specific location may be determined according to the current specific location. Specific examples of the above configuration will be described in detail later using Figure 16(a) as an example of a modified version.
[0024] Furthermore, in the above configuration, specific information may be provided for each of several specific locations, and the configuration may be designed to make it easier for the user to access specific information set by the user from among the multiple types of specific information. Specific examples of the above configuration will be described in detail later using Figures 16(b-1) and 16(b-2) as examples of modifications.
[0025] Furthermore, in the above configuration, it is possible to set a predetermined location (Pw) that is different from the user's current location in the real space Sr (user location Pr), and to assign specific information that has been assigned to other users within a predetermined range from the predetermined location to the user who has set the predetermined location. Specific examples of the above configuration will be described in detail later using Figures 16(a-1) and 16(a-2) as examples of modifications.
[0026] The management device 10 (control means 11) can accept permission from the user to process content information Cu that the user has photographed or recorded, and can generate processed content information Ca in which additional information Ga corresponding to events in the game is added to the content information Cu. The above configuration will be described in detail later with reference to Figure 12.
[0027] Furthermore, the management device 10 can accept permission to share the processed content information Ca with other users (see Figure 14(b-1) below). The processed content information Ca described above is intended to indicate the start conditions of an event (encounter event) (see Figure 13 below). In addition, the processed content information Ca described above can be further processed by the user (see Figure 14(b-2) below). In addition, the above configuration may be configured to acquire the user's location information in real space and generate processed content information Ca according to that location information. Specific examples of the above configuration will be described in detail as modifications (see Figure 17(b)).
[0028] Figure 4(a) is a diagram illustrating a specific example of an encounter spot res. As shown in Figure 4(a), encounter spots res are established in each region.
[0029] In this location-based game, when the user's location Pr is located at an encounter spot res, the encounter event described below can be initiated. In the encounter event, predetermined rewards are given to the user. For example, in the encounter event, the user is given a character C (1, 2, ...). Specifically, the character C corresponding to the encounter spot res is given in the encounter event. That is, the character C given in the encounter event differs for each encounter spot res.
[0030] Each encounter spot res in this embodiment is, for example, located in a real-world space Sr where there are actual rumors of sightings of unidentified mysterious animals (so-called UMAs). The character C assigned to each encounter spot res represents the unidentified mysterious animal corresponding to the rumors at that encounter spot res.
[0031] For example, in the specific example in Figure 4, we assume that there is a rumor that an unidentified flying object (so-called UFO) has been sighted at encounter spot res1 among the various encounter spots res. In this specific example, the user is assigned character C1, which represents an alien, during the encounter event at encounter spot res1. Also, in the specific example in Figure 4, we assume that there is a rumor that a Tsuchinoko has been sighted at encounter spot res2. In this specific example, the user is assigned character C2, which represents a Tsuchinoko, during the encounter event at encounter spot res2.
[0032] Figure 4(b) is a diagram illustrating a specific example of encounter processing. The management device 10 executes encounter processing in the encounter event described above. Specifically, as shown in Figure 4(b), the encounter spot rse is an area of a predetermined size (for example, the area inside a circle with a radius of approximately 50 meters). When a user (user position Pr) is located in the above encounter spot rse, and the predetermined start conditions (see Figure 5 below) are met, an operation to start the encounter event (touch operation of object Gx shown in Figure 9(a) below) becomes available.
[0033] When an encounter event begins, the encounter processing is executed, and as shown in Figure 4(b), character C is assigned to the user. Specifically, during the period before the user progresses through the encounter event (before character C is assigned), the image that shows the detailed appearance of character C is hidden (see area Rc in Figure 10(a) described later). On the other hand, a user who possesses character C can display an image that shows the appearance of character C. With this configuration, the user can be given the enjoyment of imagining what character C looks like during the period before encountering character C.
[0034] Furthermore, in an encounter event (encounter processing), in addition to character C, rumor information Dx corresponding to character C is assigned to the user. As shown in Figure 4(b), the rumor information Dx consists of character information dt corresponding to the rumor information Dx, and partial information dp1 to dp4 corresponding to the rumor information Dx. The character information dt of the rumor information Dx is information about character C that is assigned along with the rumor information Dx in the encounter event. In addition, each partial information dp(1 to 4) assigned in the encounter event is information that suggests the start conditions of the encounter event (such as the encounter spot res).
[0035] In this embodiment, an encounter event can be initiated when a user of an encounter spot (res) happens to meet the above-mentioned initiation conditions. For the purposes of this explanation, a user who happens to meet the initiation conditions for an encounter event may be referred to as the "encounter user." As will be explained in detail later, if predetermined sharing conditions are met between the encounter user and another user, one of the partial information (dp) is assigned to that other user (see Figure 7). Furthermore, if a user who has been assigned partial information (dp) meets the sharing conditions with yet another user, that partial information (dp) is assigned to that other user (the partial information (dp) is shared).
[0036] In other words, rumor information Dx (partial information dp) is spread from encountering users to other users, just like actual rumors (see Figure 8(a) below). Also, as will be explained in more detail later, users who collect each part of information dp (1-4) to complete rumor information Dx can start an encounter event without actually moving to the encounter spot res (see Figure 11(d) below).
[0037] Figure 5 is a diagram illustrating a specific example of rumor information Dx. As mentioned above, rumor information Dx consists of character information dt and individual sub-information dp (1-4). Character information dt is information about character C. Specifically, character information dt includes the name of character C (in the example in Figure 5, it is "alien").
[0038] Based on the character information dt described above, the character C that will be granted in the encounter event that becomes available when the rumor information Dx is completed (when each part of the information dp(1~4) is collected) can be determined. As will be explained in detail later, among the information (dt, dp1~4) that makes up the rumor information Dx, the character information dt can be obtained by using a predetermined item (in-game currency). In other words, in this embodiment, in order to obtain the desired character C, the user needs to obtain the character information dt of that character C using in-game currency and then collect each part of the information dp(1~4) (except when an encounter spot res is discovered by chance). Note that in-game currency is granted on various occasions. For example, in-game currency is granted once a day when the application program PGx is launched.
[0039] The above configuration has the advantage of improving the game's enjoyment compared to a configuration where character C is directly granted by using in-game currency. It is also possible to have a configuration where some or all of character C can be obtained directly with in-game currency. In the above configuration, it is preferable that the amount of in-game currency required to obtain the character information dt corresponding to character C (the amount of in-game currency required to perform one gacha draw) is less than the amount of in-game currency required to directly obtain character C.
[0040] As described above, each sub-information dp(1-4) of rumor information Dx suggests the conditions for initiating an encounter event. Specifically, the initiation conditions include environmental conditions, location conditions, and behavioral conditions. Of the sub-information dp, sub-information dp1 suggests the environmental conditions among the above initiation conditions. These environmental conditions are the conditions related to the environment in which an encounter event can be initiated, and may differ for each encounter event. For example, an encounter event can be initiated if any of the environmental conditions, including "the user is located at the encounter spot res during a predetermined time period" or "the encounter spot res has predetermined weather conditions (sunny, rainy, etc.)", are met. In the specific example in Figure 5, sub-information dp1 is assumed to suggest the environmental condition "the user is located at the encounter spot res around 12 o'clock".
[0041] Of the partial information dp, partial information dp2 and partial information dp3 suggest the location condition among the conditions for initiating an encounter event. The location condition is that the user is located at the encounter spot res. Of the partial information dp(2, 3) that suggest the location condition (encounter spot res), partial information dp2 suggests a relatively broad area where the encounter spot res is located. For example, partial information dp2 indicates the name of the city or town where the encounter spot res is located (in the example in Figure 5, it is "XX City"). Partial information dp3 indicates a narrower (more specific) location of the encounter spot res than the location indicated by partial information dp2. For example, partial information dp3 indicates the name of the facility located at the encounter spot res (in the example in Figure 5, it is "XX Museum").
[0042] Among the conditions for initiating an encounter event, the behavioral conditions are those related to the user's actions required to initiate the encounter event, and these may differ for each encounter event. Partial information dp4 of each partial information dp suggests these behavioral conditions. For example, an encounter event can be initiated if either of the behavioral conditions, including "stopping at the encounter spot res for a predetermined amount of time" or "moving at the encounter spot res at a predetermined speed," is met. In the specific example in Figure 5, partial information dp4 suggests a case where the behavioral condition is "stopping at the encounter spot res for approximately 5 minutes." The time the user stopped and the user's movement speed can be calculated by the management device 10 acquiring the user's position Pr at predetermined time intervals.
[0043] Figure 6(a) is a diagram illustrating a specific example of the gacha lottery process. As described above, even users who have not reached an encounter spot res (hereinafter referred to as "non-encounter users") can obtain character information dt by consuming in-game currency. Specifically, when a predetermined operation is received on the terminal device 20, the management device 10 consumes the user's in-game currency and executes the gacha lottery process. In the gacha lottery process described above, the management device 10 randomly determines one of the characters C at each encounter spot res and assigns the character information dt corresponding to the determined character C to the user.
[0044] In this embodiment, it becomes possible to collect partial information dp(1-4) corresponding to character information dt, provided that the user possesses the character information dt. Specifically, if a non-encounter user possessing character information dt passes by another user (for example, an encountered user) who possesses any of the partial information dp(1-4) corresponding to the character information dt, the partial information dp is assigned to the non-encounter user as "part of a rumor." However, even if a user passes by another user who possesses partial information dp(1-4) corresponding to the character information dt, the partial information dp will not be assigned to a user who does not possess the character information dt. The above configuration will be described in detail later with reference to Figure 7.
[0045] The left side of Figure 6(b) is a conceptual diagram of a specific example of character information dt immediately after it is assigned by the gacha lottery process. The specific example in Figure 6(b), as in Figure 5 above, shows character information dt corresponding to "Alien" among character C. As shown in the left side of Figure 6(b), the character information dt immediately after it is assigned by the gacha lottery process does not include partial information dp(1~4). It is difficult to infer the encounter spot res from the above character information dt.
[0046] The right-hand portion of Figure 6(b) is a conceptual diagram of another specific example of character information dt. The specific example on the right-hand portion of Figure 6(b) assumes a case where a user who has obtained character information dt through a gacha lottery process satisfies the sharing conditions with another user who possesses partial information dp(1~4) of that character information dt. In this case, one of the partial information dp(1~4) possessed by one user is granted (shared) with the other user. The specific example in Figure 6(b) assumes that partial information dp2 is shared among the various partial information dp(1~4).
[0047] In this embodiment, even before completing the rumor information Dx (without collecting all the partial information dp(1-4)), the encounter event can be started by the user moving to the encounter spot res. Furthermore, each of the partial information dp(2,3) of the rumor information Dx suggests the actual encounter spot res. Therefore, some users (for example, users whose local area is where the encounter spot res is located) may be able to infer the encounter spot res even before collecting all the partial information dp. In such cases, the user can start the encounter event by moving to the encounter spot res, even before completing the rumor information Dx.
[0048] However, some users may find it difficult to actually travel to an encounter spot (res) even if they can guess the location. For example, a user living far from an encounter spot (res) may find it difficult to travel there even if they complete the rumor information (Dx). Let's assume a configuration where the encounter event cannot be started unless the user actually travels to the encounter spot (res). In this configuration, some users may find it inconvenient that they cannot proceed with the encounter event even if they complete the rumor information (even if they find the encounter spot (res)).
[0049] To mitigate the aforementioned inconveniences, this embodiment employs a configuration that allows users who have completed rumor information Dx to start an encounter event without having to move to the encounter spot res. This configuration suppresses the aforementioned inconveniences. Furthermore, this embodiment employs a configuration that allows users who do not possess character information dt to start an encounter event at the encounter spot res. However, if a user does not possess character information dt, the configuration may be such that the encounter event cannot be started even if the user reaches the encounter spot res.
[0050] Figure 7 is a diagram illustrating a specific example of the sharing process. As described above, when the sharing conditions are met between a user who does not possess partial information dp(1-4) and another user who possesses that partial information dp(1-4), the partial information dp(1-4) becomes shareable between the users. Specifically, when the users pass each other, the sharing process becomes executable, and the partial information dp(1-4) is shared between the users.
[0051] The specific example in Figure 7 assumes a case where partial information dp(1-4) of user Ua, who possesses terminal device 20a, is assigned (shared) with user Ub, who possesses terminal device 20b. As shown in Figure 7, user Ua is located at user location Pra, and user Ub is located at user location Prb. It is also assumed that user Ua possesses character information dt and all the corresponding partial information dp(1-4) (possesses the completed rumor information Dx). Furthermore, it is assumed that in the period before the sharing process is executed, user Ub possesses the character information dt but does not possess the partial information dp(1-4).
[0052] As shown in Figure 7, the area from the user (user position Pr) to a predetermined distance is set as the user's "shared area Rt". The management device 10 determines whether another user possessing partial information dp(1~4) corresponding to the character information dt possessed by the user is located in the user's shared area Rt. If another user possessing the above partial information dp(1~4) is located in the user's shared area Rt, one of the partial information dp(1~4) is selected and shared by each user.
[0053] For example, in the specific example in Figure 7, we assume that user Ub is located in the shared area Rt of user Ua. In this case, one of the partial information dp(1~4) possessed by user Ua is selected during the sharing process and becomes available to be assigned (shared) to user Ub. In the specific example in Figure 7, we assume that partial information dp2 of the partial information dp(1~4) possessed by user Ua becomes available to be assigned to user Ub.
[0054] In the sharing process of this embodiment, if a user (user Ua) possesses multiple (for example, 4) partial information dp(1-4) that can be shared with other users (user Ub), a random partial information dp is selected and made shareable. Specifically, the probability of a partial information dp(1-4) being selected to be shared with another user is the same for all partial information dp. For example, consider a case where a user possessing two partial information dp shares one of those partial information dp with another user. In this case, the probability of each partial information dp being selected is approximately 1 / 2 and is common to all. Note that partial information dp already possessed by another user may or may not be excluded from being shared with that other user.
[0055] In this embodiment, regardless of whether a user possesses all or only some of the partial information dp(1-4) (regardless of whether or not they have completed the rumor information Dx), the user's partial information dp may be shared with other users. Specifically, the partial information dp(1-4) of users other than the encountered user may also be shared by that user with other users. For example, a user who possesses partial information dp1 and partial information dp2 of partial information dp(1-4) may share partial information dp1 or partial information dp2 with another user.
[0056] Figure 8(a) is a diagram illustrating a specific example of how partial information dp, which constitutes rumor information Dx, is distributed to each user. As described above, in this embodiment, rumor information Dx (partial information dp) is initially assigned to the user who encounters it. Furthermore, the partial information dp of rumor information Dx is shared with other users located in the encounter user's shared area Rt (see Figure 7 above). However, the area in which each user travels on a daily basis (hereinafter referred to as "living area") is usually limited to a small area. Therefore, other users who directly share the encounter user's partial information dp are limited to users within that encounter user's living area.
[0057] Let's assume a configuration where partial information dp of rumor information Dx is shared only by users who encounter it. In this configuration, non-encounter users who can collect all the partial information dp constituting rumor information Dx are limited to non-encounter users who live within the encountering user's area of residence. Therefore, non-encounter users who do not live within the encountering user's area of residence may find it excessively difficult to collect partial information dp, which could lead to a decrease in their motivation to play the game.
[0058] Considering the above circumstances, this embodiment employs a configuration that suppresses the aforementioned disadvantages. Specifically, when partial information dp of an encountered user is shared with a non-encountered user, the configuration is such that partial information dp is shared with other non-encountered users who satisfy the sharing conditions with that non-encountered user. More specifically, when another non-encountered user is located in the shared area of a non-encountered user from whom partial information dp has been shared, the configuration is such that partial information dp is shared with that other non-encountered user.
[0059] For example, the specific example in Figure 8(a) assumes that the encountered user Ua is assigned rumor information Dx (all partial information dp1-4). It also assumes that among the non-encountered users (Ub-Uf), non-encountered users Ub and Uc are in the living area of encountered user Ua, while the other non-encountered users (Ud-Uf) are not. Furthermore, it assumes that among the partial information dp(1-4) possessed by encountered user Ua, partial information dp1 is directly shared with non-encountered user Ub, and partial information dp2 is directly shared with non-encountered user Uc.
[0060] In the specific example in Figure 8(a), we assume that non-encountered user Ud is not in the living area of encountered user Ua, but is in the living area of non-encountered user Ub. In this case, non-encountered user Ud does not directly share partial information dp of encountered user Ua, but may share partial information dp1 of non-encountered user Ub. The specific example in Figure 8(a) assumes that partial information dp1 of non-encountered user Ud is further shared with non-encountered user Uf. Similarly, we assume that partial information dp2 of non-encountered user Uc is shared with non-encountered user Ue, and then partial information dp2 of non-encountered user Ue is shared with non-encountered user Uf.
[0061] As can be understood from the above explanation, the partial information dp of an encountered user is disseminated to a wider area than the living sphere of the encountered user Ua through other non-encountered users. With this configuration, non-encountered users who are outside the living sphere of an encountered user can also collect all of the partial information dp.
[0062] Incidentally, it is common for population density (resident population, daytime population) to differ from region to region (for example, a city, town, or village). Given these circumstances, if the size of the shared area Rt were uniform regardless of the region where the user is located (hereinafter referred to as "proportional"), it would be difficult to maintain fairness among users, which could be problematic.
[0063] For example, in the proportional relationship described above, in areas with high population density (e.g., urban centers), many other users will pass through a user's shared area Rt even if the user hardly moves at all. Therefore, users in areas with high population density can easily share partial information dp of other users without moving much. On the other hand, users in areas with low population density need to travel over a wide area to obtain partial information dp from other users. To mitigate these inconveniences, this embodiment employs a configuration in which the shared area Rt can change depending on the region.
[0064] Figure 8(b) is a conceptual diagram of a specific example of a shared area determination table. The management device 10 variably determines the shared area Rt for a user (user location Pr) according to the region (A, B, C…) in which the user is located. Figure 8(b) shows excerpts of the shared area Rt for regions A, B, and C. Region A has a higher population density (resident population, daytime population) than region B. Region B also has a higher population density than region C.
[0065] As shown in Figure 8(b), if the user's location Pr is in region A, the shared area Rt extends approximately 500 meters from that user's location Pr. Similarly, if the user's location Pr is in region B, the shared area Rt extends approximately 1 kilometer from that user's location Pr. Likewise, if the user's location Pr is in region C, the shared area Rt extends approximately 10 kilometers from that user's location Pr.
[0066] In this embodiment, the shared area Rt becomes smaller for users in areas with high population density (e.g., area A) and larger for users in areas with low population density (e.g., area C). Therefore, fairness for each user is easier to maintain compared to the proportional relationship described above. However, the present invention does not exclude the proportional relationship described above, and a configuration in which the shared area Rt does not change regardless of the region is also possible. Furthermore, the size of the shared area Rt for users in each region is not limited to the example shown in Figure 8(b).
[0067] Figure 9(a) is a conceptual diagram of a specific example of the play screen Mp. As shown in Figure 9(a), the play screen Mp consists of a display area Rp1, a display area Rp2, a rumor list display button Bp1, a pass-by log display button Bp2, a companion UMA display button Bp3, and an upload button Bp4.
[0068] The virtual space Sv is displayed in the display area Rp1 of the play screen Mp, and the location-based game progresses in this virtual space Sv. Specifically, in the location-based game, various events can be progressed in the virtual space Sv by the user moving in the real space Sr. The virtual space Sv is displayed based on map information and user location Pr in the real space Sr. The above map information is provided, for example, from the management device 10 to the terminal device 20. However, the management device 10 may be configured to acquire map information from an external server and transfer that map information to the terminal device 20. The user location Pr is identified using the GPS signal described above.
[0069] As shown in Figure 9(a), various objects are displayed in the virtual space Sv. Specifically, the virtual space Sv consists of a user location image Gp, a ground surface image Gg, and objects Gx. Note that in the specific example in Figure 9(a), only a selection of the objects displayed on the map screen Mp are shown.
[0070] The ground image Gg in the virtual space Sv is displayed in the area corresponding to the ground surface in the real space Sr. The ground image Gg is displayed based on map information in the real space Sr. Specifically, the ground image Gg displays road areas at locations corresponding to roads in the real space Sr. In addition, the ground image Gg displays sea areas at locations corresponding to the sea in the real space Sr, and river areas at locations corresponding to rivers in the real space Sr. In other words, the ground image Gg represents a map of the real space Sr. In this embodiment, the virtual space Sv corresponding to the real space Sr up to a predetermined distance (for example, about 5 kilometers) from the user's position Pr is displayed on the play screen Mp.
[0071] The user location image Gp indicates the user's position in the virtual space Sv. As shown in Figure 4, the user location image Gp is displayed on the user location Pv. The user location Pv in the virtual space Sv corresponds to the user location Pr in the real space Sr. In other words, the user location Pv indicates the user location Pr on the map of the real space Sr represented by the ground image Gg. Specifically, as the user location Pr identified from the GPS signal moves, the user location Pv in the virtual space Sv moves. That is, as the user moves in the real space Sr, the user location image Gp moves in the virtual space Sv.
[0072] For explanatory purposes, the location in the virtual space Sv corresponding to an encounter spot res in the real space Sr may be referred to as "encounter spot ves". Encounter events associated with an encounter spot res in the real space Sr are also associated with the encounter spot ves in the corresponding virtual space Sv. Each encounter spot ves in the virtual space Sv has an object Gx that corresponds to the encounter event associated with that encounter spot ves.
[0073] In this embodiment, object Gx is displayed in a manner corresponding to the character C assigned in the encounter event corresponding to the encounter spot ves where object Gx is displayed. When the user touches object Gx on the play screen Mp, the encounter event corresponding to the encounter spot res is started. However, if the conditions for starting the encounter event are not met, the encounter event will not start even if object Gx is touched. Specifically, object Gx represents only the silhouette of character C assigned in the encounter event, and does not represent the actual appearance of character C. The appearance of character C is kept hidden from the user until the user starts the encounter event.
[0074] The triggers for displaying object Gx can be changed as appropriate. For example, object Gx may be displayed when all the conditions for starting an encounter event (location conditions, environmental conditions, and action conditions) are met. Alternatively, even if the conditions for starting an encounter event are not met, object Gx may be displayed at the encounter spot ves if the virtual space Sv displayed by the play screen Mp includes that encounter spot ves.
[0075] For example, the system may be configured so that object Gx is displayed if only one of the predetermined conditions for starting an encounter event is met, even if the other conditions are not met. Specifically, the system may be configured so that object Gx is displayed if the virtual space Sv displayed on the play screen Mp includes the encounter spot ves during the time period in which an encounter event can be started (when the environmental conditions are met).
[0076] Furthermore, the system may be configured to display object Gx even if the other conditions are not met, as long as only two predetermined conditions for starting an encounter event are met. For example, if the user is located at the encounter spot res during the time period in which an encounter event can be started (meeting both the location and environmental conditions), the system may be configured to display object Gx even if the action conditions are not met. Moreover, even if none of the location, environmental, or action conditions are met, the system may be configured to display object Gx if the virtual space Sv displayed on the play screen Mp includes the encounter spot ves.
[0077] Furthermore, the appearance (display area and angle) of each of the above objects (such as the ground image Gg) changes as the user's position Pv moves. In other words, the appearance of each object in the virtual space Sv changes as the user moves in the real space Sr. Specifically, the play screen Mp displays the virtual space Sv as seen from a predetermined line of sight from the user's position Pv (user position image Gp). The above line of sight may be configured to be changeable according to the user's actions.
[0078] When the Rumor List display button Bp1 on the play screen Mp is selected, the Rumor List screen Ml (see Figure 9(b) below) is displayed in place of the play screen Mp. The Rumor List screen Ml displays a list of character information dt owned by the user. As mentioned above, character information dt is assigned to the user through gacha lottery processing or encounter processing. The user can also select one of the character information dt as "Tracking Information dt".
[0079] As will be described in detail later, in this embodiment, partial information dp corresponding to the character information dt selected as the tracking information dt from among the character information dt possessed by the user is shared with other users. The display area Rp2 of the play screen Mp displays a string corresponding to the currently tracking information dt. Specifically, when all partial information dp corresponding to the additional information dt has been collected, the name of the character C that can be obtained in the encounter event is displayed in the display area Rp2.
[0080] When the StreetPass Log Display button Bp on the Play Screen Mp is selected, the StreetPass Log Display screen Ms (see Figure 11(a) below) is displayed instead of the Play Screen Mp. As will be explained in detail later, the user can obtain partial information dt where the sharing conditions have been met via the StreetPass Log Display screen Ms. When the Companion UMA Display button Bp3 on the Play Screen Mp is selected, a character list screen is displayed showing a list of characters C owned by the user. The character list screen displays images representing the specific appearance of the characters C owned by the user.
[0081] When the upload button Bp4 is selected, the user can upload content information Cu (for example, images taken by the user) (see Figure 14(a)). In this embodiment, in addition to rumor information Dx (each part information dp1-4), processed content information Ca (see Figure 12, described later) may suggest encounter spots res. Furthermore, processed content information Ca is generated by processing each content information Cu uploaded by each user. The above configuration will be explained in detail using Figure 12.
[0082] Figure 9(b) is a simulated example of the rumor list screen Ml. The rumor list screen Ml displays a list of character information dt owned by the user. Specifically, as shown in Figure 9(b), the rumor list screen Ml displays buttons Bl1 and Bl2, various display areas Rl (1, 2, ...), and a return button Bl3.
[0083] Each display area Rl (1, 2, etc.) on the rumor list screen Ml corresponds to one of the character information dt owned by the user. Furthermore, each display area Rl displays various information related to the character information dt it corresponds to. For example, the name of character C corresponding to character information dt is displayed in the display area Rl.
[0084] Furthermore, the display area Rl shows the number of partial information dp (1-4) corresponding to each character information dt that the user has already collected, as well as the number of partial information dp that have not yet been collected. For example, among the display areas Rl(1, 2...), display area Rl1 corresponds to the character information dt of "Alien" among character C. In the specific example in Figure 9(b), we assume that of the partial information dt (1-4) corresponding to the character information dt of character C "Alien", 3 have been collected and 1 has not yet been collected. According to the rumor list screen Ml described above, the user can check the number of collected (and uncollected) partial information dp. The user can, for example, set the character information dt with many collected partial information dp as the information being tracked dt.
[0085] The Rumor List screen Ml can switch between displaying a list of character information dt for which all partial information dp has been collected, and a list of character information dt for which some partial information dp remains uncollected. Specifically, when button Bl1 on the Rumor List screen Ml is selected, the list of character information dt for which some partial information dp remains uncollected is displayed. On the other hand, when button Bl2 on the Rumor List screen Ml is selected, the list of character information dt for which all partial information dp has been collected is displayed.
[0086] Each display area Rl (1, 2…) displays a confirmation screen display button Blx. When the confirmation screen display button Blx for a display area Rl is selected, a confirmation screen Mc (see Figure 10(a) below) is displayed showing details of the character information dt corresponding to that display area Rl. As will be explained in detail later, the user can set (change) the tracking information dt via the confirmation screen Mc. When the return button Bl3 for the rumor list screen Ml is selected, the play screen Mp is displayed instead of the rumor list screen Ml.
[0087] Figure 10(a) is a simulated example of a confirmation screen Mc. The confirmation screen Mc displays the details of the character information dt possessed by the user. The example in Figure 10(a) assumes a confirmation screen Mc that displays the details of the character information dt from the rumor information dt possessed by the user, where uncollected partial information dp remains. As shown in Figure 10(a), the confirmation screen Mc consists of a character display area Rc, character information dt, a distribution status confirmation button Bc1, a tracking setting button Bc2, and a return button Bc3.
[0088] The specific example in Figure 10(a) assumes that among the partial information dp(1-4), partial information dp1, partial information dp2, and partial information dp4 have been collected, while partial information dp3 has not been collected. In this case, the character information dt on the confirmation screen Mc will display partial information dp1, partial information dp2, and partial information dp4, but partial information dp3 will not be displayed. According to the confirmation screen Mc, the user can understand which partial information dp has been collected and which has not been collected. Furthermore, by checking the character information dt (partial information dp) on the confirmation screen Mc, some users may be able to infer the encounter spot res from the character information dt even if there are remaining uncollected partial information dp.
[0089] The character display area Rc of the confirmation screen Mc displays character C corresponding to the character information dt displayed on the confirmation screen Mc. However, if the collection of partial information dp for character information dt is not complete, only the silhouette of character C corresponding to that character information dt is displayed in the character display area Rc (see Figure 10(a)). On the other hand, if the collection of partial information dp for character information dt is complete and the encounter event corresponding to that character information dt is complete, the character display area Rc displays the specific appearance of character C corresponding to that character information dt.
[0090] If the collection of partial information dp for character information dt is complete, but the encounter event corresponding to that character information dt has not been completed, only the silhouette of character C corresponding to that character information dt will be displayed in the character display area Rc. In this case, the encounter execution button Bg3 described below will be displayed on the confirmation screen Mc (see Figure 11(c)). When the encounter execution button Bg3 is selected, the encounter event will start.
[0091] When the tracking setting button Bc2 on the confirmation screen Mc is selected, the character information dt displayed on the confirmation screen Mc is set as the tracking information dt, and the screen returns to the play screen MP. If the tracking information dt is already set, and the tracking setting button Bc2 on the confirmation screen Mc is selected, the tracking information dt will be changed to the character information dt displayed on the confirmation screen Mc. When the return button Bc3 on the confirmation screen Mc is selected, the tracking information dt is not set (changed), and the screen switches to the play screen MP. When the distribution status confirmation button Bc1 on the confirmation screen Mc is selected, the distribution status display screen Md, described below, is displayed instead of the confirmation screen Mc.
[0092] Figure 10(b) is a simulated example of the distribution status confirmation screen Md. As described above, each partial information dp possessed by a user can be granted (shared) to another user if that user is located in the user's shared area Rp, and the sharing conditions are met. The distribution status confirmation screen Md is displayed in a manner that allows the location where the sharing conditions for partial information dp have been met to be identified.
[0093] As described above, the distribution status confirmation screen Md is displayed when the distribution status confirmation button Bc1 on the confirmation screen Mc (see Figure 10(a)) is selected. The distribution status confirmation screen Md shows the regions where the sharing conditions of the partial information dp corresponding to the character information dt displayed on the confirmation screen Mc are met. Specifically, the distribution status screen Md consists of a display area Rd. The above display area Rd is displayed according to the map information described above and shows a map of the real space Sr. The above display area Rd displays, for example, the name of each region (prefecture name, city / ward / town / village name). The distribution location image Gc is also displayed in the display area Rd.
[0094] The distribution location image Gc on the distribution status confirmation screen Md is displayed in the display area Rd corresponding to the region where the sharing conditions of the partial information dp are met. Specifically, the distribution location image Gc for each region is displayed in a manner corresponding to the number of times the sharing conditions have been met in that region. For example, in this embodiment, the distribution location image Gc is displayed larger the more times the sharing conditions have been met in the region where the distribution location image Gc is displayed.
[0095] For example, Figure 10(b) assumes that the number of times the sharing condition is met is highest in "XX City". In this case, the distribution location image Gc corresponding to "XX City" will be displayed larger than the distribution location image Gc corresponding to other regions. In addition, the string "highest" will be displayed on the distribution location image Gc corresponding to "XX City".
[0096] The configuration of the distribution location image Gc is not limited to the examples above. For example, the distribution location image Gc corresponding to each region may be configured to display the number of times the sharing conditions have been met in that region. For example, the distribution location image Gc corresponding to a region where the sharing conditions have been met 100 times may be configured to display the string "100 times". Alternatively, the symbol "×" may be displayed at the locations where the sharing conditions have been met. In the above configurations, the symbol "×" will be displayed densely in regions where the sharing conditions have been met many times.
[0097] For example, the user can check the distribution status of partial information dp around their current location using the distribution status confirmation screen Md. If many of the sharing conditions are met around the user's current location, the character information dt corresponding to the partial information dp whose distribution status is being checked is set to the tracking information dt. Specifically, the distribution status confirmation screen Md displays a tracking setting button Bd1 and a return button Bd2. When the tracking setting button Bd1 is selected, the character information dt corresponding to the partial information dp whose distribution status is being checked is set to the tracking information dt, and the screen switches to the play screen Mp. On the other hand, when the return button Bd2 is selected, the display returns to the confirmation screen Mc.
[0098] Figure 11(a) is a schematic diagram of a specific example of the StreetPass Log display screen Ms. The StreetPass Log display screen Ms is displayed when the StreetPass Log display button Bp on the play screen Mp described above is selected. As shown in Figure 11(a), the StreetPass Log display screen Ms consists of log display areas Rs(1, 2…).
[0099] Each log display area Rs displays various information about other users who have met the sharing conditions for partial information dp. Specifically, the log display area Rs displays the name (account name) of the other user who has met the sharing conditions for partial information dp, the user's level, and the region and time when the sharing conditions were met with that user. A user's level increases as they progress through the game. Therefore, for example, users who possess many characters C tend to have higher levels. Note that the information displayed in the log display area Rs is not limited to the examples above.
[0100] On the encounter log display screen Ms, a log display area Rs corresponding to each instance in which a user has met the sharing conditions with another user is added and displayed. In addition, a share execution button Bs1 corresponding to that log display area Rs is displayed. When the share execution button Bs1 is selected, the sharing process is executed, and one of the partial information dp of other users whose sharing conditions were met at the event corresponding to the share execution button Bs1 is obtained. When the share execution button Bs1 is selected, the acquisition screen Mg, described below, is displayed instead of the encounter log display screen Ms.
[0101] Figure 11(b) is a simulated example of the acquisition screen Mg. The acquisition screen Mg is displayed when the log display area Rs (shared execution button Bs1) (see Figure 11(a)) is selected. In the acquisition screen Mg described above, partial information dp for which the sharing condition was met at the trigger corresponding to the selected log display area Rs is reported. For example, in the example in Figure 11(b), it is assumed that partial information dp2 is newly assigned among the partial information dp(1~4) corresponding to the character information dt. In this case, the acquisition screen Mg is displayed in a manner that reports that partial information dp2 has been newly assigned.
[0102] The specific example in Figure 11(b) assumes that partial information dp2 is newly assigned, and that all partial information dp except dp3 (dp1, dp2, dp4) of each partial information dp are collected. In other words, it assumes that partial information dp3 has not been collected. In this case, a user who has confirmed that partial information dp3 has not been collected can display the encounter log display screen Ms by selecting the return button Bg2. As shown in Figure 11(b), the acquisition screen Mg is provided with a display area Rg. If some of the partial information dp has not been collected, only the silhouette of character C corresponding to the character information dt of the acquisition screen Mg is displayed in the display area Rg.
[0103] Figure 11(c) is a simulated diagram of another specific example of the acquisition screen Mg. The specific example in Figure 11(c) assumes that partial information dp3 is newly added among the partial information dp(1~4) corresponding to the character information dt. Furthermore, it assumes that all partial information dp has been collected as a result of the addition of partial information dp3. In other words, it assumes that the rumor information Dx has been completed.
[0104] When all partial information dp has been collected, the acquisition screen Mg displays a return button Bg2 as well as an encounter execution button Bg3. When the encounter execution button Bg3 on the acquisition screen Mg is selected, an encounter event can be started to acquire character C corresponding to the character information dt (rumor information Dx) displayed on the acquisition screen Mg. Specifically, when the encounter execution button Bg3 is selected, the movement animation screen Mm described below is displayed, and then the encounter event starts.
[0105] Figure 11(d) is a simulated example of the movement animation screen Mm. As described above, the movement animation screen Mm is displayed when the encounter execution button Bg3 on the acquisition screen Mg is selected. As shown in Figure 11(d), the movement animation screen Mm has a display area Rm. The display area Rm displays a map of the real space Sr, similar to the distribution status screen Md described above. The display area Rm also displays the moving object Gj and object Gx. Object Gx is displayed at the encounter spot ves, which corresponds to the encounter spot res. The moving object Gj moves from the position corresponding to the user's position Pr at the time the encounter execution button Bg3 is selected to the encounter spot ves and is displayed. When the moving object Gj moves to the encounter spot ves, the encounter event starts.
[0106] According to this embodiment, by collecting each partial information dp of character information dt, it becomes possible to initiate an encounter event to acquire character C corresponding to the character information dt. Specifically, a user who has collected all the partial information dp can initiate an encounter event without actually moving to the encounter spot res.
[0107] Furthermore, if the log display area Rs (shared execution button Bs1) on the passing log screen Ms is selected and the acquisition screen Mg indicates that partial information dp has been shared, the log display area Rs will be hidden from the passing log screen Ms. Specifically, even if the return button Bg2 on the acquisition screen Mg is selected when all partial information dp has been acquired, the log display area Rs selected to display the acquisition screen Mg will be hidden. However, on the character information confirmation screen Mc after all partial information dp has been acquired, the encounter execution button Bg3 will be displayed instead of the tracking setting button Bc2 mentioned above. When the encounter execution button Bg3 on the confirmation screen Mc is selected, the movement animation screen Mm mentioned above will be displayed, and then the encounter event will begin.
[0108] Figure 12 is a diagram illustrating the configuration for generating processed content information Ca. As described above, in this embodiment, the system is configured to allow users to upload content information Cu (for example, images taken by the user). The content information Cu uploaded by the user is processed by the management device 10 (game operator) to generate processed content information Ca. The processed content information Ca, like the rumor information Dx (each part information dp1-4) described above, suggests the encounter spot res corresponding to the processed content information Ca.
[0109] Specifically, the user can upload content information Cu to the management device 10 by operating the terminal device 20 as appropriate (Sa in Figure 12). Furthermore, content information Cu can be uploaded via the upload screen Ma shown in Figure 14(a), which will be described later. Also, as will be explained in more detail later, when uploading content information Cu, the user must grant permission to the game operator to generate processed content information Ca from the content information Cu.
[0110] When uploading content information Cu, the terminal device 20 obtains the current user location Pr. The terminal device 20 also transmits the combination of user location Pr and content information Cu to the management device 10. The management device 10 stores the user location Pr and content information Cu in the storage means 12, associating them. As shown in Figure 12, each user's content information Cu is stored in the storage means 12. The number of content information Cu that can be stored in the management device 10 (storage means 12) is limited to a maximum of 10 per user.
[0111] The management device 10 performs a selection process (Sa2 in Figure 12). In this selection process, content information Cu to be processed into processed content information Ca is selected based on the user's location Pr of the content information Cu. For example, content information Cu whose user location Pr is close to the encounter spot res is selected in the selection process. The processed content information Ca generated from this content information Cu is highly likely to have been taken near the encounter spot res. Therefore, the encounter spot res may be suggested from the processed content information Ca.
[0112] In the above example, a configuration was adopted in which content information Cu is selected based on the user's location Pr when uploading the content information Cu. However, a configuration in which content information Cu is selected based on something other than the user's location Pr may also be adopted. For example, some content information Cu may contain metadata indicating the location where the content information Cu was generated (the location where the image was taken). In this case, a configuration may be adopted in which content information Cu to be used to generate processed content information Ca is selected based on the shooting location indicated by the metadata.
[0113] In this embodiment, the content information Cu to be processed into processed content information Ca is selected at the discretion of the game developer. Specifically, content information Cu that contains images of things that could serve as hints for encounter spots res (landscapes, buildings, local products, signs, etc.) is selected. However, the configuration may also be such that the content information Cu to be processed into processed content information Ca is automatically selected using, for example, image recognition technology.
[0114] When content information Cu to be processed into processed content information Ca is selected, the processing step (Sa3 in Figure 12) is executed. The processing step includes the game developer adding additional information Ga to content information Cu to generate processed content information Ca, and the user further processing (modifying) the processed content information Ca. The processed content information Ca generated by the processing step is shared with other users (Sa4) after obtaining permission from the user who provided the content information Cu used to create the processed content information Ca (Sa3 in Figure 12).
[0115] For example, the processed content information Ca is assigned (shared) to other users through the gacha lottery process described above. Specifically, the processed content information Ca in this embodiment may have multiple (e.g., 5) pieces of additional information Ga(1-5) attached to it. However, at the time it is assigned to other users, only additional information Ga1 of each of the additional information Ga(1-5) is attached to the processed content information Ca. On the other hand, the provider of the content information Cu is assigned processed content information Ca with all of the additional information Ga(1-5) attached.
[0116] A user who possesses processed content information Ca with only additional information Ga1 added can acquire the other additional information Ga(2-5) by moving to the shared area Rt (see Figure 7) of a user who possesses processed content information Ca with the other additional information Ga(2-5) added. In other words, each additional information Ga(2-5), like the partial information dp, is shared among users when the above-mentioned sharing conditions are met.
[0117] In this embodiment, the more additional information Ga is added to the processed content information Ca, the easier it is to predict the encounter spot res. Furthermore, if all the additional information Ga of the processed content information Ca is collected, the encounter event corresponding to that processed content information Ca can be started even if the user is not located at the encounter spot res (similar to the case where the rumor information Dx described above is completed).
[0118] Specifically, the additional information Ga1 in the processed content information Ca suggests the character C that can be obtained at the encounter spot res, similar to the character information dt mentioned above. For example, the additional information Ga1 "UFO" in the processed content information Ca shown in Figure 12 suggests the character C of "alien". In addition, each of the other additional information Ga(2~5) suggests the start conditions of the encounter event (location conditions, environmental conditions, behavioral conditions) (see Figure 13). The processed content information Ca may include a correction image Gb, as shown in Figure 12. This correction image Gb is added during the processing by the user who provided the content information Cu.
[0119] Figure 13 is a conceptual diagram of a specific example of a processing table. As described above, the content information Cu used to generate the processed content information Ca is determined based on the user location Pr of the content information Cu and the encounter spot res (encounter event) corresponding to the processed content information Ca generated from the content information Cu. A processing table is provided for each encounter spot res and defines the additional information Ga (1-5) to be added to the processed content information Ca corresponding to that encounter spot res.
[0120] As described above, the additional information Ga1 attached to the processed content information Ca is an image that suggests the character C that will be assigned in the encounter event corresponding to the processed content information Ca. Additionally, the additional information Ga2 is an image that suggests the environmental conditions of the encounter event. Similarly, the additional information Ga3 and Ga4 are images that suggest the location conditions of the encounter event. The additional information Ga5 is an image that suggests the action conditions of the encounter event.
[0121] For example, the specific example in Figure 13 assumes a processing table corresponding to an encounter event to which the character C, an "alien," is assigned. In this processing table, additional information Ga1 representing "UFO" is added when processing the content information Ca. Furthermore, the encounter event corresponding to the processing table shown in Figure 13 assumes the same environmental conditions as the encounter event explained using Figure 5 above, where the environmental condition is "the user is located at the encounter spot res around 12 o'clock," the location condition is "the user is located at the encounter spot res in the XX building in XX city," and the action condition is "the user stops at the encounter spot res for only about 5 minutes."
[0122] As described above, of the additional information Ga(2-5), additional information Ga2 suggests the environmental conditions of the encounter event. For example, in the specific example in Figure 13, additional information Ga2 representing "a clock showing the time 12 o'clock" is added to the processed content information Ca. Also, of the additional information Ga(2-5), additional information Ga3 suggests the location conditions of the encounter event. For example, in the specific example in Figure 13, additional information Ga3 representing "a local specialty of the area where the encounter spot res is located" is added to the processed content information Ca. Similarly, additional information Ga4 suggests the location conditions of the encounter event. For example, in the specific example in Figure 13, additional information Ga4 representing "a facility located at the encounter spot res" is added to the processed content information Ca. Additional information Ga5 suggests the action conditions of the encounter event. For example, in the specific example in Figure 13, additional information Ga5 representing the message "Wait 5 minutes" is added to the processed content information Ca. Note that the additional information Ga is not limited to the above examples and can be changed as appropriate.
[0123] As mentioned above, processed content information Ca is also assigned to users other than the provider of content information Cu. As shown in Figure 13, immediately after being assigned to another user, processed content information Ca will only have additional information Ga1, which suggests character C assigned in the encounter event, attached to it, out of the assigned information Ga(1-5). In addition, if a user possesses processed content information Ca, additional information Ga(2-5) that is not attached to that processed content information Ca may be shared by other users. Specifically, if another user is located in the shared area of a user who possesses processed content information Ca with any of the additional information Ga(2-5) attached, one of the additional information Ga(2-5) will be shared with each user.
[0124] Figure 14(a) is a simulated example of the upload screen Ma. The upload screen Ma is displayed when the upload button Bp4 (see Figure 9(a)) is selected. The user can upload each image (content information Cu) they possess via the upload screen Ma.
[0125] As shown in Figure 14(a), the upload screen Ma consists of selection buttons Ba1 (a11, a12…), a terms of service confirmation button Ba2, an upload execution button Ba3, and a return button Ba4. Furthermore, by appropriately operating the terminal device 20, the application program PGx can be granted permission to access images owned by the user (images stored on the terminal device 20, images stored on a so-called cloud server, etc.).
[0126] If the application program PGx is granted permission to access images owned by the user, a list of images (content information Cu) owned by the user will be displayed on the upload screen Ma. In the specific example shown in Figure 14(a), we assume that the upload screen Ma displays content information Cu1 and content information Cu2. By operating the terminal device 20 as appropriate (swiping operation), the content information Cu displayed on the upload screen Ma can be switched to other content information Cu owned by the user.
[0127] The selection buttons Ba1 (a11, a12…) on the upload screen Ma correspond to one of the content information Cu (1, 2…). Furthermore, the selection button Ba1 corresponding to a content information Cu is displayed to the right of that content information Cu. Each time a selection operation is performed, the selection button Ba1 switches between selected and unselected states. In the specific example shown in Figure 14(a), we assume that among the selection buttons Ba1 (a11, a12…), the selection button Ba11 corresponding to content information Cu1 is selected.
[0128] Selecting the Terms of Use confirmation button Ba2 will display the predetermined terms of use. These terms of use will specify, for example, the scope of use of the uploaded content information Cu. Specifically, the terms of use will state that the content information Cu uploaded by the user will be processed to generate processed content information Ca in location-based games. Furthermore, selecting the Upload execution button Ba3 will be deemed as agreeing to the terms of use and granting permission to generate processed content information Ca from the content information Cu, as stated in the terms of use. Note that the specific content of the terms of use is not limited to the examples above.
[0129] When the upload execution button Ba3 is selected, the content information Cu corresponding to the selected selection button Ba1 is uploaded to the management device 10. For example, in the specific example in Figure 14(a), content information Cu1 is uploaded. Even after the content information Cu has been uploaded, it will still be displayed on the upload screen Ma. Specifically, the uploaded content information Cu will display the string "Uploaded". When the return button Ba4 is selected, the content information Cu is not uploaded, and the system switches from the upload screen Ma to the play screen Mp.
[0130] Furthermore, a limit (for example, 10) may be set on the number of content information Cu that can be uploaded at one time. Additionally, the system may be configured to allow the deletion of uploaded content information Cu from the management device 10 (allowing the upload to be canceled). For example, the system may be configured to allow the user to cancel the upload of an uploaded content information Cu by selecting it on the upload screen Ma. Also, if the application program PGx does not have permission to access images owned by the user, the content information Cu cannot be uploaded. In such cases, the system may be configured to display a message in place of the content information Cu on the upload screen Ma to inform the user of this limitation.
[0131] Figure 14(b-1) shows a specific example of the sharing permission screen Mk. The sharing permission screen Mk is displayed on the terminal device 20 of the user who provided the content information Cu used to generate the processed content information Ca. As described above, the processed content information Ca is shared with other users. The sharing permission screen Mk is an image used to obtain permission in advance from the user who provided the content information Cu used to generate the processed content information Ca, in order to share the processed content information Ca with each user.
[0132] As shown in Figure 14(b-1), the sharing permission screen Mk displays the "Start Modification" button Bk1, the "Accept Sharing" button Bk2, the "Deny Sharing" button Bk3, and the "Switch Content" button Bk4. The sharing permission screen Mk also displays the processed content information Ca for which each user has permission to share. Users review the processed content information Ca displayed on the sharing permission screen Mk and decide whether or not they wish to share the processed content information Ca with other users.
[0133] Specifically, the processed content information Ca may have multiple pieces of additional information Ga(1-5) attached to it. Therefore, processed content information Ca can be shared in the following ways: processed content information Ca with only additional information Ga1 added, processed content information Ca with additional information Ga1 and additional information Ga2 added, processed content information Ca with additional information Ga1 and additional information Ga3 added, processed content information Ca with additional information Ga1 and additional information Ga4 added, processed content information Ca with additional information Ga1 and additional information Ga5 added, processed content information Ca with additional information Ga1 to additional information Ga3 added, processed content information Ca with additional information Ga1, additional information Ga2 and additional information Ga4 added, processed content information Ca with additional information Ga1, additional information Ga2 and additional information Ga5 added, processed content information Ca with additional information Ga1, additional information Ga3 and additional information Ga4 added, processed content information Ca with additional information Ga1, additional information Ga3 and additional information Ga5 added, and processed content information Ca with all additional information Ga added.
[0134] In this embodiment, a configuration is adopted that allows for prior confirmation of the processed content information Ca for all shareable patterns. Specifically, when the content switching button Bk4 on the sharing permission screen Mk is selected, the processed content information Ca for other patterns can be displayed on the sharing permission screen Mk. By selecting the content switching button Bk4, the user can prioritize the processing content information Ca for all shareable patterns.
[0135] Incidentally, some users may not permit the sharing of processed content information Ca created by the game operators as is, but may permit its sharing on the condition that some parts of the processed content information Ca are concealed. For example, permission may be granted to share the processed content information Ca on the condition that inconvenient information in the processed content information Ca is concealed.
[0136] Considering the above circumstances, this embodiment employs a configuration that allows users to further process (modify) the processed content information Ca created by the game operator. Specifically, when the modification start button Bk1 on the sharing permission screen Mk is selected, the modification screen Mf described below is displayed (see Figure 14(b-2) below). The user can modify the processed content information Ca created by the game operator via the modification screen Mf.
[0137] When the sharing permission button Bk2 on the sharing permission screen Mk is selected, the processed content information Ca displayed on the sharing permission screen Mk becomes shareable with other users. On the other hand, when the sharing rejection button Bk3 is selected, the processed content information Ca displayed on the sharing permission screen Mk is not shared with other users. The scope of users who can share the processed content information Ca may be configured so that the user who provided the content information Cu used to generate the processed content information Ca can select the users who can share the processed content information Ca. For example, consider a configuration where a user can send a friend request to another user, and if the user who receives the friend request accepts, that other user is set as a friend. In the above configuration, the scope of users who can share the processed content information Ca may be limited to the friends of the user who provided the content information Cu used to generate the processed content information Ca.
[0138] Figure 14(b-2) is a conceptual diagram of a specific example of the editing screen Mf. The editing screen Mf is displayed when the editing start button Bk1 on the sharing permission screen Mk described above is selected. As described above, the user can modify the processed content information Ca created by the game operator via the editing screen Mf.
[0139] Specifically, as shown in Figure 14(b-2), the editing screen Mf consists of a content switching button Bf1, a confirmation button Bf2, a return button Bf3, and a display area Rf. In addition, the editing screen Mf displays the processed content information Ca before permission for sharing is granted, similar to the sharing permission screen Mk described above. The processed content information Ca displayed on the editing screen Mf can be switched by selecting the content switching button Bf1, similar to the processed content information Ca displayed on the sharing permission screen Mk described above.
[0140] The display area Rf of the editing screen Mf displays the editing images Gb (1, 2, 3, 4…). In this embodiment, multiple editing images Gb are provided. The user can add any of the editing images Gb displayed in the display area Rf to the processed content information Ca. Specifically, Figure 14(b-2) shows edited images Gb1, Gb2, Gb3, and Gb4 extracted from the editing images Gb. The user places any of the editing images Gb displayed in the display area Rf at any position in the processed content information Ca (drag and drop). In the specific example in Figure 14(b-2), as indicated by the white arrow, we assume that editing image Gb1 is placed in the lower left part of the processed content information Ca.
[0141] After the edited content information Ca has been modified with the edited image Gb, selecting the confirm button Bf2 returns the display to the sharing permission screen Mk. The sharing permission screen Mk then displays the modified content information Ca (with the edited image Gb added) as modified by the user. Subsequently, selecting the sharing permission button Bk2 on the sharing permission screen Mk makes the modified content information Ca available for sharing with other users. On the other hand, selecting the return button Bf3 on the editing screen Mf does not reflect the changes to the modified content information Ca, and the display returns to the sharing permission screen Mk.
[0142] According to this embodiment, users have the advantage of being able to share processed content information Ca with other users while concealing information that is unfavorable to them. Note that the modification images Gb are not limited to the examples described above. Furthermore, a configuration may be adopted in which the number of types of modification images Gb that can be used to modify processed content information Ca changes (increases) when the user meets predetermined conditions. For example, a configuration may be adopted in which special modification images Gb become available when the user pays a fee. Alternatively, a configuration may be adopted in which the number of types of modification images Gb that can be added to content information Cu increases according to the user's game progress (e.g., the number of characters C collected, the user's level). Furthermore, an expiration date may be set for the processed content information Ca. For example, a configuration may be adopted in which the processed content information Ca is deleted from each user's terminal device 20 after a predetermined period (e.g., about one month) has elapsed since the processed content information Ca was first assigned to the user.
[0143] Figure 15(a) is a flowchart of the encounter processing performed by the management device 10. Encounter processing is performed, for example, in the encounter event described above. Encounter processing may be performed jointly by the terminal device 20 and the management device 10, or it may be performed by the terminal device 20 alone. The same applies to each step of the processing described later (normal processing, passing processing, generation processing).
[0144] As shown in Figure 15(a), in the encounter processing, the user who initiated the encounter event is assigned character C and rumor information Dx (S101). Specifically, when the user meets the conditions for initiating an encounter event, the management device 10 updates the "acquired characters" included in the user's game information. For example, character C assigned in the encounter event is added to "acquired characters". For the period after character C is added to "acquired characters", the specific appearance of character C is displayed on the confirmation screen Mc (character display area Rc) of the terminal device 20. In addition, when the user meets the conditions for initiating an encounter event, the management device 10 updates the "acquired information" included in the user's game information. For example, the character information dt and partial information dp(1~4) of rumor information Dx assigned in the encounter event are added to "acquired information".
[0145] Figure 15(b) is a flowchart of the pass-by processing. The management device 10 executes the pass-by processing when another user is located in the user's shared area Rt (see Figure 7 above). When the pass-by processing starts, the management device 10 determines whether the other user it has passed possesses character information dt that is common to the currently set tracking information dt (S201). If it is determined that the other user does not possess character information dt that is common to the tracking information dt (S201: No), the management device 10 terminates the pass-by processing.
[0146] On the other hand, if the management device 10 determines that another user possesses character information dt that is common to the tracking information dt (S201: Yes), the management device 10 randomly selects one of the partial information dp that corresponds to the character information dt from among the partial information dp possessed by that other user. After that, the management device 10 performs a sharing process (S203). In the above sharing process, the partial information dp of the other user selected in the previous step S203 is assigned to the user.
[0147] After performing the sharing process, the management device 10 terminates the passing-by process. It is also possible to configure the system so that the probability of selecting each partial information dp of the character information dt differs in step S202. For example, a configuration is preferred in which a partial information dp that makes it relatively easy to estimate the encounter spot res (e.g., partial information dp3 shown in Figure 5 above) is less likely to be selected (less likely to be shared) than other partial information dp.
[0148] Figure 15(c) is a flowchart of the normal processing. When the management device 10 starts the normal processing, it determines whether the upload button Bp4 has been selected on the terminal device 20 (S301). Specifically, when the upload button Bp4 is selected, the terminal device 20 requests various information from the management device 10 to display the upload screen Ma. Upon receiving this request, the management device 10 sends various information to the terminal device 20 to display the upload screen Ma, causing the upload screen Ma to be displayed (S302). For example, the management device 10 sends an instruction to the terminal device 20 to have the application program PGx acquire the content information Cu to be displayed on the upload screen Ma. Once the upload screen Ma is displayed, the management device 10 terminates the normal processing.
[0149] Figure 15(d) is a flowchart of the generation process. When the management device 10 starts the generation process, it executes a selection process (S401). In the selection process, as described above, one of the content information Cu uploaded by each user is selected based on the user location Pr and encounter spot res of the content information Cu. After executing the selection process, the management device 10 executes a processing process (S402). In the processing process, the content information Cu selected in the previous selection process is processed by the game developer. Specifically, additional information Ga (1-5) is added to the content information Cu, and processed content information Ca is generated.
[0150] After the processing is completed, the management device 10 performs a notification process (S403). In the notification process, a permission request notification is sent to the terminal device 20 of the user who uploaded (provided) the content information Cu selected in the previous selection process (used in the processing). Upon receiving the above permission request notification, the terminal device 20 becomes able to display the above-mentioned shared permission screen Mk. After the notification process is completed, the management device 10 determines whether the above-mentioned modification start button Bk1 (see Figure 14(b-1)) has been selected on the terminal device 20 side (S404). If it is determined that the modification start button Bk has been selected (S404: Yes), the management device 10 starts the reprocessing process (S405).
[0151] On the other hand, if the management device 10 determines that the correction start button Bk has not been selected (S404: No), it skips the reprocessing process and proceeds to step S406. When the reprocessing process is executed, various information for displaying the correction screen Mf (Figure 14(b-2)) is sent to the terminal device 20. Also, when the confirmation button Bf2 on the correction screen Mf is selected, the processed content information Ca corrected by the user is sent to the management device 10. After the reprocessing process is executed, the management device 10 determines whether or not the sharing permission button Bk2 has been selected (whether or not it has received notification to that effect from the terminal device 20) (S406).
[0152] If the management device 10 determines that the sharing permission button Bk2 has been selected (S406: Yes), it saves the processed content information Ca for which sharing has been permitted as processed content information Ca that can be shared with other users (S407), and terminates the generation process. Each processed content information Ca saved in step S407 is given to the provider of the content information Cu used to generate the processed content information Ca. In addition, the processed content information Ca is given to other users, for example, in the gacha lottery process.
[0153] If the management device 10 determines that the sharing permission button Bk2 has not been selected (S406: No), it determines whether the sharing rejection button Bk3 has been selected (S408). If the management device 10 determines that the sharing rejection button Bk3 has not been selected (i.e., it has not received a notification to that effect from the terminal device 20) (S408: No), it returns to step S404 described above. On the other hand, if the management device 10 determines that the sharing rejection button Bk3 has been selected (S408: Yes), it terminates the generation process.
[0154] <Variation> Each of the above forms can be modified in various ways. Specific examples of these modifications are given below. Two or more forms can be arbitrarily selected from the following examples and combined as appropriate.
[0155] (1) As a concrete example of generating processed content information Ca from content information Cu in each form, a configuration in which an image uploaded by the user is processed is described. However, the configuration for generating processed content information Ca from content information Cu is not limited to the above example. For example, a configuration in which a video (including sound information) can be uploaded as content information Cu is also possible. In the above configuration, processed content information Ca of the video is generated from the content information Cu of the video. As an example of the above configuration, a configuration is conceivable in which processed content information Ca is generated in which the above additional information is displayed for a predetermined period of time (for example, about 2 seconds) in the video uploaded by the user.
[0156] Furthermore, the system may be configured to play sounds (voices, sound effects) that suggest partial information dp for a predetermined period of time during the video uploaded by the user. For example, in the processed content information Ca that suggests the encounter spot res of character C shown in Figure 5 above, the system may be configured to generate voices that suggest partial information dp1, such as "around 12 o'clock", suggest partial information dp2, such as "XX city", suggest partial information dp3, such as "XX building", and suggest partial information dp4, such as "wait 5 minutes". Additionally, the uploadable content information Cu may include two or more still images, video, and sound information. In the above configurations, the additional information (still images, video, sound information) attached to the content information Cu may change depending on the type of content information Cu (still images, video, sound information).
[0157] (2) In each configuration, the encounter spot res may be configured to be movable. For example, the encounter spot res (an example of a specific location) may be changed after a predetermined period of time (for example, about one week) has elapsed. Alternatively, the new encounter spot res may be determined according to the current encounter spot res. Specific examples adopting each of the above configurations will be described in detail below.
[0158] Figure 16(a) illustrates a specific example of the above modification. In the example in Figure 16(a), one of the predetermined event spot res is set as an encounter spot res. Also, after about one week has passed since the encounter spot res was set, that encounter spot res moves to another event spot res. That is, the encounter spot res in which a specific character C can be obtained moves every week. However, the encounter spot res in which a predetermined character C (for example, a cryptid that lives in a specific location) can be obtained may not move.
[0159] Now, let's assume a configuration where new encounter spots (res) are determined independently of the current encounter spots (res). In this configuration, a remote location from the current encounter spot (res) could be determined as the new encounter spot (res). Consequently, a user who had identified the current encounter spot (res) and planned to visit it later might be unable to go to the new encounter spot (res), which could be inconvenient.
[0160] To mitigate the aforementioned inconveniences, the modified version employs a configuration in which the new encounter spot res is determined according to the current encounter spot res. Specifically, the distance from the current encounter spot res to the new encounter spot res (hereinafter referred to as "distance L") is set to be less than or equal to a predetermined distance. For example, the new encounter spot res is determined to be one of the event spot res within a range of approximately 10 kilometers from the current encounter spot res.
[0161] For example, consider the case in the specific example in Figure 16(a) where encounter spot resx moves to encounter spot resy. The encounter spot resx is an area that includes "○○ Museum" in "○○ City". On the other hand, the new encounter spot resy is an area that includes "×× Station" in "○○ City", which is the same as encounter spot resx. In the specific example in Figure 16(a) above, the target facility changes before and after the encounter spot res is changed (○○ Museum → ×× Station), but the area where encounter spot res is established (○○ City) remains the same. Therefore, the aforementioned inconvenience is mitigated.
[0162] In this modified example, while the partial information dp(2, 3) that suggests the location conditions of the encounter event may be changed before and after the encounter spot res is changed, the partial information dp1 that suggests environmental conditions and the partial information dp4 that suggests behavioral conditions remain unchanged. However, it is also possible to have a configuration in which either or both of the partial information dp1 that suggests the environmental conditions of the encounter event and the partial information dp4 that suggests behavioral conditions may be changed before and after the encounter spot res is changed. Furthermore, it is also possible to have a configuration in which the encounter spot res is changed so that the distance L is greater than or equal to a predetermined value.
[0163] (3) In each form, a configuration may be adopted that makes it easier for the user to be assigned a partial information dp (an example of specific information) that has been set by the user from among several types of partial information dp (an example of specific information). In addition, in the above embodiment, a configuration was adopted in which only the partial information dp corresponding to the character information dt that is being set (see Figure 10(a) above) can be assigned through the sharing process from among the partial information dp for acquiring various characters C (aliens, Tsuchinoko, etc.). Instead of the above configuration, a configuration may be adopted in which partial information dp can be shared by other users regardless of the corresponding character information dt.
[0164] Figure 16(b) is a diagram illustrating specific examples of modified configurations employing the above-described configurations. Figure 16(b) is a simulated diagram of a specific example of the tracking information setting screen Mx. By operating the terminal device 20 as appropriate, the user can receive various necessary information from the management device 10 and display the tracking information setting screen Mx. The user can also set tracking information via the tracking information setting screen Mx.
[0165] Specifically, as shown in Figure 16(b), the tracking information setting screen Mx consists of a character change button Bx1, a confirm button Bx2, and a return button Bx3. In addition, the tracking information setting screen Mx displays each sub-information dp corresponding to any of the character information dt. Specifically, it displays the sub-information dt (1-4) that the user possesses, from among the sub-information dt (1-4) that correspond to the character information dt. For example, in the specific example in Figure 16(b), it is assumed that the user possesses sub-information dp1, sub-information dp2, and sub-information dp4, but does not possess sub-information dp3.
[0166] When the character change button Bx1 is selected, each part of the information dp displayed on the tracking information setting screen Mx can be changed to the part of the information dp corresponding to other character information dt. The user can also select any one of the part of the information dp displayed on the tracking information setting screen Mx. In the specific example in Figure 16(b), we assume that part of the information dp (1, 2, 4) is selected. When the confirm button Bx2 on the tracking information setting screen Mx is selected, the selected part of the information dp is set as the tracking information. When the return button Bx3 is selected, the tracking information setting screen Mx switches to another screen.
[0167] In this modified version, if the sharing conditions are met, one of all the partial information dp held by the other user will be shared. Specifically, if the aforementioned tracking information is not set, one random partial information dp from all the partial information dp held by the other user will be shared. Furthermore, the probability of sharing is the same regardless of the partial information dp. For example, if the other user holds n (where n is a natural number) partial information dp, the probability of each partial information dp being shared is approximately 1 / n and is common to all of them.
[0168] During the period in which any of the partial information dp is set as tracking information, the partial information dp corresponding to the character information dt common to that tracking information may be preferentially selected from all the partial information dp held by other users. Specifically, this assumes that the partial information dp held by other users includes partial information dp common to tracking information. In this case, if the sharing conditions with that other user are met, one of the partial information dp corresponding to the character information dt common to tracking information will be shared randomly. That is, even if other users hold partial information dp corresponding to character information dt other than the character information dt corresponding to tracking information, sharing will be limited to one of the partial information dp corresponding to the character information dt common to tracking information.
[0169] On the other hand, if the partial information dp held by another user does not include any partial information dp common to the tracking information (including cases where the other user holds partial information dp other than the tracking information that corresponds to the character information dt common to the tracking information), then, as in the case where tracking information is not set, one random partial information dp from all the partial information dp held by that other user will be shared. According to the above modification, setting tracking information makes it easier to collect partial information dt corresponding to the character information dt common to that tracking information.
[0170] (4) In each form, the region in which partial information dp (additional information Ga) is shared is not limited to the shared region Rt described above. Figures 17(a-1) and 17(a-2) are diagrams illustrating specific examples of the region in which partial information dp (additional information Ga) is shared in modified examples.
[0171] The specific example in Figure 17(a-1) is a simulated diagram of a specific example of the base setting screen My. In this modified example, the user can set the "base Pw" via the base setting screen My. Specifically, one of the encounter spot res in which the user has previously progressed through an encounter event will be set as the base Pw. The base setting screen My displays a list of encounter spot res (e.g., XX City XX Station, XX City YY Station, YY City △ Park, etc.) in which the user has previously progressed through an encounter event. The user can select one of the encounter spot res displayed on the base setting screen My by operating the terminal device 20 as appropriate. The specific example in Figure 17(a-1) assumes that "XX City XX Station" is selected among the encounter spot res.
[0172] Furthermore, as shown in Figure 17(a-1), the map display button By1 is displayed on the base setting screen My. Each of the map display buttons By1 corresponds to one of the encounter spots res. When the map display button By1 is selected, a map screen showing the virtual space Sv around the encounter spot res corresponding to that map display button By1 is displayed.
[0173] As described above using Figure 9(a), the virtual space Sv is displayed on the play screen Mp, similar to the map screen displayed in response to the operation of the map display button By1. In the above configuration, a specific object displayed in the virtual space Sv on the play screen Mp may be omitted from the map screen. For example, as described above, if there is an encounter spot res near the user's location Pr, the object Gx is displayed in the virtual space Sv on the play screen Mp. In the above configuration, even if the encounter spot res is located near a candidate location of the base Pw (and assuming the user's location Pr is at that candidate location, even if the object Gx is displayed on the play screen Mp), it is preferable that the object Gx is not displayed on the map screen displayed in response to the operation of the map display button By1.
[0174] With the above configuration, the inconvenience of users being able to grasp information about the surrounding area of a candidate location Pw without having to move to that location is suppressed. However, the objects in the virtual space Sv of the map screen displayed in response to the operation of the map display button By1 and the objects in the virtual space Sv of the play screen Mp may have the same configuration.
[0175] Figure 17(a-2) is a diagram illustrating a specific example of the shared area (Rt, Ru) in the modified example. In this modified example, as in the forms described above, the shared area Rt is set to a predetermined distance from the user's position Pr. In the specific example in Figure 17(a-2), the shared area Rt for user Ua at user position Pra is shown. In addition to the shared area Rt described above, in this modified example, the shared area Ru is set to a predetermined distance from base Pw.
[0176] If another user is located in the shared area Ru, the partial information dp (additional information Ga) of that other user is shared with the user who set up the shared area Ru. For example, in the specific example in Figure 17(a-2), we assume that user Ub's user location Prb is located in user Ua's shared area Rt, and user Uc's user location Prc is located in user Ua's shared area Ru. In this case, user Ua will have access to the partial information dp (additional information Ga) of user Uc in addition to user Ub.
[0177] In the above modifications, the size of the shared area Rt and the size of the shared area Ru may be the same or different. For example, the shared area Rt may be wider than the shared area Ru, or the shared area Rt may be narrower than the shared area Ru. Also, in the above modifications, a configuration may be made in which locations other than the encounter spot res can be determined as base Pw. For example, a configuration may be made in which any location specified by the user can be determined as base Pw. Furthermore, a configuration may be made in which multiple base Pw can be set at the same time (in parallel). In the above configurations, it is preferable to set an upper limit on the number of base Pw that can be set at the same time.
[0178] (5) In each configuration, the shared area (Rt, Ru) may be configured to be variable. For example, consider a configuration in which user levels are set. The above user levels increase as the game progresses. In the above configuration, the shared area Rt may be configured to be wider the higher the user level. Also, in the modified examples shown in Figures 17(a-1) and 17(a-2) above, consider a configuration in which character levels are set for each character C. The above character levels increase as the game progresses. In the above configuration, the shared area Ru may be configured to be wider when the encounter spot res where character C was acquired is used as the base Pw, the higher the character level of character C.
[0179] (6) In each form, a configuration may be adopted that acquires the user's location information (user location Pr) in the real space Sr and generates processed content information Ca corresponding to said location information. Figure 17(b) is a diagram illustrating a specific example of a modified version that adopts the above configuration. In the above modified version, processed content information Ca corresponding to the user's location Pr is generated. Specifically, the form of the additional information Ga in the processed content information Ca changes according to the distance (distance L) from the user's location Pr to the encounter spot res.
[0180] In the above modification, we assume that additional information Ga1 (additional information Ga suggesting character C) among the additional information Ga includes additional information Ga11 and additional information Ga12. Also, as the distance L to the encounter spot res approaches, the processed content information Ca displayed on the terminal device 20 changes in the order of processed content information Ca1, processed content information Ca2, and processed content information Ca3.
[0181] For example, if the distance L to the encounter spot res is greater than approximately 10 kilometers (L > 10 kilometers), processed content information Ca1 is displayed. As shown in Figure 17(b), processed content information Ca1 displays only the additional information Ga11 (Ga11, Ga12) from the additional information Ga11. Also, if the distance L is greater than or equal to approximately 1 kilometer and less than or equal to approximately 10 kilometers (1 kilometer ≤ L ≤ 10 kilometers), processed content information Ca2 is displayed. Processed content information Ca2 displays additional information Ga11 in addition to additional information Ga12. If the distance L is less than approximately 1 kilometer (L < kilometers), processed content information Ca3 is displayed.
[0182] In addition to the additional information Ga11, additional information Ga12 is displayed in the processed content information Ca3. Furthermore, in the processed content information Ca3, additional information Ga12 is displayed in an enlarged view compared to processed content information Ca1 and processed content information Ca2. According to the above modification, the distance L to the encounter spot res is suggested by the form of additional information Ga1. In this modification, as in the other forms, other additional information Ga(2~5) is added to the processed content information Ca.
[0183] (7) In each form, the encounter event may be configured such that character C and rumor information Dx are awarded if predetermined conditions are met. For example, consider a configuration in which an encounter event starts with a battle against character C corresponding to that encounter event (hereinafter referred to as "enemy character C"). In the above configuration, the enemy character C and rumor information Dx may be awarded on the condition that the battle against enemy character C is won.
[0184] The content of the battles in the encounter events described above can be changed as appropriate. For example, a user can have their own character C (hereinafter referred to as "ally character C") battle an enemy character C. If ally character C defeats enemy character C, that enemy character C becomes ally character C. The difficulty of winning the battle (the strength of that enemy character C) may be changed for each enemy character C. In the above configuration, for example, information indicating the strength of the enemy character C to be battled in the encounter event corresponding to the display area Rl (see Figure 9(b)) may be displayed in each display area Rl of the rumor list screen Ml described above.
[0185] (8) In each configuration, an upper limit may be set on the number of partial information dp (additional information Ga) shared by other users during a specific period. For example, the configuration may be set so that the upper limit on the number of partial information dp (additional information Ga) shared by other users during a period of approximately 24 hours is "10".
[0186] (9) In each configuration, the information shared by each user is not limited to the examples described above. For example, the configuration may allow a user who possesses character information dt to share that character information dt with other users.
[0187] (10) In the above embodiment, an example was described in which processed content information Ca is generated from content information Cu (images taken outside the game) generated by an application program (such as a camera app) separate from the location-based game application program PGx. However, a configuration may be adopted in which processed content information Ca is generated from content information Cu (images taken inside the game) generated by the functions of the location-based game application program PGx itself. Alternatively, a configuration may be adopted in which processed content information Ca can be generated from both content information Cu generated outside the game and content information Cu generated inside the game. Specifically, similar to the above embodiment, a configuration is assumed in which content information Cu taken outside the game can be uploaded via the upload screen Ma (see Figure 14(a)). In the above configuration, a shooting mode switching button may be provided on the upload screen Ma. When the shooting mode switching button is selected, the system switches to shooting mode. In shooting mode, the camera of the terminal device 20 can take pictures, and the captured images are added to the upload screen Ma as uploadable content information Cu.
[0188] (11) In each form, the system may be configured so that a user can possess multiple processed content Ca. Alternatively, the system may be configured so that a reward is given to a user when they collect a predetermined combination of processed content Ca. For example, consider a configuration in which multiple processed content Ca are generated corresponding to one encounter spot res. In the above configuration, if multiple processed content Ca corresponding to a common encounter spot res are collected, the encounter event corresponding to that encounter spot res can be started (an example of a reward). Alternatively, one piece of content information Cu may be split into two, with partial processed content information Cb1 being generated from one of the split pieces of content information Cu, and partial processed content information Cb2 being generated from the other. In the above configuration, it is difficult to infer the encounter spot res from only the partial processed content information Cb1 (or partial processed content information Cb2). On the other hand, by combining the partial processed content information Cb1 and the partial processed content information Cb2, it becomes easier to infer the encounter spot res.
[0189] (12) In each form, the additional information may be changed according to the time elapsed since the additional information was added to the content information Cu. For example, immediately after the processed content information Ca is provided to the user, the processed content information Ca1 shown in Figure 17(b) above may be displayed, and then, after a predetermined period of time (for example, about one week), the processed content information Ca2 may be displayed instead of the processed content Ca1. Furthermore, after the aforementioned period of time has elapsed since the processed content information Ca2 was displayed, the processed content information Ca3 may be displayed instead of the processed content Ca2. Furthermore, after the aforementioned period of time has elapsed since the processed content information Ca3 was displayed, the validity period of the processed content information Ca may expire.
[0190] (13) In each form, the configuration may allow for setting in-game currency in the content information Cu that has been authorized to be used when generating processed content information Ca. For example, if processed content information Ca is generated using content information Cu, the configuration may allow the in-game currency set in said content information Cu to be granted to the user who provided said content information Cu. Alternatively, the configuration may allow virtual currency to be granted to the user who provided the content information Cu each time the processed content information Ca is distributed to another user. Alternatively, the configuration may allow virtual currency to be granted to the other user each time the processed content information Ca is distributed to another user.
[0191] (14) In each form, the rumor information Dx may be configured to be tradable as a digital asset that cannot be replaced by blockchain technology. For example, when the rumor information Dx is completed, it may be configured to be converted (minted) into an NFT (Non-Fungible Token). However, even before the rumor information Dx is completed, it may be configured to be possible to convert a combination of character information dt and partial information dp (part) into an NFT. Furthermore, it may be configured to be possible to convert character information dt alone into an NFT, or to convert partial information dp alone into an NFT. It may also be possible to import NFTs (rumor information Dx) purchased from other users into the game.
[0192] (15) In each embodiment, a specific example of the present invention applied to location-based games has been described. However, the present invention may also be applied to applications other than location-based games. For example, the present invention can be applied to a map service that helps users reach predetermined locations (e.g., stores), a service that measures a user's movement history (number of steps taken, distance traveled) to manage the user's health, a matching service for matching users, and a pedometer point service that awards points according to the number of steps taken by the user.
[0193] The embodiments described above may be combined in any way, replaced with other configurations, parts of the configuration may be deleted, or parts of the configuration may be modified. Furthermore, any publicly known technology at the time of filing that is not described herein may be adopted as appropriate.
[0194] <Note: Summary of the operation and effects of the embodiment> <First aspect> The program (PGy) in this embodiment provides the user with specific information (character information dt, partial information dp) related to a specific location (encounter spot res) in real space (Sr), and then causes the computer to function as a control means (11) that enables the provision of said specific information to other users when predetermined sharing conditions are met between the user and other users. According to this embodiment, the entertainment value of the service is improved.
[0195] <Second aspect> In this embodiment, the program is composed of multiple sub-informations (dp1-4) as specific information, and the control means enables the initiation of an event (encounter event) related to a specific location when the user has collected multiple sub-informations. According to this embodiment, the entertainment value of the service is improved.
[0196] <Third aspect> In this embodiment, the program allows the control means to initiate an event related to a specific location even if the user has not acquired specific information, when the user is located at that location, and to initiate an event related to that specific location even if the user has acquired specific information, when the user is not located at that location (see Figure 11(d)). This embodiment improves the entertainment value of the service.
[0197] <Fourth and fifth manifestations> In the fourth embodiment of the program, the control means changes a specific position after a predetermined period of time has elapsed. In the fifth embodiment of the program, the control means can determine a new specific position according to the current specific position (see Figure 16(a)). This embodiment improves the entertainment value of the service.
[0198] <Sixth aspect> In this embodiment, specific information is provided for each of several types of specific locations (encounter spots res), and the control means makes it easier for the user to receive specific information set by the user from among the several types of specific information (see Figure 16(b)). According to this embodiment, the entertainment value of the service is improved.
[0199] <Seventh aspect> In this embodiment, the program's control means can set a predetermined location (base Pw) that is different from the user's current location in real space, and can assign specific information that has been assigned to other users within a predetermined range (Ru) from the predetermined location to the user who set the predetermined location (see Figures 17(a-1) and 17(a-2)). This embodiment improves the entertainment value of the service.
[0200] <Eighth aspect> The information processing system (1) in this embodiment provides a user with specific information related to a specific location in real space, and then, if predetermined sharing conditions are met between the user and another user, it includes control means for providing the other user with the specific information. According to this embodiment, the same effects as in the first embodiment described above can be achieved.
[0201] Furthermore, the problem-solving means configured in the above-mentioned program (for example, the configurations described in the appendix) can be adapted as appropriate for use in devices, systems, methods, information recording media, etc. [Explanation of Symbols]
[0202] 1... Information processing system, 10... Management device, 11... Control means, 12... Storage means, 20... Terminal device.
Claims
1. The system provides users with specific information related to a particular location in real space, and then, if predetermined sharing conditions are met between that user and other users, that specific information can be shared with those other users. A program that enables a computer to function as a control mechanism.
2. The aforementioned specific information is composed of multiple sub-informations, The control means enables the initiation of an event associated with a specific location when the user has collected multiple pieces of information. The program according to claim 1.
3. The control means is If a user is located at the aforementioned specific location, even if the user has not obtained the aforementioned specific information, it is possible to initiate an event related to that specific location. If a user has obtained the aforementioned specific information, even if the user is not physically located at the aforementioned specific location, it will be possible to initiate an event related to that specific location. The program according to claim 1.
4. The control means changes the specific position after a predetermined period of time has elapsed. The program according to claim 1.
5. The control means can determine the new specific position according to the current specific position. The program according to claim 1.
6. The aforementioned specific information is provided for each of the multiple types of the aforementioned specific locations. The control means makes it easier for the user to receive the specific information set by the user from among the multiple types of specific information. The program according to claim 1.
7. The control means can set a predetermined location that is different from the user's current location in real space, and can assign the specific information that has been assigned to other users within a predetermined range from the predetermined location to the user who set the predetermined location. The program according to claim 1.
8. The system provides a user with specific information related to a particular location in real space, and then, if predetermined sharing conditions are met between that user and another user, that specific information is shared with that other user. An information processing system equipped with control means.