JP7802641B2 - Programs and Systems - Google Patents

Description

Article 30, Paragraph 2 of the Patent Act applies. ▲1▼ March 4, 2022 Announced via the website address "https://youtube.com/watch?v=SaOukMKLDEY" ▲2▼ March 5, 2022 Announced via the website address "https://prtimes.jp/main/html/rd/p/000001124.000004473.html" ▲3▼ March 30, 2022 Announced via the website address "https://youtube.com/watch?v=1hUwsFyAWWw" ▲4▼ March 31, 2022 Announcement via the website address "https://twitter.com/colopl_quiz/status/1509429329692082180"

The present invention relates to a program and a system.

In recent years, gaming systems have become known that allow users to play games online, for example.

It is expected that a variety of users will play games in such game systems, and the operators of the game systems hope that many users will continue to play the game.

However, in games that feature multiple characters, players may be given priority over characters that offer an advantage in progressing through the game, meaning they may not be able to use their preferred character. Being unable to use your preferred character in this way can be uninteresting and may reduce your motivation to continue playing the game.

“[Dragon Quest Walk] List of Appearance Equipment and How to Change It [DQ Walk]”, [online], [Retrieved September 20, 2022], Internet <URL: https://gamewith.jp/dq-walk/article/show/174130>

The object of the present invention is therefore to provide a program and system that can increase the entertainment value of games.

According to one aspect of the present invention, a program is provided that causes a computer to function as a display means for displaying a first character having a first ability value as an ability value in a game, and a second character having a second ability value different from the first ability value and having a different appearance from the first character, and as a change means for changing the appearance of the first character to the appearance of the second character without changing the ability value of the first character from the first ability value, or for changing the ability value of the first character to the second ability value of the second character without changing the appearance of the first character, wherein the game includes a quest for which a predetermined clearing condition is set, the change means changes the appearance of the first character used by the user in the quest to the appearance of the second character, and the display means displays the first character used by the user in the quest in the appearance of the first character on a result screen showing the result of the quest .

This invention makes it possible to improve the entertainment value of games.

1 is a diagram showing an example of the configuration of a game system according to an embodiment of the present invention. FIG. 2 is a diagram showing an example of the hardware configuration of a user terminal. FIG. 2 is a diagram illustrating an example of a hardware configuration of a server device. FIG. 2 is a diagram showing an example of the functional configuration of a user terminal. FIG. 2 is a diagram illustrating an example of the functional configuration of a server device. FIG. 10 is a diagram showing an example of a game part. 10 is a flowchart showing an example of a procedure for deck organization processing. FIG. 4 is a diagram showing an example of the data structure of deck information. FIG. 10 is a diagram showing an example of a deck organization screen. 10 is a flowchart showing an example of a procedure for skin editing processing. FIG. 10 is a diagram showing an example of a skin editing screen. FIG. 10 is a diagram showing an example of a sortie preparation screen. FIG. 10 is a diagram showing an example of a deck selection dialog. FIG. 10 is a diagram showing an example of a skin selection dialog. 10 is a flowchart showing an example of a procedure for a skin application process. 10A to 10C are diagrams showing a specific example of skin application processing. FIG. 10 is a diagram showing another specific example of the skin application process. FIG. 10 is a diagram showing an example of a battle screen. FIG. 10 is a diagram showing an example of a quest result screen.

Hereinafter, an embodiment of the present invention will be described with reference to the drawings.
1 is a diagram showing an example of the configuration of a game system according to this embodiment. The game system 1 shown in Fig. 1 is configured to enable users to play games online, for example, and includes a user terminal 10 and a server device 20.

The user terminal 10 is, for example, an electronic device used by a user. In this embodiment, the user terminal 10 is assumed to be, for example, a smartphone, but the user terminal 10 may also be other electronic devices such as a tablet terminal or a personal computer.

The server device 20 is communicatively connected to the user terminal 10 via a network 30 such as the Internet.

Note that although only one user terminal 10 is shown in Figure 1, the game system 1 is assumed to include multiple user terminals 10 used by multiple users (i.e., multiple users who can play games provided by the game system 1) who have been pre-registered in the game system 1 (server device 20).

Figure 2 is a diagram showing an example of the hardware configuration of the user terminal 10 shown in Figure 1. Here, we will refer to Figure 2 to explain the hardware configuration when the user terminal 10 is a smartphone.

As shown in FIG. 2, the user terminal 10 includes a non-volatile memory 11, a CPU 12, a main memory 13, a wireless communication device 14, a display 15, and a touch panel 16.

Non-volatile memory 11 stores various programs. The various programs stored in non-volatile memory 11 include, for example, an operating system (OS) and various applications that run on the user terminal 10.

The CPU 12 is a processor that controls the operation of various components within the user terminal 10, and executes various programs stored in the non-volatile memory 11, for example. The CPU 12 may be a single processor, or may be composed of multiple processors. The various programs stored in the non-volatile memory 11 are loaded from the non-volatile memory 11 to the main memory 13 and executed by the CPU 12, and the programs (application programs) executed by the CPU 12 include a game program 13A for operating as a user terminal in the game system 1.

The wireless communication device 14 is a device for performing wireless communication with an external device (e.g., a server device 20, etc.).

The display 15 is a display device for displaying various screens related to the games provided by the game system 1.

The touch panel 16 is an input device that detects the position touched by the user's fingertip, and is arranged, for example, superimposed on the front of the display 15.

The display 15 and touch panel 16 form a touchscreen display, which can detect various user operations on the screen.

Figure 3 is a diagram showing an example of the hardware configuration of the server device 20 shown in Figure 1. As shown in Figure 3, the server device 20 includes a non-volatile memory 21, a CPU 22, a main memory 23, a wireless communication device 24, etc.

Non-volatile memory 21 stores various programs. The various programs stored in non-volatile memory 21 include, for example, an operating system (OS) and various application programs that run on server device 20.

The CPU 22 is a processor for controlling the operation of various components within the server device 20, and executes various programs stored in the non-volatile memory 21, for example. The CPU 22 may be a single processor, or may be composed of multiple processors. The various programs stored in the non-volatile memory 21 are loaded from the non-volatile memory 21 to the main memory 23 and executed by the CPU 22, and the programs (application programs) executed by the CPU 22 include a game program 23A for operating as a server device in the game system 1.

The wireless communication device 24 is a device for performing wireless communication with an external device (e.g., a user terminal 10, etc.).

The functional configuration of the game system 1 according to this embodiment will be described below. The game system 1 according to this embodiment has the function of providing a game play environment in which a user can play a game, for example, by having the user terminal 10 and the server device 20 operate in cooperation. Note that in this embodiment, the game play environment refers to the environment necessary to play a game in a broad sense, and includes various elements related to the game. An example of a game play environment is a game space, etc.

Figure 4 is a diagram showing an example of the functional configuration of the user terminal 10. As shown in Figure 4, the user terminal 10 includes an operation reception unit 101, a control unit 102, a display processing unit 103, and a storage unit 104.

The operation reception unit 101, control unit 102, and display processing unit 103 shown in FIG. 4 are functional units realized, for example, by the CPU 12 (the computer of the user terminal 10) of the user terminal 10 executing the above-mentioned game program 13A (i.e., software). This game program 13A may be downloaded to the user terminal 10 via the network 30, for example, or may be distributed by pre-storing it on a computer-readable storage medium.

Furthermore, the storage unit 104 shown in Figure 4 is realized by the non-volatile memory 11 shown in Figure 2 or another storage device (not shown), etc.

The operation reception unit 101 receives user operations (instructions) for playing a game in the game play environment provided by the game system 1. As described above, if the user terminal 10 is a smartphone, the operations received by the operation reception unit 101 include operations of touching a fingertip to the touch panel 16 (touch screen display) provided on the user terminal 10 (for example, tapping, dragging, flicking, swiping, etc.).

The control unit 102 interprets the operations received by the operation reception unit 101 and executes control to progress the game being played in the gameplay environment.

The display processing unit 103 executes processing to display the above-described game play environment and screens (images) according to the progress of the game, in accordance with control by the control unit 102. The user can perform operations to play the game while referring to the screens displayed by the display processing unit 103.

The storage unit 104 stores, for example, game data and user data. Game data includes, for example, data for defining the game play environment and setting data related to the game, and is data common to all users who play games implemented in the game system 1. On the other hand, user data is data managed for each user account.

Figure 5 is a diagram showing an example of the functional configuration of the server device 20. As shown in Figure 5, the server device 20 includes a storage unit 201, a data management unit 202, a control unit 203, and the like.

Note that the storage unit 201 shown in Figure 5 is realized by the non-volatile memory 21 shown in Figure 3 or another storage device (not shown).

Furthermore, the data management unit 202 and control unit 203 shown in FIG. 5 are functional units realized, for example, by the CPU 22 (the computer of the server device 20) of the server device 20 executing the above-mentioned game program 23A (i.e., software). This game program 23A may be downloaded to the server device 20 via the network 30, for example, or may be distributed by pre-storing it on a computer-readable storage medium.

The storage unit 201 stores game data similar to the game data stored in the storage unit 104 included in the user terminal 10 described above. The storage unit 201 also stores user data for each user who has been pre-registered in the game system 1 (server device 20).

The data management unit 202 manages the game data and user data stored in the storage unit 201. Specifically, the data management unit 202 performs processes such as adding, updating, and deleting game data and user data.

As mentioned above, game data and user data are stored in the storage unit 104 included in the user terminal 10, and this game data and user data are transmitted from the data management unit 202 (server device 20) to the user terminal 10 and stored in the storage unit 104. As mentioned above, game data is common to all users and is therefore transmitted to the user terminals of all users pre-registered in the game system 1, but user data is transmitted only to the user terminal used by the user corresponding to that user data.

The control unit 203 controls the processing required to realize the game played in the game play environment provided by the game system 1.

Here, an overview of the game realized in the game system 1 according to this embodiment will be described.
As an example, a game implemented in the game system 1 according to this embodiment has a format in which a user is presented with a plurality of options and the game progresses according to the option selected by the user. The game implemented in the game system 1 is not limited to a specific genre and may be a game of any genre as long as it has the above format. Examples of games of any genre include sports games based on sports such as tennis, table tennis, dodgeball, baseball, soccer, and hockey, puzzle games, quiz games, RPGs, quiz RPGs, adventure games, shooting games, simulation games, training games, and action games.

Furthermore, game system 1 is not limited to a specific play style, and may be a system for executing games of any play style. Games of any play style include, for example, single-player games played by a single user and multiplayer games played by multiple users. Multiplayer games played by multiple users include, for example, cooperative games in which multiple users cooperate and competitive games in which multiple users compete against each other.

In this embodiment, as an example, it is assumed that the game implemented in the game system 1 is a quiz RPG in which players take on quests using a single deck composed of one or more ally characters, damage enemy characters by answering quizzes correctly, and aim to clear the quest by defeating the enemy character.

Figure 6 is a diagram illustrating the game parts included in the quiz RPG of this embodiment. As shown in Figure 6, the quiz RPG of this embodiment includes, by way of example, a deck formation part P1, a sortie preparation part P2, a battle part P3, a result part P4, and a main part P5.

Deck organization part P1 is the part where a deck to be used in a quest is organized. In this deck organization part P1, the user selects one or more characters from those they own and organizes a deck composed of the selected characters. As will be described in more detail below, deck organization part P1 may also include a skin organization part P11 where a deck skin is organized that changes the appearance or status of an ally character organized in the deck to the appearance or status of another character. Status is data that indicates a character's ability values, and examples include hit points (HP), attack power, cost, skills, attributes, etc.

The sortie preparation part P2 is a part in which the user makes various settings for challenging a quest, for example, between the time the user completes deck organization in the deck organization part P1 and the time they move on to playing the quest. The sortie preparation part P2 may also include a part that allows the user to select a quest to play from multiple quests. The sortie preparation part P2 may also include a part that allows the user to select a deck to use for the quest. The sortie preparation part P2 may also include a part that allows the user to select a deck skin to apply to the deck to use for the quest. The sortie preparation part P2 may also include a part that allows the user to select whether another user's character will participate in the quest as a helper, or a part that allows the user to select another user's character to participate as the helper.

The battle part P3 is a part that corresponds to a quest. More specifically, the battle part P3 is a part in which one or more battles are conducted in which one or more ally characters organized in the deck fight an enemy character using the deck selected by the user in the sortie preparation part P2. In the quiz RPG of this embodiment, a quiz is conducted in each battle with an enemy character, and each battle progresses depending on the user's play results for the quiz. More specifically, in the quiz RPG of this embodiment, the actions of the ally characters organized in the deck are determined depending on the correctness or incorrectness of the user's answers to the quiz questions asked during the battle with the enemy character, and the time it took to answer them, and each battle progresses by having the ally characters perform a predetermined action. Examples of predetermined actions include, for example, an attack action that inflicts damage on an enemy character, or an action that activates an ally character's skill.

Result Part P4 is the part to which the game transitions from Battle Part P3 when the conditions for ending Battle Part P3 are met, and it presents the user with the results of Battle Part P3 (e.g., whether the quest was successful), as well as the items and experience points acquired in Battle Part P3. End conditions for Battle Part P3 include allied characters defeating all enemy characters that appear in the quest (i.e., clearing the quest), all ally characters being defeated by enemy characters that appear in the quest (i.e., failing the quest), or the user retiring (withdrawing midway), etc.

The main part P5 includes parts related to game progression other than the deck organization part P1, the sortie preparation part P2, the battle part P3, and the result part P4. The main part P5 may include a part that presents the user with video related to the game scenario (story). The main part P5 may include a part that presents the user with a screen for changing game settings. The main part P5 may include a part related to gacha for acquiring characters.

Note that the quiz RPG in this embodiment may include game parts other than the various game parts shown in Figure 6.

Here, the characters appearing in the quiz RPG of this embodiment will be described. In the quiz RPG of this embodiment, characters are provided to the user as digital data representing cards. The form in which this digital data is provided to the user is not particularly limited. For example, the digital data may be provided to the user by being transmitted from the server device 20 to the user terminal 10 via the network 30. Alternatively, the digital data may be provided to the user on a physical medium on which a code, password, barcode, QR code ^TM , or the like is printed. In this case, the digital data printed on the physical medium is read by the user terminal 10, and the character associated with the digital data is made available in the game executed by the user terminal 10. Information regarding the character owned by the user is stored in the server device 20 (storage unit 201) as the user data of the user.

The many characters that appear in quiz RPGs are each assigned a different appearance, voice, and status. As mentioned above, one of the elements included in status is attribute. Attributes are elements that determine compatibility with enemy characters, and include, for example, fire attribute, water attribute, lightning attribute, and dark attribute. To explain in more detail, the fire attribute is stronger than the lightning attribute but weaker than the water attribute, the water attribute is stronger than the fire attribute and weaker than the lightning attribute, and the lightning attribute is stronger than the water attribute and weaker than the fire attribute. Furthermore, the light attribute is stronger than the dark attribute, and the dark attribute is stronger than the light attribute.

For example, when attempting a quest featuring many water-attribute enemy characters, the user can progress through the quest with an advantage by including many lightning-attribute ally characters, which are stronger than water-attribute characters, in their deck. In this way, attributes are a very important factor in progressing through this game.

By the way, users often want to be able to organize and use their favorite characters (for example, characters whose appearance or voice they like) in their decks. However, as mentioned above, in order to progress through quests advantageously, it is important to organize a deck taking into account attributes and other stats, and as a result, users may not be able to organize their favorite characters in their decks. Not being able to organize their favorite characters in their decks and play the game may lead to a decrease in the user's motivation for the game. Furthermore, an environment in which only a few strong characters are used and other characters are not used much reduces the interest of the game.

Therefore, the game system 1 according to this embodiment proposes a mechanism that suppresses the decline in motivation described above and increases the enjoyment of the game. Specifically, by implementing a deck skin function that changes the behavior or status of an ally character organized in a deck to that of another character, the decrease in motivation described above is suppressed while increasing the enjoyment of the game.

Note that changing a character's appearance to that of another character includes changing the display appearance (appearance) identifiable as the character to that of the other character, and changing the voice identifiable as the character to that of the other character. Also, when a character's appearance is changed to that of another character, only the appearance of the character may be changed to that of the other character, only the voice of the character may be changed to that of the other character, or both the appearance and voice of the character may be changed to that of the other character.

Below, we will first explain the deck compilation process in a quiz RPG implemented in the game system 1 according to this embodiment, with reference to Figure 7. Figure 7 is a flowchart showing an example of the steps of the deck compilation process executed by the user terminal 10.

First, the operation reception unit 101 receives a user operation to transition to the deck organization part P1 on the game screen (hereinafter referred to as the deck organization start operation) (step S1). The deck organization start operation includes various operations for transitioning to the deck organization screen described below, such as tapping a tab on the home screen (not shown) to transition to the deck organization screen, or tapping a button in the deck selection dialog described below to transition to the deck organization screen.

When the operation reception unit 101 receives the deck organization start operation, the control unit 102 sends a deck organization start request to the server device 20 (step S2). The deck organization start request includes, for example, a user ID for identifying the user using the user terminal 10.

When the server device 20 receives a deck organization start request sent from the user terminal 10, it reads from the storage unit 201 the user data associated with the user ID included in the received deck organization start request, and transmits the user data to the user terminal 10 of the user identified by the user ID. As a result, the user terminal 10 (control unit 102) acquires the user data from the server device 20 (step S3). The user data includes, for example, deck information and possessed character information.

An example of the data structure of deck information will now be described with reference to FIG.
Deck information is information that defines a deck composed of characters owned by a user. As shown in FIG. 8 , the deck information includes one or more slots. The one or more slots are used to associate characters to be organized into the deck. The one or more slots may be referred to as the first slot, second slot, third slot, fourth slot, and fifth slot, from left to right in the figure. For example, in the deck information shown in FIG. 8 , characters A to E are associated with slots 1 to 5, respectively. Note that associating a character with a specific slot includes, for example, associating a character ID with the specific slot. A character ID is information used to identify a character. While FIG. 8 shows a case in which the deck information includes five slots, the number of slots included in the deck information is not limited to this, and the deck information may include any number of slots as long as the number is an integer greater than or equal to one.

Returning to the explanation of Figure 7, the display processing unit 103, under the control of the control unit 102, displays the deck organization screen 400 based on the user data acquired in the processing of step S3 on the display 15 of the user terminal 10 (step S4).

Here, the deck organization screen 400 will be described with reference to FIG.
As shown in FIG. 9, the deck organization screen 400 includes a deck name display area 401, a deck organization display area 402, a possessed character display area 403, a decision button 404, various tabs 405, and the like.

The name of the deck is displayed in the deck name display area 401. In the deck organization screen 400 shown in Figure 9, the name of the deck is displayed as "Deck 1." The deck name displayed in the deck name display area 401 can be changed by the user at will.

The deck composition display area 402 displays one or more characters that make up the deck. More specifically, the deck composition display area 402 displays one or more characters associated with one or more slots included in the deck information. Each of the one or more characters displayed in the deck composition display area 402 includes an attribute icon 402a indicating an attribute, which is one of the character's statuses. In the deck composition screen 400 shown in FIG. 9, "Character A," "Character B," "Character C," "Character D," and "Character E" are displayed in order from left to right as characters associated with the first through fifth slots included in the deck information. Characters A through E all include an attribute icon 402a indicating the "lightning attribute." While details will be omitted here, the deck composition display area 402 also displays each character's other status (HP, attack power, cost) in addition to the attribute icon 402a.

The owned character display area 403 displays characters owned by the user of the user terminal 10. In other words, the owned character display area 403 displays the owned characters indicated by the owned character information. Note that there is a limit to the number of characters that can be displayed in the owned character display area 403 at one time, and the user can display a group of characters different from the group of characters currently displayed in the owned character display area 403 by, for example, swiping left or right in the owned character display area 403. Also, in Figure 9, the attribute icon of the owned character displayed in the owned character display area 403 is left blank, but in reality it indicates one of the fire, water, lightning, light, or dark attributes. The owned character display area 403 also displays, for example, the character's level (e.g., Lv6, Lv3, etc.), which will be described later, in an identifiable manner.

The user can associate a character displayed in the owned character display area 403 with one of the one or more frames displayed in the deck composition display area 402 by dragging and dropping the character into that frame. The user can also disassociate a character displayed in a frame within the deck composition display area 402 from that frame by dragging and dropping the character outside of the deck composition display area 402.

The decision button 404 is a button for confirming the deck configuration displayed in the deck configuration display area 402. As will be described later, when the user taps (presses) this decision button 404, the user terminal 10 transmits deck information corresponding to the deck configuration displayed in the deck configuration display area 402 to the server device 20.

The various tabs 405 include at least a deck organization tab 405a and a skin organization tab 405b. The deck organization tab 405a is a tab for transitioning the game part to the deck organization part P1 and displaying the deck organization screen 400 on the display 15 of the user terminal 10. The skin organization tab 405b is a tab for transitioning the game part to the skin organization part P11 included in the deck organization part P1 and displaying the skin organization screen described below on the display 15 of the user terminal 10.

Returning to the explanation of Figure 7, the operation reception unit 101 accepts user operations for organizing a deck (hereinafter referred to as deck organization operations) (step S5). Deck organization operations include operations for associating characters selected by the user with one or more boxes included in the deck information (i.e., operations for dragging and dropping a character in the owned character display area 403 into a box in the deck organization display area 402), or operations for disassociating a character from one or more boxes included in the deck information (i.e., operations for dragging and dropping a character in the deck organization display area 402 from inside a box to outside the box). The characters to be associated with one or more boxes included in the deck information are selected by the user from among the owned characters displayed in the owned character display area 403.

When the operation reception unit 101 receives a user operation of tapping the decision button 404 on the deck organization screen 400 (step S6), the control unit 102 transmits deck information corresponding to the deck configuration displayed in the deck organization display area 402 to the server device 20 (step S7), and terminates the deck organization process.

Next, referring to Figure 10, we will explain the skin editing process in a quiz RPG implemented in the game system 1 according to this embodiment. Figure 10 is a flowchart showing an example of the steps of the skin editing process executed by the user terminal 10.

First, the operation reception unit 101 receives a user operation to transition to the skin organization part P11 on the game screen (hereinafter referred to as the skin organization start operation) (step S11). The skin organization start operation includes various operations for transitioning to the skin organization screen described below, such as tapping the skin organization tab 405b on the deck organization screen 400 shown in FIG. 9, or tapping the button in the skin selection dialog described below to transition to the skin organization screen.

When the operation reception unit 101 receives the skin organization start operation, the control unit 102 sends a skin organization start request to the server device 20 (step S12). The skin organization start request includes, for example, a user ID for identifying the user using the user terminal 10.

When the server device 20 receives a skin organization start request sent from the user terminal 10, it reads from the storage unit 201 the user data associated with the user ID included in the received skin organization start request, and sends the user data to the user terminal 10 of the user identified by the user ID. As a result, the user terminal 10 (control unit 102) acquires the user data from the server device 20 (step S13). The user data includes, for example, deck skin information and owned character information.

The data structure of the deck skin information is similar to the deck information shown in Figure 8, so a detailed explanation will be omitted here. However, the deck skin information defines a deck skin made up of characters owned by the user, and includes one or more slots (e.g., slots 1 to 5) for associating characters to be organized as deck skins.

The processing of steps S12 and S13 described above may be omitted. For example, when transitioning from deck organization part P1 to skin organization part P11 (i.e., when the operation reception unit 101 receives a user operation of tapping the skin organization tab 405b on the deck organization screen 400 in the processing of step S11), the user data has already been acquired in the processing of step S3 shown in FIG. 7, and in this case, the processing of steps S12 and S13 described above is omitted. The processing of steps S12 and S13 described above is mainly executed when transitioning from a game part other than deck organization part P1 to skin organization part P11.

The display processing unit 103, under the control of the control unit 102, displays a skin editing screen 410 based on the user data acquired in the processing of step S13 (or step S3) on the display 15 of the user terminal 10 (step S14).

Here, the skin organization screen 410 will be described with reference to FIG.
As shown in FIG. 11, the skin organization screen 410 includes a skin name display area 411, a skin organization display area 412, a skin-configurable character display area 413, a confirm button 414, various tabs 415, and the like.

The name of the deck skin is displayed in the skin name display area 411. In the skin organization screen 410 shown in FIG. 11, the name of the deck skin is displayed as "Deck Skin 2." The name of the deck skin displayed in the skin name display area 411 can be changed by the user as desired.

The skin organization display area 412 displays one or more characters that make up the deck skin. More specifically, the skin organization display area 412 displays one or more characters that are respectively associated with one or more slots included in the deck skin information. Each of the one or more characters displayed in the skin organization display area 412 includes an empty attribute icon (a colorless attribute icon, an attributeless attribute icon) 412a rather than the attribute icon of the attribute originally assigned to that character. In the skin organization screen 410 shown in Figure 11, "Character a," "Character a," "Character b," "Character c," and "Character d" are displayed in order from left to right as characters associated with the first through fifth slots included in the deck skin information.

The skin-configurable character display area 413 displays characters owned by the user of the user terminal 10 that meet the conditions for setting them as deck skins. In other words, the skin-configurable character display area 413 does not display characters owned by the user that do not meet the conditions for setting them as deck skins.

The conditions for setting a character as a deck skin are, for example, that the character's level is at or above a predetermined level (above a threshold level) and that the character is not a special character. However, the conditions for setting a character as a deck skin are not limited to this, and any conditions may be set depending on the game being implemented in the game system 1.

Note that "character level" here refers to the level associated with a character; for example, if a user owns multiple copies of a certain character, the "character level" of all of these identical characters will be the same.

A character's level increases based on experience points gained by, for example, correctly answering quizzes given during battles in battle part P3. Experience points for increasing a character's level can be obtained not only by correctly answering quizzes given during battles in battle part P3, but also by using items acquired when certain conditions are met in the game (for example, items acquired when a mission is completed). There may be multiple types of items for gaining the above-mentioned experience points, such as items that can be used until the character reaches a certain level and items that can be used after the character reaches a certain level.

Furthermore, the initial value of a character's level may differ depending on the character's rarity. For example, the rarer the character, the higher the initial value of the character's level may be set.

A special character is, for example, a character that is distributed to each user in the game on a limited basis, and whose appearance and attributes are customized by each user. Note that the definition of a special character may be changed as appropriate depending on the game implemented in the game system 1.

Note that there is a limit to the number of characters that can be displayed at one time in the skinnable character display area 413, and the user can display a group of characters different from the currently displayed group of characters in the skinnable character display area 413 by, for example, swiping left or right in the skinnable character display area 413.

The user can associate a character displayed in the skin configurable display area 413 with one of the one or more frames displayed in the skin organization display area 412 by dragging and dropping the character into that frame. The user can also disassociate a character displayed in a frame within the skin organization display area 412 from that frame by dragging and dropping the character outside the skin organization display area 412.

The Confirm button 414 is a button for confirming the deck skin configuration displayed in the skin organization display area 412. As will be described later, when the user taps (presses) this Confirm button 414, the user terminal 10 transmits deck skin information corresponding to the deck skin configuration displayed in the skin organization display area 412 to the server device 20.

The various tabs 415 include at least a deck organization tab 415a and a skin organization tab 415b. The deck organization tab 415a is a tab for transitioning the game part to the deck organization part P1 and displaying the deck organization screen 400 on the display 15 of the user terminal 10. The skin organization tab 415b is a tab for transitioning the game part to the skin organization part P11 included in the deck organization part P1 and displaying the skin organization screen 410 on the display 15 of the user terminal 10.

Returning to the explanation of FIG. 11, the operation reception unit 101 receives user operations for organizing deck skins (hereinafter referred to as skin organizing operations) (step S15). Skin organizing operations include operations for associating characters selected by the user with one or more frames included in the deck skin information (i.e., dragging and dropping a character in the skin-configurable character display area 413 onto a frame in the skin organizing display area 412), or operations for disassociating a character from one or more frames included in the deck information (i.e., dragging and dropping a character in the skin organizing display area 412 from inside a frame to outside the frame). The characters to be associated with one or more frames included in the deck skin information are selected by the user from among the skin-configurable characters displayed in the skin-configurable character display area 413.

When the operation reception unit 101 receives a user operation of tapping the decision button 414 on the skin organization screen 410 (step S16), the control unit 102 transmits deck skin information corresponding to the deck skin configuration displayed in the skin organization display area 412 to the server device 20 (step S17), and terminates the skin organization process.

Next, we will explain the sortie preparation part P2 with reference to the screen examples in Figures 12 to 14. Figure 12 shows an example of the sortie preparation screen 420, Figure 13 shows an example of the deck selection dialog 430, and Figure 14 shows an example of the skin selection dialog 440.

As shown in FIG. 12, the sortie preparation screen 420 includes a quest name display area 421, a selected deck name display area 422, a selected deck composition display area 423, a helper display area 424, and a challenge button 425.

The name of the quest is displayed in the quest name display area 421. In the sortie preparation screen 420 shown in Figure 12, the name of the quest is displayed as "Quest 1."

The selected deck name display area 422 displays the name of the deck selected by the user to be used in the quest (hereinafter referred to as the selected deck). In the sortie preparation screen 420 shown in FIG. 12, the name "Deck 1" is displayed as the name of the selected deck. The selected deck name display area 422 includes a deck selection button 422a for displaying a deck selection dialog 430 on the sortie preparation screen 420 for selecting the deck to be used in the quest.

The selected deck composition display area 423 displays one or more characters that make up the selected deck. More specifically, the selected deck composition display area 423 displays one or more characters that are respectively associated with one or more boxes included in the deck information of the selected deck. Each of the one or more characters displayed in the selected deck composition display area 423 includes an attribute icon 423a that indicates an attribute, which is one of the character's statuses. In the sortie preparation screen 420 shown in Figure 12, the characters that make up the selected deck, "Character A," "Character B," "Character C," "Character D," and "Character E," are displayed in order from left to right in the figure. Characters A to E all include an attribute icon 423a that indicates the "lightning attribute."

The helper display area 424 displays characters of other users who will participate in the quest as helpers. In the sortie preparation screen 420 shown in Figure 12, a helper character with a "lightning attribute" is displayed.

The challenge button 425 is a button for instructing the player to challenge the quest, that is, a button for transitioning the game part from the sortie preparation part P2 to the battle part P3.

When the deck selection button 422a is tapped on the sortie preparation screen 420 shown in FIG. 12, that is, when the operation reception unit 101 receives a user operation to tap the deck selection button 422a, the display processing unit 103 displays a deck selection dialog 430 on the display 15 of the user terminal 10 in accordance with control by the control unit 102.

As shown in FIG. 13, the deck selection dialog 430 includes multiple deck display areas 431, a skin application button 432, a skin selection button 433, and a close button 434.

Each of the multiple deck display areas 431 displays the name of a deck previously organized in the deck organization part P1 and the character associated with the first slot from among the one or more characters that make up that deck. Each of the multiple deck display areas 431 includes a selection button 431a and a deck edit button 431b. The selection button 431a is a button for selecting the deck displayed in the corresponding deck display area 431 as the deck to be used in the quest. The deck edit button 431b is a button for editing the deck displayed in the corresponding deck display area 431, and is a button for transitioning the game part to the deck organization part P1 (in other words, a button for transitioning the game screen to the deck organization screen 400).

The skin application button 432 is a button for switching whether or not a deck skin is applied; when this skin application button 432 is on, the deck skin is applied to the selected deck. On the other hand, when this skin application button 432 is off, the deck skin is not applied to the selected deck. When the skin application button 432 is on, the selected deck composition display area 423 of the sortie preparation screen 420 displays one or more characters that make up the selected deck and one or more characters that make up the deck skin, switching between them at regular intervals. This allows the user to visually confirm both the selected deck and the deck skin that will be applied to the selected deck on the sortie preparation screen 420.

The skin selection button 433 is a button that further opens the skin selection dialog 440 for selecting a deck skin to apply to the selected deck.

The close button 434 is a button for closing the deck selection dialog 430 and redisplaying the sortie preparation screen 420 on the display 15 of the user terminal 10.

When the skin selection button 433 is tapped in the deck selection dialog 430 shown in FIG. 13, that is, when the operation reception unit 101 receives a user operation of tapping the skin selection button 433, the display processing unit 103 displays the skin selection dialog 440 on the display 15 of the user terminal 10 in accordance with control by the control unit 102.

As shown in FIG. 14, the skin selection dialog 440 includes multiple deck skin display areas 441 and a close button 442.

Each of the multiple deck skin display areas 441 displays the name of a deck skin that has been pre-organized in the skin organization part P11, along with one or more characters that make up that deck skin. Each of the multiple deck skin display areas 441 includes a selection button 441a and a skin edit button 441b. The selection button 441a is a button for selecting the deck skin displayed in the corresponding deck skin display area 441 as the deck skin to be applied to the selected deck. The skin edit button 441b is a button for editing the deck skin displayed in the corresponding deck skin display area 441, and is a button for transitioning the game part to the skin organization part P11 (in other words, a button for transitioning the game screen to the skin organization screen 410).

The close button 442 is a button for closing the skin selection dialog 440 and redisplaying the deck selection dialog 430 on the display 15 of the user terminal 10.

Next, referring to Figure 15, we will explain the skin application process in the quiz RPG implemented in the game system 1 according to this embodiment. Figure 15 is a flowchart showing an example of the steps of the skin application process executed by the user terminal 10.

First, when the operation reception unit 101 receives a user operation of tapping the challenge button 425 on the sortie preparation screen 420, the control unit 102 determines whether the skin application button 432 is turned on (step S21).

If, in the processing of step S21, it is determined that the skin application button 432 is not turned on, that is, that the skin application button 432 is turned off (No in step S21), the control unit 102 does not apply a deck skin to the deck selected by the user in the deck selection dialog 430 (selected deck), and proceeds to the processing of step S26, which will be described later.

On the other hand, if it is determined in the processing of step S21 that the skin application button 432 is turned on (Yes in step S21), the control unit 102 determines whether a character associated with a specific frame among one or more frames included in the deck information corresponding to the deck selected by the user in the deck selection dialog 430 (selected deck) satisfies the conditions for applying a deck skin. More specifically, the control unit 102 determines whether the level of the character associated with the specific frame is equal to or higher than a threshold level, and whether the character associated with the specific frame is not a special character (step S22). Note that this processing is performed, for example, starting with the first frame included in the deck information.

If, in the processing of step S22, it is determined that the character associated with a specified frame does not meet the conditions for applying a deck skin (No in step S22), the control unit 102 does not apply a deck skin to the character associated with the specified frame (step S23), and proceeds to the processing of step S25, which will be described later.

On the other hand, if it is determined in the processing of step S22 that the character associated with a specified frame meets the conditions for applying a deck skin (Yes in step S22), the control unit 102 applies, as a deck skin to the character associated with the specified frame, the character associated with the frame that corresponds to the specified frame, from among one or more frames included in the deck skin information corresponding to the deck skin selected by the user in the skin selection dialog 440 (step S24).

The control unit 102 determines whether the processing of step S24 described above has been performed (whether it has determined whether a deck skin can be applied) for all characters associated with one or more frames included in the deck information corresponding to the selected deck (step S25).

If, in the processing of step S25, it is determined that the processing of step S22 described above has not been performed for all characters, that is, that the applicability of deck skins has not been determined for all characters (No in step S25), the control unit 102 performs the processing of step S22 described above for characters associated with frames for which the applicability of deck skins has not yet been determined.

On the other hand, if it is determined in step S25 that the processing of step S22 has been performed for all characters (Yes in step S25), the control unit 102 sends a quest start request to the server device 20 to transition to battle part P3 (step S26), and ends the skin application processing.

Here, we will explain a specific example of the skin application process with reference to Figures 16 and 17.

The case shown in Figure 16 assumes that the characters making up the selected deck are "Character A," "Character B," "Character C," "Character D," and "Character E," and the characters making up the deck skin are "Character a," "Character a," "Character b," "Character c," and "Character d." The case shown in Figure 16 also assumes that of the characters A through E making up the selected deck, only character C has a character level below the threshold level. In this case, only character C does not have the corresponding deck skin (i.e., character b in the third slot), and the other characters A, B, D, and E have the corresponding deck skins applied, so that in battle part P3, a deck with the appearance of "Character a," "Character a," "Character C," "Character c," and "Character d" is displayed.

The case shown in Figure 17 assumes that the characters making up the selected deck are "Character A," "Character B," "Character C," "Character D," and "Character E," and the characters making up the deck skin are "Character a," "Character a," "Character b," "Character c," and "Character d." The case shown in Figure 17 also assumes that of the characters A through E making up the selected deck, only character C is a special character. In this case, only character C does not have the corresponding deck skin (i.e., character b in the third slot), and the other characters A, B, D, and E each have their corresponding deck skin applied, so in battle part P3, a deck with the appearance of "Character a," "Character a," "Character C," "Character c," and "Character d" is displayed.

Next, the battle part P3 will be described with reference to the screen example in Figure 18. Figure 18 is a diagram showing an example of a battle screen 450. Note that Figure 18 assumes that the characters making up the selected deck are "Character A," "Character B," "Character C," "Character D," and "Character E," and the characters making up the deck skin are "Character a," "Character a," "Character b," "Character c," and "Character d." Figure 18 also assumes that the skin application button 432 is on, and that characters A through E making up the selected deck meet the conditions for applying a deck skin. In other words, it assumes that a quest start request is sent from the user terminal 10 to the server device 20 with deck skins applied to characters A through E using the skin application process shown in Figure 15.

As shown in FIG. 18, the battle screen 450 includes an enemy character display area 451, an ally character display area 452, and a quiz menu display area 453.

The enemy character display area 451 displays enemy characters that fight against friendly characters. In the battle screen 450 shown in Figure 18, three water-attribute enemy characters are displayed.

The ally character display area 452 displays one or more ally characters that make up the selected deck and that fight against enemy characters. As described above, Figure 18 assumes that the skin application button 432 is on and that characters A to E that make up the deck meet the conditions for applying a deck skin. Therefore, instead of characters A to E that make up the selected deck, the ally character display area 452 displays "Character a," "Character a," "Character b," "Character c," and "Character d," which are characters that make up the deck skin, lined up in order from left to right in the figure.

More specifically, character a with the status of character A is displayed in the first frame of the ally character display area 452, which displays the character associated with the first frame included in the deck information of the selected deck. In other words, by applying the deck skin, the appearance of character A has been changed to character a in the first frame of the ally character display area 452, while character A's status remains the same. Therefore, character a is displayed in the first frame of the ally character display area 452, including an attribute icon 452a indicating character A's attribute, the "lightning attribute."

Similarly, the second frame of the ally character display area 452, which displays the character associated with the second frame included in the deck information of the selected deck, displays character a with the status of character B. In other words, the second frame of the ally character display area 452 retains the status of character B, but the appearance has changed from character B to character a. Therefore, the second frame of the ally character display area 452 displays character a with an attribute icon 452a indicating the "lightning attribute," which is character B's attribute.

In addition, character b with the status of character C is displayed in the third frame of the ally character display area 452, which displays the character associated with the third frame included in the deck information of the selected deck. In other words, the appearance of the third frame of the ally character display area 452 has changed from character C to character b, while the status of character C remains the same. Therefore, character b is displayed in the third frame of the ally character display area 452, including an attribute icon 452a indicating the "lightning attribute", which is character C's attribute.

Furthermore, the fourth frame of the ally character display area 452, which displays the character associated with the fourth frame included in the deck information of the selected deck, displays character c with the status of character D. In other words, the fourth frame of the ally character display area 452 retains the status of character D, but the appearance has changed from character D to character c. Therefore, the fourth frame of the ally character display area 452 displays character c, including an attribute icon 452a indicating the "lightning attribute," which is character D's attribute.

In addition, character d with the status of character E is displayed in the fifth box of the ally character display area 452, which displays the character associated with the fifth box included in the deck information of the selected deck. In other words, the appearance of character E has been changed from character E to character d, while the status of character E remains the same in the fifth box of the ally character display area 452. Therefore, character d is displayed in the fifth box of the ally character display area 452, including an attribute icon indicating the "lightning attribute", which is character E's attribute.

In addition, on the battle screen 450 of Figure 18, an icon 452b indicating that a deck skin has been applied is displayed in the lower left corner of each frame in the ally character display area 452. This allows the user of the user terminal 10 to recognize that a deck skin has been applied to the character in the frame in which icon 452b is displayed (in other words, the character in the frame in which icon 452b is displayed is a deck skin character).

Furthermore, while playing the game, a user of the user terminal 10 may take a screenshot of the battle screen 450 and show (transmit) the screenshot to other users, for example, via SNS. By viewing such a screenshot, other users can obtain information useful for completing the quest, such as characters that will be advantageous in the quest. In this case, if a deck skin has been applied to the characters that make up the selected deck, the deck skin characters will be displayed on the battle screen 450 as described above, which may lead other users to mistakenly believe that the deck skin characters are characters that will be advantageous in the quest. However, by displaying icon 452b indicating that a deck skin has been applied, other users can recognize that the character in the frame in which icon 452b is displayed is a deck skin character, thereby preventing the above-mentioned mistaken recognition from occurring.

Note that the shape of icon 452b is not limited to the shape shown in Figure 18, and any shape may be used as long as it is possible to identify that a deck skin has been applied.

In addition, each frame in the ally character display area 452 may flash a character before the deck skin is applied, i.e., a character from the selected deck, at regular intervals. Users tend to associate a character's appearance with its status in their memory. For this reason, by flashing a character before the deck skin is applied, i.e., a character from the selected deck, at regular intervals, the user can more easily recognize the actual status of the character in each frame in the ally character display area 452.

The quiz menu display area 453 displays a quiz menu for selecting the genre of the quiz to be asked during battle. The battle screen 450 shown in FIG. 18 displays a quiz menu from which the genres "Entertainment," "Trivia," "Sports," and "Entertainment" can be selected. When one of these quiz menus is selected, a quiz corresponding to the selected genre will be asked to the user.

Next, we will explain the result part P4 with reference to the example screen in Figure 19. Figure 19 shows an example of the clear result screen 460.

As shown in FIG. 19, the clear result screen 460 includes a quest name display area 461, a cleared formation display area 462, an OK button 463, and a retry button 464.

The quest name display area 461 displays the name of the quest. In the clear result screen 460 shown in Figure 19, the name of the quest is displayed as "Quest 1."

The cleared formation display area 462 displays one or more characters that make up the deck that cleared the quest (hereinafter referred to as the cleared deck). More specifically, the cleared formation display area 462 displays one or more characters that are respectively associated with one or more slots included in the deck information of the cleared deck. The selected deck used for the quest and the cleared deck that cleared the quest using the selected deck are the same.

Even if a deck skin has been applied to the selected deck using the skin application process shown in FIG. 15, the selected deck without the deck skin applied will be displayed as the cleared deck in the cleared formation display area 462. This means that even if a user of the user terminal 10 takes a screenshot of the cleared result screen 460 and shows (transmits) the screenshot to other users, for example, via SNS, the selected deck with the deck skin applied will not be displayed as the cleared deck, preventing an incorrect deck formation from being transmitted to other users. Note that, in addition to the cleared deck, the cleared result screen 460 may also display information that a deck skin has been applied to the cleared deck and the configuration of the deck skin. Furthermore, similar to the quest result screen 460, in environments where other users can view the decks used, such as during specific events, it is desirable to display the deck without the deck skin applied.

In addition, experience points earned by correctly answering quizzes given during quests may be given to the characters that make up the selected deck, or may be split between the characters that make up the selected deck and the characters that make up the deck skin.

The OK button 463 is a button for transitioning the game part from the result part P4 to the main part P5. The retry button 464 is a button for transitioning the game part from the result part P4 to the battle part P3 and instructing the player to retry the quest using the clear deck displayed in the clear formation display area 462.

As described above, in this embodiment, a character (first character) having a predetermined status (ability value) in a game implemented in the game system is displayed, along with another character (second character) having a status different from the predetermined status and having a different appearance or voice from the first character. Furthermore, in this embodiment, the appearance or voice of the first character is changed to the appearance or voice of the second character without changing the status of the first character. Alternatively, the status of the first character is changed to the status of the second character without changing the appearance or voice of the first character.

In this embodiment, the above-described configuration makes it possible to prevent a decline in motivation among users playing a game (quiz RPG) featuring a large number of characters, while increasing the interest of the game.

Specifically, as a comparative example to this embodiment, a configuration could be considered in which the appearance of equipment equipped by one character is changed to another piece of equipment while maintaining the performance of that equipment. However, with such a configuration, it is only possible to change the appearance of the equipment, and it is not possible to change the appearance or voice of a character to that of another character. As a result, it would not be possible to satisfy the user's desire to use a favorite character.

In contrast, in this embodiment, the appearance (appearance) of a character organized in a deck can be changed to the appearance (appearance) of another character organized in a deck skin, thereby satisfying the above-mentioned user needs and preventing a decrease in the user's motivation to play the game.

Furthermore, in this embodiment, the voice of a character organized in a deck can be changed to the voice of another character organized in a deck skin. This makes it possible to satisfy the needs of users who, for example, like the character's voice rather than its appearance, and to prevent a decline in the motivation of such users.

In addition, in this embodiment, if a character organized into a deck meets the conditions for applying a deck skin, and the character you want to organize into a deck skin meets the conditions for setting it as a deck skin, the appearance or voice of the character organized into the deck can be changed to the appearance or voice of the character organized into the deck skin. In other words, both the character organized into the deck and the character organized into the deck skin must meet certain conditions, and since you cannot immediately use your favorite character as a deck skin in any deck organization, this can be expected to increase the user's motivation to "try hard to use your favorite character" and encourage the user to continue playing the game.

Furthermore, in this embodiment, the appearance or voice of a character can be changed to that of another character all at once on a deck-by-deck basis, thereby reducing the burden (effort) on the user compared to changing the appearance or voice of each character one by one.

Furthermore, in this embodiment, since it is possible to set multiple identical characters as deck skins, it is possible, for example, to change the appearance or voice of all the characters that make up a deck to that of just one character of the user's choice. This satisfies the needs of even the most hardcore users.

Furthermore, in this embodiment, as shown in FIG. 18, an icon 452b indicating that a deck skin has been applied is displayed near the character of that deck skin, and the character before the deck skin was applied can be flashed at regular intervals. In short, in this embodiment, information that identifies that a deck skin has been applied can be displayed in association with the character of that deck skin. This prevents the user from becoming confused and prevents other users from perceiving incorrect information.

In addition, in this embodiment, even if a deck skin has been applied to a deck used in a quest, the deck without the deck skin applied will be displayed as the cleared deck on the quest result screen 460 shown in FIG. 19. This prevents other users from mistakenly recognizing a deck with a deck skin applied as the cleared deck.

Furthermore, in this embodiment, during multiplayer mode, where multiple users cooperate to play a single quest, even if other users have applied deck skins, the deck will be displayed without the deck skin applied. This allows you to accurately understand the deck configurations of other users and develop a strategy for conquering the quest.

In the embodiment described above, we have explained the case where the appearance or voice of a character is changed to that of another character on a deck-by-deck basis, but it is also possible to change the appearance or voice of each character individually.

Furthermore, in this embodiment, we have mainly described a case where a character's appearance or voice is changed to that of another character without changing the character's status, but similar control can also be used to change a character's status to that of another character without changing the character's appearance or voice.

Furthermore, in this embodiment, a case has been described in which one or more frames that make up a deck correspond to one or more frames that make up a deck skin, but this is not limited to this. For example, a priority may be set in advance for one or more characters that make up a deck skin, and the deck skins may be applied to one or more characters that make up a deck in order of highest priority.

The present invention is not limited to the above-described embodiments, and can be embodied by modifying the components in the implementation stage without departing from the spirit of the invention. Furthermore, various inventions can be created by appropriately combining multiple components disclosed in the above-described embodiments. For example, some components may be omitted from all of the components shown in the embodiments. Furthermore, components from different embodiments may be combined as appropriate.

1...Game system, 10...User terminal, 11...Non-volatile memory, 12...CPU, 13...Main memory, 13A...Game program, 14...Wireless communication device, 15...Display, 16...Touch panel, 20...Server device, 21...Non-volatile memory, 22...CPU, 23...Main memory, 23A...Game program, 24...Wireless communication device, 30...Network, 101...Operation reception unit, 102...Control unit, 103...Display processing unit, 104...Storage unit, 201...Storage unit, 202...Data management unit, 203...Control unit.

Claims (4)

Computer,
a display means for displaying a first character having a first ability value as an ability value in a game, and a second character having a second ability value different from the first ability value and having a different aspect from the first character;
a change means for changing the state of the first character to the state of the second character without changing the ability value of the first character from the first ability value, or for changing the ability value of the first character to the second ability value of the second character without changing the state of the first character;
The game includes a quest with a predetermined completion condition set therefor,
the change means changes the appearance of the first character used by the user in the quest to the appearance of the second character;
The display means displays the first character used by the user in the quest in the form of the first character on a result screen showing the result of the quest . Computer,
a display means for displaying a first character having a first ability value as an ability value in a game, and a second character having a second ability value different from the first ability value and having a different aspect from the first character;
a change means for changing the state of the first character to the state of the second character without changing the ability value of the first character from the first ability value, or for changing the ability value of the first character to the second ability value of the second character without changing the state of the first character;
The game includes a quest for which a predetermined clearing condition is set, and includes a game environment in which the quest is shared and played by a plurality of users;
the change means changes the appearance of the first character used by the user in the quest to the appearance of the second character;
The display means displays the first character having the aspect of the second character used by another user in the quest in the aspect of the first character . a display means for displaying a first character having a first ability value as an ability value in a game, and a second character having a second ability value different from the first ability value and having a different aspect from the first character;
a change means for changing the state of the first character to the state of the second character without changing the ability value of the first character from the first ability value, or for changing the ability value of the first character to the second ability value of the second character without changing the state of the first character;
Equipped with
The game includes a quest with a predetermined completion condition set therefor,
the change means changes the appearance of the first character used by the user in the quest to the appearance of the second character;
The display means displays the first character used by the user in the quest in the form of the first character on a result screen showing the result of the quest . a display means for displaying a first character having a first ability value as an ability value in a game, and a second character having a second ability value different from the first ability value and having a different aspect from the first character;
a change means for changing the state of the first character to the state of the second character without changing the ability value of the first character from the first ability value, or for changing the ability value of the first character to the second ability value of the second character without changing the state of the first character;
Equipped with
The game includes a quest for which a predetermined clearing condition is set, and includes a game environment in which the quest is shared and played by a plurality of users;
the change means changes the appearance of the first character used by the user in the quest to the appearance of the second character;
The display means displays the first character having the appearance of the second character used by another user in the quest in the appearance of the first character.