JP2023169191A - Message system, program, and message generation method - Google Patents

Abstract

To shorten the time required for inputting while securing flexibility in contents of a message.SOLUTION: In a message system in which a server 10 and each terminal 20 mutually transmit and receive data through a communication network, the server includes: a registration message data storage unit 72 for storing registration message data indicating an object-related registration message registered beforehand and set so that a symbol string on at least one object is inserted into a predetermined position or replaced with a predetermined part; an object selection reception result acquisition unit 94 for acquiring a reception result of an object selection reception unit 92 for receiving the selection of an object displayed on a screen; and a message acquisition unit 96 for acquiring, as a message input by a user, a message acquired by inserting the symbol string related to at least one object selected by the user into a predetermined position of the object-related registration message or replacing it with the predetermined part.SELECTED DRAWING: Figure 9

Description

The present invention relates to a message input receiving device, a message system, and a program.

2. Description of the Related Art Systems are known that allow multiple users to communicate by sending and receiving messages. For example, a game system is known in which a plurality of users can communicate with each other by sending and receiving messages while playing a game.

Patent No. 4637192

For example, in a game where a user plays a game while communicating with other users, it is necessary to quickly input messages in accordance with the ever-changing game situation.

Conventionally, in the above-mentioned games, a method of inputting a message into an input field has been adopted as a method of inputting a message. According to this input method, it is possible to input a message that matches the current situation, but since it is necessary to type the message each time, it may take a long time to input the message. As a result, for example, the game situation may change while a message is being input, resulting in a situation where the contents of the input message do not match the current situation.

Furthermore, in the above games, a method of inputting a message by selecting a message registered in advance is also adopted as a method of inputting a message. According to this input method, it is possible to shorten the time required to input a message, but since only messages with predetermined contents can be selected, there is no flexibility in message contents, and the current situation In some cases, it was not possible to enter a message that matched the content. That is, if a message with content suitable for the current situation has not been registered in advance, it is not possible to input a message with content suitable for the current situation.

The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to provide a message input reception device and a message system capable of shortening the time required to input a message while ensuring flexibility regarding message content. , and to provide programs.

In order to solve the above-mentioned problems, a message input reception device according to the present invention is configured such that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part in a registered message registered in advance. a registered message data acquisition means for acquiring the registered message data stored in a registered message data storage means for storing registered message data indicating an object-related registered message that has been registered, and a selection of an object to be displayed on the screen is received from a user. an object selection reception result acquisition means for acquiring a reception result of the object selection reception means; and inserting a symbol string associated with at least one object selected by the user into the predetermined position of the object related registration message; Message acquisition means for acquiring a message obtained by replacing a predetermined portion as a message input by the user.

Furthermore, the message system according to the present invention indicates an object-related registered message that is registered in advance and is set such that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part. A registration message data acquisition means for acquiring the registered message data stored in a registration message data storage means for storing the registered message data, and an object selection reception means for accepting from the user a selection of an object to be displayed on the screen. object selection acceptance result acquisition means to obtain, and a symbol string associated with at least one object selected by the user, by inserting it into the predetermined position of the object-related registration message or replacing it with the predetermined part. Message acquisition means for acquiring a message inputted by the user as a message input by the user.

Further, the program according to the present invention is a registration message registered in advance, which is a registration message indicating an object-related registration message set such that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part. A registered message data acquisition means that acquires the registered message data stored in a registered message data storage means that stores message data, and an object that acquires the reception result of the object selection reception means that accepts from the user the selection of an object to be displayed on the screen. a message obtained by inserting a symbol string associated with at least one object selected by the user into the predetermined position of the object-related registration message or replacing the predetermined portion of the object-related registration message; This is a program for causing a computer to function as a message acquisition means for acquiring a message input by the user.

Further, an information storage medium according to the present invention is a computer-readable information storage medium on which the above program is recorded.

FIG. 1 is a diagram showing an example of the overall configuration of a message system. It is a figure showing an example of a game screen. It is a figure showing an example of a game screen. It is a figure showing an example of a game screen. It is a figure showing an example of a game screen. It is a figure showing an example of a game screen. It is a figure showing an example of a list screen. It is a figure showing an example of a registration screen. FIG. 2 is a functional block diagram of a message system. FIG. 3 is a diagram showing an example of a registered message table. It is a figure which shows an example of an object table. It is a figure which shows an example of a message table. FIG. 2 is a diagram illustrating an example of processing executed by the message system. It is a figure which shows an example of other processing performed by a message system. It is a figure showing an example of a game screen. It is a figure showing an example of a game screen. It is a figure showing an example of a game screen. FIG. 2 is a functional block diagram of a message system.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Examples of embodiments of the present invention will be described in detail below with reference to the drawings.

FIG. 1 is a diagram showing the overall configuration of a message system according to an embodiment of the present invention. A message system realizes a chat in which multiple users participate by controlling the sending and receiving of messages between multiple users. As shown in FIG. 1, the message system 1 includes a server 10 and a plurality of terminals 20. The server 10 and each terminal 20 can send and receive data to and from each other via the communication network 2.

Server 10 is realized by a server computer. As shown in FIG. 1, the server 10 includes a control section 11, a storage section 12, and a communication section 13. The control unit 11 includes one or more microprocessors, and executes processing according to an operating system and other programs. The storage unit 12 includes a main storage unit (for example, RAM) and an auxiliary storage unit (for example, a hard disk drive or solid state drive). The communication unit 13 is for performing data communication via the communication network 2.

The terminal 20 is a computer operated by a user. The terminal 20 is, for example, a mobile phone (including a smartphone), a personal digital assistant (including a tablet computer), a desktop computer, a laptop computer, or a game machine (home game machine, or installed in an amusement facility, etc.). (including arcade game machines). As shown in FIG. 1, the terminal 20 includes a control section 21, a storage section 22, a communication section 23, an operation section 24, and a display section 25.

The control unit 21, storage unit 22, and communication unit 23 are similar to the control unit 11, storage unit 12, and communication unit 13 of the server 10. The operation unit 24 is an input device, for example, a pointing device such as a touch panel. The display section 25 is, for example, a liquid crystal display panel or an organic EL display, and displays various images according to instructions from the control section 21.

Programs and data described as being stored in the storage unit 12 or 22 are supplied to the server 10 or the terminal 20 via the communication network 2, for example. Note that the server 10 or the terminal 20 may include a component for reading a program or data stored in a computer-readable information storage medium (for example, a memory card or an optical disk). Then, the program and data may be supplied to the server 10 or the terminal 20 via an information storage medium. Further, programs and data described as being stored in the storage unit 12 or 22 may be stored in a storage unit of a device that is accessible from the server 10 or the terminal 20 via the communication network 2.

Next, a chat executed in the message system 1 will be explained. Here, an example will be described in which four users playing a game chat while working together to defeat a common enemy. Note that these four users are herein referred to as users A, B, C, and D, respectively, and when there is no need to distinguish between users A to D, they are simply referred to as "users." Note that the "user" here is a person who inputs a message (a person who operates the terminal 20), and can also be said to be a player of the game.

FIG. 2 is a diagram showing an example of a game screen displayed on the display unit 25 of the terminal 20. Here, the game screen displayed on user A's terminal 20 will be described. Note that the terminal 20 includes a touch panel provided over the display unit 25, and allows the user to select an object displayed on the game screen by touching the object with a finger on the object displayed on the game screen. This will be explained as follows.

As shown in FIG. 2, a game image showing the state of the game being executed is displayed on the game screen 30. On the game screen 30 shown in FIG. 2, an enemy object 32 representing a common enemy of users A, B, C, and D is displayed. The enemy object 32 is an image representing an enemy.

Further, user objects 34A, 34B, 34C, and 34D representing users A, B, C, and D, respectively, are displayed on the game screen 30. User objects 34A to 34D are avatar images representing users A to D, respectively. Note that hereinafter, when there is no need to distinguish between the user objects 34A to 34D, they will simply be referred to as "user objects 34."

Furthermore, item objects 36X, 36Y, and 36Z representing items X, Y, and Z, respectively, are displayed on the game screen 30. Item objects 36X to 36Z are images representing items X to Z, respectively. Note that in the following description, the item objects 36X to 36Z are simply referred to as "item object 36" when there is no need to distinguish them.

Note that an "item" is something used in the game. An "item" is something that produces a predetermined effect when used in a game. For example, an "item" is something that allows the user to advance in battle against an enemy advantageously. For example, items that damage enemies, items that recover damage taken by the user, items that reduce the enemy's abilities (attack power or defense power, etc.), or items that reduce the user's abilities (attack power or defense power, etc.) etc.) There are items that improve the performance. A user can use an item by selecting the item object 36.

Also, an attack icon 38 is displayed on the game screen 30. The attack icon 38 is an icon for instructing an attack on an enemy. For example, in this embodiment, when attacking an enemy, the user selects a part to attack. For example, it is possible to select the head, left arm, or right arm as the part to be attacked. That is, when the user selects the attack icon 38 and then selects either the enemy's head, left arm, or right arm as a part to be attacked, an attack is executed against the selected part. For example, in the game screen 30 shown in FIG. 2, the enemy is holding a weapon in his left hand and a shield in his right hand. Therefore, for example, by attacking the enemy's left arm, the enemy's attack power can be reduced, and by attacking the enemy's right arm, the enemy's defense power can be reduced. Further, for example, when the damage inflicted on the enemy's head reaches a predetermined value, it is determined that the enemy has been defeated.

Furthermore, a chat icon 40 is displayed on the game screen 30. The chat icon 40 is an icon for making a comment. That is, the chat icon 40 is an icon for inputting a message to another user.

Note that a "message" is information transmitted between terminals operated by a user, and is, for example, a symbol string, a moving image, a voice, or a combination thereof input or specified by the user. Here, the term "symbol string" refers to a character string (including, for example, an emoticon, an ASCII art, or a plus/minus sign constituting a code that can be understood only between users), an image, or a combination thereof. Further, the "symbol string" includes a symbol string whose length is "1".

When the chat icon 40 is selected by the user, a message registered in advance (hereinafter referred to as "registered message") is displayed as a message candidate for another user. FIG. 3 shows an example of the game screen 30 in this case. On the game screen 30 shown in FIG. 3, a plurality of registered message objects 42A, 42B, 42C, 42D, 42E, and 42F each representing a plurality of registered messages are displayed. A user can enter a message for another user by selecting one of the registered message objects 42A-42F. Note that hereinafter, when there is no need to distinguish between the registered message objects 42A to 42F, they will simply be referred to as "registered message object 42."

By the way, in this embodiment, it is possible to register a message regarding a certain target (for example, an attack target part, item, user, etc.) without specifically specifying the target. For example, a message that urges another user to take a certain action (e.g., attack an enemy, use an item, use a special skill, or use magic, etc.) or a message that tells another user to take a certain action, It is possible to register the target of the action (for example, the body part to be attacked, the item to be used, the special technique to be used, the magic to be used, etc.) without specifically specifying it. Furthermore, for example, it is possible to register a message expressing greetings or gratitude to a certain user without specifically specifying the other user.

For example, in this embodiment, a message including a tag can be registered as a registered message. In the example shown in FIG. 3, for example, the tags <part>, <item>, and <user> are included in the registration message.

For example, the registration message represented by the registration message object 42A includes a <part> tag. This registered message is a message that calls on other users to attack a certain body part, but the part that indicates the body part to be attacked is a <body part> tag, and the body part to be attacked is specifically identified. is not specified. As will be described later, the <part> tag indicates a part that can be replaced with the name of any part. Note that the name of one of the parts will be inserted at the position indicated by the <part> tag, so the <part> tag indicates the position where the name of one of the parts will be inserted. You can also do it.

Further, for example, the registered message represented by the registered message object 42C includes an <item> tag. This registration message is a message that informs other users that a certain item will be used, but the part that indicates the item to be used is an <item> tag, and the item to be used is specifically specified. It is in a state where there is no. As will be described later, the <item> tag indicates a portion that can be replaced with the name of any item. Note that the name of one of the items will be inserted at the position indicated by the <item> tag, so the <item> tag indicates the position where the name of one of the items will be inserted. You can also do it.

Further, for example, the registration message represented by the registration message object 42E includes a <user> tag. This registered message is a message (greeting) to a certain user, but the part indicating the other user is a <user> tag, and the other user is not specifically specified. As will be described later, the <user> tag indicates a portion that can be replaced with the name of any user. Note that the name of one of the users will be inserted at the position indicated by the <user> tag, so the <user> tag indicates the position where the name of one of the users will be inserted. You can also do it.

Examples of tags are not limited to those described above. For example, a tag indicating a special skill or magic may be included in the registration message. Note that it is also possible to register a message that does not include the tag as described above as a registered message (see registered message object 42F).

FIG. 4 shows an example of the game screen 30 when a registered message object 42 representing a registered message including a tag is selected by the user. Note that FIG. 4 shows an example of the game screen 30 when the registered message object 42A is selected. As described above, the registered message represented by the registered message object 42A includes the <body part> tag, and the body part to be attacked is not specifically specified. Therefore, in this case, the user is required to select the part to be attacked.

In this case, the game screen 30 displays a marker indicating a part that the user can select as an attack target. FIG. 4 shows a case where either the enemy's head, left arm, or right arm can be selected as an attack target. Therefore, on the game screen 30 shown in FIG. 4, markers 44A, 44B, and 44C are displayed in association with a part object 33A representing the head, a part object 33B representing the left arm, and a part object 33C representing the right arm, respectively. Note that the part objects 33A to 33C are images representing the enemy's head, left arm, and right arm, respectively. Further, hereinafter, when there is no need to distinguish between body part objects 33A to 33C, they will be simply referred to as "part object 33", and when there is no need to distinguish between markers 44A to 44C, they will simply be denoted as "marker 44".

Note that since the registered message represented by the registered message object 42B also includes the <part> tag, the markers 44A to 44C shown in FIG. 4 are displayed even when the registered message object 42B is selected.

Further, the registered messages represented by the registered message objects 42C and 42D include an <item> tag, and any item is not specifically specified. Therefore, when the registered message object 42C or 42D is selected, the user is requested to select an item. That is, the markers 44 are displayed in association with the item objects 36X to 36Z, respectively.

Furthermore, the registration message represented by the registration message object 42E includes a <user> tag, and is in a state in which no user is specifically specified. Therefore, when the registered message object 42E is selected, the user is requested to make a selection. That is, markers 44 are displayed in association with user objects 34A to 34D, respectively.

On the game screen 30 shown in FIG. 4, the user selects one of the body part objects 33 by selecting one of the markers 44A to 44C. FIG. 5 shows an example of the game screen 30 when one of the markers 44A to 44C is selected. Note that FIG. 5 shows an example of the game screen 30 when the marker 44B is selected (that is, when the part object 33B representing the left arm is selected).

As shown in FIG. 5, a transmission icon 46 is displayed on the game screen 30 in this case. When the send icon 46 is selected by the user, it is determined that the message obtained by replacing the <part> tag included in the registered message represented by the registered message object 42A with the name of the part object 38B (left arm) has been input by the user. be done. In other words, it is determined that the message "Let's attack the left arm" has been input by the user. Note that when the marker 44B is selected, it may be determined that the message "Let's attack the left arm" has been input by the user without displaying the transmission icon 46.

If it is determined that the message "Let's attack the left arm" has been input by the user, a message object 48 representing the message is displayed on the game screen 30, as shown in FIG. The message object 48 is displayed on each terminal 20 of users A, B, C, and D.

The message object 48 is displayed in association with the user object 34A representing the user A who inputted the message. For example, in the example shown in FIG. 6, the message object 48 is a balloon image containing a message inside the balloon. The message object 48 is displayed as a speech bubble extending from the user object 34A representing the user A. This makes it possible to identify that the message was input by user A.

Note that the message object 48 is not represented two-dimensionally as shown in FIG. 6, but may be represented three-dimensionally in the virtual space.

As described above, the message system 1 allows the user to input a message that matches the current situation. For example, in a situation where the user should attack the enemy's left arm, the user can input a message urging other users to attack the enemy's left arm.

Furthermore, in the message system 1, the user can input a message suitable for the current situation as described above by selecting a registered message and an object. For example, by selecting the registered message object 42A and the part object 33B (marker 44B), the user can input a message urging other users to attack the enemy's left arm. In other words, the user can enter a message like the one above without having to type the message each time.

That is, according to the message system 1, it is possible to reduce the time required to input a message while ensuring flexibility regarding message content.

Note that the registration message described above is set for each user. That is, the message system 1 allows the user to arbitrarily set a registered message as described above. Here, the steps that the user performs to set a registration message will be explained.

FIG. 7 shows an example of a list screen showing a list of registered messages. The list screen 50 shown in FIG. 7 is displayed on the display unit 25 of the terminal 20, for example, when the user performs a predetermined operation. As shown in FIG. 7, a list of registered messages is displayed on the list screen 50. Furthermore, setting icons 52A, 52B, 52C, 52D, 52E, and 52F are displayed in association with each registered message. The user selects one of the registered messages displayed on the list screen 50 by selecting one of the setting icons 52A to 52F. In the following, when there is no need to distinguish between the setting icons 52A to 52F, they will simply be referred to as "setting icons 52."

When any one of the registered messages displayed on the list screen 50 is selected, a registration screen for registering the registered message is displayed. FIG. 8 shows an example of the registration screen. A field 62 is displayed on the registration screen 60 shown in FIG. Field 62 is a field for the user to input a message.

Further, a virtual keyboard 64 is displayed on the registration screen 60 shown in FIG. The virtual keyboard 64 is a virtual keyboard (software keyboard) for inputting symbols (for example, characters) into the field 62. Note that the user interface for inputting symbols is not limited to the virtual keyboard 64, and various user interfaces can be employed as the user interface for inputting symbols.

Further, tag icons 66A, 66B, and 66C are displayed on the registration screen 60 shown in FIG. 8. For example, the tag icon 66A is an icon corresponding to the <part> tag. Tag icon 66A is used to include a <part> tag in a message. A user can set a <part> tag in a message by dragging and dropping tag icon 66A into field 62. That is, when the user touches the tag icon 66A with a finger on the touch panel, moves the finger to the field 62 while keeping the finger in contact with the touch panel, and releases the finger from the touch panel, the <region> tag is displayed. is set as part of the message.

For example, the tag icon 66B is an icon corresponding to the <user> tag. Tag icon 66B is used to include the <user> tag in the message. Further, the tag icon 66C is an icon corresponding to the <item> tag. Tag icon 66C is used to include an <item> tag in the message.

Note that the user interface for inputting tags is not limited to the above example. Various user interfaces can be employed as the user interface for inputting tags. For example, the user may input the tag using the virtual keyboard 64.

Further, a registration icon 68 is displayed on the registration screen 60 shown in FIG. When the registration icon 68 is selected, the message entered in the field 62 is registered. That is, the message input in field 62 is set as the registered message.

As described above, the user can set a new registered message or change the registered message.

Next, a configuration for realizing the functions described above will be described. FIG. 9 is a functional block diagram showing functional blocks implemented in the message system 1. As shown in FIG.

As shown in FIG. 9, the message system 1 includes a data storage section 70. For example, the data storage unit 70 is realized by the storage unit 12 of the server 10. Note that the data storage unit 70 may be realized by a storage unit included in another device that is accessible from the server 10.

The data storage unit 70 stores various data. The data storage section 70 includes a registered message data storage section 72 . The registered message data storage section 72 stores registered message data.

The registered message data is data necessary to output (for example, display) a registered message registered in advance. For example, the registered message data includes data necessary to output each of a plurality of registered messages registered in advance. Also, for example, the plurality of registration messages includes at least one object-related registration message.

The "object-related registration message" is a registration message with content related to an object. That is, the object-related registration message is a registration message that is set so that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part. Further, an "object" is an object to be selected by the user. Furthermore, an "object" is something that is displayed on the screen. Further, the "predetermined position" may be, for example, a position determined for each object-related registration message, or may be a fixed position (for example, the beginning position or the end position of the object-related registration message). . Similarly, the "predetermined part" may be, for example, a part determined for each object-related registration message, or may be a fixed part (for example, the beginning or end of an object-related registration message). good.

For example, in the examples shown in FIGS. 2 to 8, the body part object 33, user object 34, or item object 36 corresponds to the "object". Further, for example, a registration message including a <part> tag, <item> tag, or <user> tag corresponds to an "object-related registration message." That is, the registration message indicated by each of the registration message objects 42A to 42E corresponds to an "object-related registration message."

Further, for example, the registered message data includes insertion position information or replacement part information. Further, for example, the registered message data includes object type information.

"Insertion position information" is information indicating a position (hereinafter referred to as "insertion position") where a symbol string related to an object can be inserted in an object-related registration message. In this case, the position indicated by the insertion position information corresponds to the above-mentioned "predetermined position". For example, "insertion position information" is tag information embedded at the insertion position in the object-related registration message. Further, for example, the "insertion position information" may be information indicating how many characters from the beginning (or end) of the object-related registration message the insertion position is. For example, in the examples shown in FIGS. 2 to 8, the <part> tag, <item> tag, or <user> tag corresponds to "insertion position information."

The "replacement part information" includes replacement part information indicating a part of the object-related registration message that can be replaced with a symbol string related to the object (hereinafter referred to as a "replacement part"). In this case, the part indicated by the replacement part information corresponds to the above-mentioned "predetermined part". For example, "replacement part information" is tag information embedded in the above-mentioned replacement part in the object-related registration message. For example, the "replaceable portion information" may be information indicating from which character to which character from the beginning (or end) of the object-related registration message the replacement portion is. For example, in the examples shown in FIGS. 2 to 8, the <part> tag, <item> tag, or <user> tag corresponds to "replacement part information."

"Object type information" is information that can specify the type of object corresponding to the object-related registration message. "The type of object corresponding to the object-related registration message" is the type of object that matches the content of the object-related registration message. In other words, "the type of object corresponding to the object-related registration message" refers to the type of object related to the content of the object-related registration message, the type of object assumed in the content of the object-related registration message, or the type of object The type of object mentioned in the associated registration message.

For example, in the case of the examples shown in FIGS. 2 to 8, the type of object corresponding to the registered message indicated by the registered message objects 42A and 42B is "part". Further, the type of object corresponding to the registered message indicated by the registered message objects 42C and 42D is "item", and the type of object corresponding to the registered message indicated by the registered message object 42E is "user". Furthermore, in the examples shown in FIGS. 2 to 8, the <part> tag, <item> tag, or <user> tag corresponds to "object type information".

10 to 12 show examples of data stored in the data storage section 70 (registered message data storage section 72).

FIG. 10 shows the registration message table. The registered message table is data showing a list of registered messages for each user. The registered message table includes "registered message ID", "registrant", and "registered message" fields.

The "registered message ID" field indicates information that uniquely identifies the registered message. The "registrant" field indicates the user who registered the registration message. The user ID of the user who registered the registration message is registered in the "registrant" field. The "registration message" field indicates the content of the registration message.

FIG. 11 shows the object table. The object table is data that shows a list of objects that can be selected by the user in the game. In other words, the object table is data that shows a list of objects that can be displayed on the screen. The object table includes "object ID", "object type", and "object name" fields.

The "object ID" field indicates information that uniquely identifies an object. The "object type" field indicates the type of object. The "object name" field indicates the name of the object.

FIG. 12 shows the message table. The message table is data showing a list of messages input by each user. The message table includes "message ID", "input person", "input date and time", "message", and "related object" fields.

The "Message ID" field indicates information that uniquely identifies the message input by each user. The "input person" field indicates the user who entered the message. The user ID of the user who entered the message is registered in the "input person" field. The "input date and time" field indicates the date and time when the message was input. The "message" field indicates the content of the message.

The "Related Object" field indicates objects related to the message. For example, a message is generated by replacing a symbol string related to an object with a predetermined part of an object-related registration message (or a message generated by inserting a symbol string related to an object into a predetermined position of an object-related registration message). ), information indicating the object (object ID) is registered in the "related object" field.

As shown in FIG. 9, the message system 1 includes a designation reception section 74, a designation reception result acquisition section 76, and a registration control section 78. Furthermore, the message system 1 includes a change reception section 80, a change reception result acquisition section 82, and an update control section 84. These functional blocks are functional blocks related to registration message settings (new registration or update). For example, the designation receiving section 74 and the change receiving section 80 are realized by the control section 21 and the storage section 22 of the terminal 20. That is, for example, when the control unit 21 executes a program stored in the storage unit 22, the specification reception unit 74 and the change reception unit 80 are realized. Further, for example, the specification reception result acquisition unit 76, the registration control unit 78, the change reception result acquisition unit 82, and the update control unit 84 are realized by the control unit 11 and storage unit 12 of the server 10 (message input reception device). That is, for example, when the control unit 11 executes a program stored in the storage unit 12, the designation reception result acquisition unit 76, the registration control unit 78, the change reception result acquisition unit 82, and the update control unit 84 are realized. .

The designation receiving unit 74 receives the designation of the object-related registration message and the insertion position or the replacement portion from the user via the operation unit 24. The designation reception result acquisition unit 76 acquires the reception result of the designation reception unit 74. For example, the reception result of the designation reception unit 74 is transmitted to the server 10 via the communication unit 23 and received by the server 10 via the communication unit 13. Then, the designated reception result acquisition unit 76 acquires the reception result received via the communication unit 13. The registration control unit 78 generates registration message data indicating the object-related registration message specified by the user and including insertion position information indicating the insertion position specified by the user or replacement part information indicating the replacement part specified by the user. Control is performed to register the message in the registration message data storage section 72.

Further, the change reception unit 80 receives changes to the object-related registration message and the insertion position information or replacement portion information from the user via the operation unit 24. The change reception result acquisition unit 82 acquires the reception result of the change reception unit 80 . For example, the reception result of the change reception unit 80 is transmitted to the server 10 via the communication unit 23 and received by the server 10 via the communication unit 13. Then, the change reception result acquisition unit 82 acquires the reception result received via the communication unit 13. The update control section 84 performs control for updating the registered message data stored in the registered message data storage section 72 based on the reception result of the change reception section 80 .

For example, in the examples shown in FIGS. 2 to 8, the specification reception unit 74 displays the registration screen 60 on the display unit 25, and allows the specification of the object-related registration message and the insertion position or replacement part to be specified on the operation unit 24 ( (touch panel) from the user. Then, when the registration icon 68 on the registration screen 60 is selected, the designation reception unit 74 acquires the message input in the field 62 on the registration screen 60, and transmits data indicating the message to the server 10 as a reception result. 23. The designation reception result acquisition unit 76 acquires the data transmitted by the terminal 20 (designation reception unit 74) via the communication unit 13. The registration control unit 78 registers the message indicated by the acquired data in the registered message data. The operations of the change reception unit 80, change reception result acquisition unit 82, and update control unit 84 are basically the same as those of the designation reception unit 74, designation reception result acquisition unit 76, and registration control unit 78.

As shown in FIG. 9, the message system 1 includes a registered message data acquisition section 86, a registered message selection reception section 88, a registered message selection reception result acquisition section 90, an object selection reception section 92, an object selection reception result acquisition section 94, and a registered message selection reception section 88. It includes an acquisition unit 96. These functional blocks are functional blocks related to message input reception. For example, the registration message selection reception unit 88 and the object selection reception unit 92 are realized by the control unit 21 and storage unit 22 of the terminal 20. That is, for example, when the control unit 21 executes a program stored in the storage unit 22, the registration message selection reception unit 88 and the object selection reception unit 92 are realized. For example, the registered message data acquisition unit 86, registered message selection reception result acquisition unit 90, object selection reception result acquisition unit 94, and message acquisition unit 96 are controlled by the control unit 11 and storage unit 12 of the server 10 (message input reception device). Realized. That is, for example, when the control unit 11 executes the program stored in the storage unit 12, the registered message data acquisition unit 86, the registered message selection reception result acquisition unit 90, the object selection reception result acquisition unit 94, and the message acquisition unit 96 is realized.

The registered message selection acceptance unit 88 accepts a selection of one of the plurality of registered messages from the user via the operation unit 24. The registered message selection reception result acquisition unit 90 acquires the reception result of the registration message selection reception unit 88. For example, the reception result of the registration message selection reception unit 88 is transmitted to the server 10 via the communication unit 23 and received by the server 10 via the communication unit 13. Then, the registration message selection reception result acquisition unit 90 acquires the received reception result.

For example, in the case of the examples shown in FIGS. 2 to 8, the registered message selection reception unit 88 selects one of the registered messages by displaying on the game screen 30 a plurality of registered message objects 42 each representing a plurality of registered messages. A selection from the user is accepted via the operation unit 24 (touch panel). Then, the registration message selection reception unit 88 transmits data indicating the registration message selected by the user to the server 10 via the communication unit 23 as a reception result. The registration message selection reception result acquisition section 90 acquires the above data transmitted by the terminal 20 (registration message selection reception section 88) via the communication section 13.

The object selection reception unit 92 receives a selection of an object displayed on the screen from the user via the operation unit 24. Note that the object selection reception unit 92 may restrict reception of selection of objects of types other than those corresponding to the object-related registration message selected by the user.

As described above, the "type corresponding to the object-related registration message" is, for example, the type of object that matches the content of the object-related registration message.

"Restricting acceptance of object selection" means, for example, setting an object in a state where it cannot be selected. For example, "restricting acceptance of object selection" may mean setting the object in a state where it cannot be selected by not displaying the object on the screen. Note that "restricting acceptance of object selection" means, for example, that even if an object is selected by the user, the device (computer) side refuses to accept the selection or invalidates the selection itself. You can. For example, "restricting acceptance of object selection" may mean, when an object is selected by the user, displaying a warning that the object cannot be selected.

The object selection reception unit 92 also selects an object of the type corresponding to the object-related registration message selected by the user from among the objects displayed on the screen and other objects among the objects displayed on the screen. It may be displayed so that the user can distinguish it.

"Displaying the first object and the second object in a distinguishable manner" means, for example, displaying the first object and the second object so that the user can distinguish them. "Displaying the first object and the second object in a distinguishable manner" includes, for example, the following. (a) A predetermined image (for example, a marker or a frame) is displayed in association with only one of the first object and the second object, and the predetermined image is not displayed in association with the other. (b) Change the display mode (color, brightness, size, shape, type, line type, etc.) of a predetermined image (for example, marker or frame, etc.) displayed in association with the first object to the second object. The display mode is changed to that of a predetermined image that is displayed in association. (c) Changing the display mode (color, brightness, etc.) of the first object itself from the display mode of the second object itself. (d) Displaying the first object in a first predetermined area, and displaying the second object in a second predetermined area different from the first predetermined area. (e) When the first object and the second object are displayed according to the display order, the display order of the first object is set higher than the display order of the second object.

For example, in the case of the examples shown in FIGS. 2 to 8, the object selection reception unit 92 displays the marker 44 in association with each of the plurality of objects displayed on the game screen 30, thereby selecting one of the plurality of objects. The selection is accepted via the operation unit 24 (touch panel).

Here, assume that the registered message object 42A or 42B is selected by the user. The registered messages indicated by the registered message objects 42A and 42B include a <part> tag, and these registered messages are messages related to the enemy's parts.

In this case, the object selection reception unit 92 displays the marker 44 in association with only the part object 33 whose type is "part", and displays the marker 44 in association with other types of objects (i.e., user object 34 and item object 36). 44 is not displayed.

By doing this, the object selection reception unit 92 allows the user to select the type of object (part object 33) corresponding to the registered message selected by the user and other objects (user object 34 and item object 36). It is designed to be displayed in a distinguishable manner.

In addition, by doing the above, the object selection reception unit 92 sets a state in which only the type of object (body part object 33) corresponding to the registered message selected by the user can be selected, and other objects (user object 34 and item object 36) cannot be selected.

Note that when the registered message object 42C or 42D is selected by the user, the registered message indicated by the registered message object 42C or 42D includes an <item> tag, and these registered messages are messages with content related to the item. Therefore, the object selection reception unit 92 displays the marker 44 in association with only the item object 36 whose type is "item".

Furthermore, when the registered message object 42E is selected by the user, the registered message indicated by the registered message object 42E includes a <user> tag, and these registered messages are messages related to the user. The object selection receiving unit 92 displays the marker 44 in association with only the user object 34 whose type is "user".

The object selection reception result acquisition unit 94 acquires the reception result of the object selection reception unit 92. For example, the reception result of the object selection reception unit 92 is transmitted to the server 10 via the communication unit 23 and received by the server 10 via the communication unit 13. Then, the object selection reception result acquisition unit 94 acquires the reception result received via the communication unit 13.

For example, in the examples shown in FIGS. 2 to 8, when any marker 44 is selected by the user, the object selection reception unit 92 receives data indicating the object associated with the marker 44 selected by the user. As a result, it is transmitted to the server 10 via the communication unit 23. The object selection reception result acquisition unit 94 acquires the data transmitted by the terminal 20 (object selection reception unit 92) via the communication unit 13.

The registered message data acquisition unit 86 acquires registered message data stored in the registered message data storage unit 72. The message acquisition unit 96 acquires the message input by the user based on the reception results of the registered message selection reception unit 88 and the object selection reception unit 92.

The message acquisition unit 96 receives a message input by the user, which is obtained by replacing a symbol string associated with at least one object selected by the user with a predetermined part of the object-related registered message selected by the user. Get it as a message. For example, the message acquisition unit 96 acquires a message obtained by replacing a symbol string associated with at least one object selected by the user with a portion of the object-related registration message indicated by the replacement portion information.

Alternatively, the message acquisition unit 96 inputs a message obtained by inserting a symbol string associated with at least one object selected by the user into a predetermined position of the object-related registered message selected by the user. retrieved as a message. For example, the message acquisition unit 96 inputs a message obtained by inserting a symbol string associated with at least one object selected by the user into the position indicated by the insertion position information of the object-related registered message. retrieved as a message.

For example, in the case of the examples shown in FIGS. 2 to 8, the message acquisition unit 96 replaces the name of at least one object selected by the user with a tag included in the object-related registration message selected by the user. The resulting message is obtained as a message input by the user.

The message acquisition section 96 causes the data storage section 70 to store the acquired message. For example, the message acquisition unit 96 registers the acquired message in the message table.

As shown in FIG. 9, the message system 1 includes a message object display control section 98. For example, the message object display control section 98 is realized by the control section 11 of the server 10 (message input reception device).

The message object display control unit 98 performs control to display a message object indicating the message acquired by the message acquisition unit 96 on the screen.

For example, in the case of the examples shown in FIGS. 2 to 8, the message object display control unit 98 transmits data necessary for displaying the message object 48 indicating the message acquired by the message acquisition unit 96 on the game screen 30 to the terminal 20. Send to. In the terminal 20, the message object 48 is displayed on the game screen 30 (display section 25) based on the data transmitted by the server 10 (message object display control section 98).

Next, the processing executed by the message system 1 will be explained.

FIG. 13 is a diagram illustrating an example of a process executed when a user sets a registration message. The control unit 11 executes the processing shown in FIG. 13 according to the program, so that the control unit 11 functions as the designation reception result acquisition unit 76, the registration control unit 78, the change reception result acquisition unit 82, and the update control unit 84. Become. Furthermore, when the control unit 21 executes the processing shown in FIG. 13 according to the program, the control unit 21 functions as the designation reception unit 74 and the change reception unit 80.

As shown in FIG. 13, in this case, the control unit 21 of the terminal 20 requests the server 10 for data on the list screen 50 (S101). Note that "data on the list screen 50" is data for displaying the list screen 50. In step S101, for example, the user ID input by the user using the terminal 20 is transmitted to the server 10.

When the above request is received by the server 10, the control unit 11 of the server 10 refers to the registered message table and obtains a list of registered messages associated with the user ID received from the terminal 20. Then, the control unit 11 transmits data on the list screen 50 showing the acquired list to the terminal 20 (S102).

When the above data is received by the terminal 20, the control unit 21 of the terminal 20 displays the list screen 50 on the display unit 25 (S103). While the list screen 50 is displayed, the control unit 21 monitors whether any setting icon 52 is selected (S104).

If any of the setting icons 52 is selected, the control unit 21 requests the server 10 for data on the registration screen 60 (S105). Note that "data of the registration screen 60" is data for displaying the registration screen 60. In step S105, the registration message ID of the registration message selected by the user is transmitted to the server 10 together with the user's user ID.

When the above request is received by the server 10, the control unit 11 of the server 10 transmits the data on the registration screen 60 to the terminal 20 (S106). When this data is received by the terminal 20, the control unit 21 of the terminal 20 displays the registration screen 60 on the display unit 25 (S107).

While the registration screen 60 is displayed, the control unit 21 updates the message displayed in the field 62 based on the user's operation. That is, the control unit 21 updates the message displayed in the field 62 according to operations related to the virtual keyboard 64 and the tag icon 66. Further, the control unit 21 monitors whether the registration icon 68 is selected (S108).

If the registration icon 68 is selected, the control unit 21 transmits message data to the server 10 (S109). Here, "message data" is data indicating a message input into field 62. Note that in step S109, the message data is transmitted to the server 10 together with the user ID of the user and the registered message ID of the registered message selected on the list screen 50.

When the message data is received by the server 10, the control unit 11 of the server 10 updates the registered message table (S110). For example, the registered message selected on the list screen 50 is updated to the message entered in the field 62 of the registration screen 60. That is, the registration message associated with the registration message ID received from the terminal 20 is updated to the message input in the field 62 of the registration screen 60.

Thereafter, the control unit 11 refers to the registered message table and obtains a list of registered messages associated with the user ID received from the terminal 20. Then, the control unit 11 transmits data on the list screen 50 showing the acquired list to the terminal 20 (S111). In this case, based on this data, the control unit 21 of the terminal 20 displays the list screen 50 on the display unit 25 (S112). The updated registration message is displayed on the list screen 50.

FIG. 14 is a diagram showing an example of a process executed when chat icon 40 on game screen 30 is selected. When the control unit 11 executes the processing shown in FIG. 14 according to the program, the control unit 11 operates the registered message data acquisition unit 86, the registration message selection reception result acquisition unit 90, the object selection reception result acquisition unit 94, the message acquisition unit 96, It also functions as a message object display control section 98. Furthermore, when the control unit 21 executes the processing shown in FIG. 14 according to the program, the control unit 21 functions as the registration message selection reception unit 88 and the object selection reception unit 92.

As shown in FIG. 14, the control unit 21 of the terminal 20 requests registration message data from the server 10 (S201). In step S201, for example, the user ID input by the user using the terminal 20 is transmitted to the server 10.

When the above request is received by the server 10, the control unit 11 of the server 10 refers to the registration message table and obtains the registration message associated with the user ID received from the terminal 20. Then, the control unit 11 transmits data indicating the acquired registration message to the terminal 20 as registration message data (S202).

When the registered message data is received by the terminal 20, the control unit 21 of the terminal 20 displays the registered message object 42 on the game screen 30 based on the registered message data (S203). Then, the control unit 21 monitors whether any registration message has been selected (S204). That is, the control unit 21 monitors whether any registered message object 42 has been selected.

If any registered message is selected, the control unit 21 determines whether the selected registered message is an object-related registered message (S205). For example, the control unit 21 determines whether the selected registration message includes a tag. If the registration message includes a tag, the control unit 21 determines that the selected registration message is an object-related registration message. On the other hand, if the registration message does not include a tag, the control unit 21 determines that the selected registration message is not an object-related registration message.

If the selected registration message is not an object-related registration message, the control unit 21 transmits the input message data to the server 10 (S208). The "input message data" in this case is data indicating the selected registered message. For example, the registered message ID of the selected registered message is sent to the server 10 as input message data. Note that in this case, the user's user ID is also transmitted to the server 10.

When the above input message data (registered message ID) is received by the server 10, the control unit 11 of the server 10 acquires the message input by the user (S209). For example, the control unit 11 refers to the registered message table and acquires the registered message associated with the received registered message ID as the message input by the user. Then, the control unit 11 additionally registers the message acquired in step S209 in the message table (S210).

On the other hand, if it is determined in step S205 that the selected registration message is an object-related registration message, the control unit 21 displays the marker 44 on the game screen 30 (S206).

For example, the control unit 21 specifies the type of object corresponding to the selected registration message (object-related registration message). For example, the type of object corresponding to the registration message is specified based on the type of tag included in the registration message. For example, if the <part> tag is included in the registration message, the type of object corresponding to the registration message is specified as "part".

Then, the control unit 21 displays the marker 44 in association with the type of object identified as described above. For example, when the type of the identified object is a "part", the control unit 21 displays the marker 44 in association with the part object 33 indicating the part. In this case, the control unit 21 does not display the marker 44 in association with an object that does not indicate a body part. That is, the control unit 21 does not display the marker 44 in association with the user object 34 and the item object 36.

After step S206 is executed, the control unit 21 monitors whether any object has been selected (S207). That is, the control unit 21 monitors whether any marker 44 has been selected.

If any object is selected, the control unit 21 transmits the input message data to the server 10 (S208). For example, the "input message data" in this case is data indicating both the selected registered message and the selected object. For example, a combination of the registered message ID of the selected registered message and the object ID of the selected object is transmitted to the server 10 as input message data. Note that in this case, the user's user ID is also transmitted to the server 10.

When the above input message data (registered message ID and object ID) is received by the server 10, the control unit 11 of the server 10 acquires the message input by the user (S209).

For example, the control unit 11 refers to the registration message table and obtains the registration message associated with the received registration message ID. The control unit 11 also refers to the object table and obtains the object name associated with the received object ID. Then, the control unit 11 replaces the tag included in the acquired registration message with the acquired object name. The control unit 11 acquires the message obtained in this way as a message input by the user.

Then, the control unit 11 additionally registers the message acquired in step S209 in the message table (S210).

After step S210 is executed, the control unit 11 transmits message object data to the terminal 20 (S211). Note that the "message object data" is data necessary for displaying the message object 48 indicating the message acquired in step S209. Furthermore, although omitted in FIG. 14, the message object data is transmitted not only to the terminal 20 of the user who inputs the message, but also to the terminals 20 of other users. Then, in each terminal 20, a message object 48 indicating the message acquired in step S209 is displayed on the game screen 30 based on the message object data (S212).

According to the message system 1 described above, the user can input a message with content suitable for the current situation. For example, in a situation where the user should attack the enemy's left arm, the user can input a message inviting other users to attack the enemy's left arm. That is, according to the message system 1, it is possible to ensure flexibility regarding message contents.

Further, according to the message system 1, the user can input a message suitable for the current situation as described above by selecting a registered message and an object. For example, in the case of the examples shown in FIGS. 2 to 5, the user selects the registered message object 42A and part object 33B (marker 44B) to input a message calling on other users to attack the enemy's left arm. can do. In other words, the user can input the above message without having to type the message each time. That is, according to the message system 1, it is possible to shorten the time required to input a message as described above.

As described above, according to the message system 1, it is possible to reduce the time required to input a message while ensuring flexibility regarding message content.

Further, in the message system 1, the marker 44 is displayed in association with only the type of object corresponding to the registered message selected by the user. According to the message system 1, it is possible to prevent the user from accidentally selecting an object that does not match the content of the registered message selected by the user.

Furthermore, the message system 1 allows the user to arbitrarily set registered messages (message content, tag position, and type). According to the message system 1, a user can assume a situation when inputting a message and set the content of a pre-registered message to a desired content that matches the situation.

Note that the present invention is not limited to the embodiments described above.

[Modification 1] For example, when the user is not able to select the body part object 33, such as when the current scene is not a battle scene with an enemy, the registration message selection reception unit 88 selects the registration message corresponding to the body part. Messages may not be selectable. That is, the registered message selection reception unit 88 may be configured to prevent the registered message objects 42A and 42B from being selected.

Furthermore, when the user cannot select the part object 33, the registered message selection reception unit 88 may display the registered message corresponding to the part and other registered messages so that the user can distinguish them. That is, the registered message selection receiving unit 88 may display the registered message objects 42A, 42B and the registered message objects 42C to 42E so that the user can distinguish them.

As described above, the registration message selection reception unit 88 may restrict reception of selection of registration messages corresponding to types of objects that cannot be selected by the user.

Further, the registered message selection reception unit 88 displays a registered message corresponding to a type of object that can be selected by the user and a registered message corresponding to a type of object that cannot be selected by the user so that the user can distinguish between the registered message and the registered message corresponding to the type of object that is not selectable by the user. Good too.

Note that here, the "user-selectable object" is, for example, an object displayed on the screen (an object that can be displayed on the screen). For example, the object currently displayed on the screen is a "user selectable object." Further, for example, an object that is not currently displayed on the screen but is displayed as the screen scrolls (or transitions) is a "user-selectable object." On the other hand, objects that are not displayed on the screen even if the screen is scrolled are "objects that cannot be selected by the user."

For example, when a virtual space viewed from a virtual viewpoint is displayed on the screen, objects arranged in the virtual space are "objects that can be selected by the user." On the other hand, objects that are not placed in the virtual space are "objects that cannot be selected by the user."

Note that even if you consider only the objects currently displayed on the screen as "object types that can be selected by the user," and the objects that are not currently displayed on the screen as "object types that can be selected by the user," good. Similarly, only objects placed in the visual field of the virtual viewpoint are considered "objects that can be selected by the user," and objects that are not placed in the visual field of the virtual viewpoint are considered "objects that cannot be selected by the user." You may also do so.

Further, "restricting acceptance of selection of registered messages" is not limited to setting a state in which registered messages cannot be selected. For example, "restricting acceptance of selection of registered messages" may mean setting a state in which registered messages cannot be selected by not displaying registered messages on the screen. Note that "restricting acceptance of object selection" means, for example, that even if a registered message is selected by the user, the device (computer) may refuse to accept the selection or invalidate the selection itself. There may be. For example, "restricting acceptance of selection of registered messages" may mean, when a registered message is selected by a user, displaying a warning that the registered message cannot be selected.

Furthermore, "displaying the first registered message and the second registered message in a distinguishable manner" means, for example, displaying the first registered message and the second registered message in a way that allows the user to distinguish them. be. "Displaying the first registration message and the second registration message so that the user can distinguish them" includes, for example, the following. (a) A predetermined image (for example, a marker or a frame, etc.) is displayed in association with only one of the first registered message and the second registered message, and the predetermined image is not displayed in association with the other. (b) The display mode (color, brightness, size, shape, type, type of line, etc.) of a predetermined image (for example, a frame or a speech bubble) displayed in association with the first registered message can be changed to a second object. The display mode of the predetermined image displayed in association with the predetermined image is changed. (c) Changing the display mode (color, brightness, font, etc.) of the first registration message itself from the display mode of the second registration message itself. (d) Displaying the first registration message within the first predetermined area, and displaying the second registration message within a second predetermined area different from the first predetermined area. (e) When displaying the first registered message and the second registered message according to the display order, the display order of the first registered message is set higher than the display order of the second registered message.

By doing the above, the selection of registered messages that correspond to object types that cannot be selected by the user is restricted, so that the user may accidentally select a registered message that is related to an object that cannot be selected by the user. It is possible to avoid being put away. As a result, it is possible to avoid inputting inappropriate messages.

Furthermore, by doing the above, registration messages corresponding to object types that can be selected by the user and registration messages corresponding to object types that cannot be selected by the user can be displayed so that the user can distinguish them. Therefore, it becomes possible to prompt the user to select a registration message whose contents match the objects that the user can select.

[Modification 2] For example, in the embodiment described above, the user selects any object after selecting any registration message (see FIGS. 3 to 5). After the user selects any object, the user may select any registration message.

For example, when the chat icon 40 on the game screen 30 shown in FIG. 2 is selected, the game screen 30 as shown in FIG. 15 may be displayed. On the game screen 30 shown in FIG. 15, markers 44A to 44J are displayed in association with body part objects 33A to 33C, user objects 34A to 34D, and item objects 36X to 36Z, respectively.

In this case, the user selects one of the objects by selecting one of the markers 44A to 44J displayed on the game screen 30. FIG. 16 shows an example of the game screen 30 when any object is selected. On the game screen 30 shown in FIG. 16, registered message objects 42A to 42F each representing a plurality of registered messages are displayed. Note that FIG. 16 shows the game screen 30 when the marker 44B is selected (that is, when the part object 33B indicating the left arm is selected).

On the game screen 30 shown in FIG. 16, a registration message corresponding to the type of object selected by the user and other registration messages may be displayed so that the user can distinguish them.

For example, when the part object 33 is selected by the user, registered message objects 42A and 42B indicating registered messages corresponding to the part and other registered message objects 42C to 42F are displayed so that the user can distinguish them. You can. For example, as shown in FIG. 16, the registered message objects 42A and 42B may be displayed as solid lines, and the registered message objects 42C to 42F may be displayed as dotted lines.

Further, on the game screen 30 shown in FIG. 16, acceptance of selection of registered messages other than the registered message corresponding to the type of object selected by the user may be restricted.

For example, when the body part object 33 is selected by the user, only one of the registered message objects 42A and 42B indicating the registered message corresponding to the body part can be selected, and the registered message objects 42C to 42F cannot be selected. You may also do so.

With the above method, acceptance of the selection of registered messages corresponding to the type of object selected by the user is restricted, so the user may accidentally select a registered message with content that does not match the object selected by the user. It is possible to avoid doing this. As a result, it is possible to avoid inputting inappropriate messages.

In addition, by doing the above, the registered message corresponding to the type of object selected by the user and other registered messages will be displayed so that the user can distinguish them. It becomes possible to prompt the user to select a registered message with matching content.

[Modification 3] For example, the message object 48 shown in FIG. 6 may be displayed in association with the part object 33B representing the left arm. Message object 48 shown in FIG. 6 shows a message obtained by replacing the <part> tag included in the registration message shown by registration message object 42A with the object name (left arm) of part object 33B. Therefore, the message object 48 shown in FIG. 6 may be displayed in association with the part object 33B representing the left arm.

FIG. 17 shows an example of the game screen 30 in this case. On the game screen 30 shown in FIG. 17, a line 100 (dotted line) connecting the message object 48 and the part object 33B is displayed. By displaying such a line 100, the user can understand at a glance that the message indicated by the message object 48 is related to the left arm.

As described above, the message object 48 is a message obtained by replacing a symbol string associated with the object selected by the user with a predetermined part of the registered message, or a message associated with the object selected by the user. When indicating a message obtained by inserting a symbol string into a predetermined position of a registered message, the message object display control unit 98 controls to display the message object 48 in association with the selected object. You may also do so.

Here, "displaying a message object in association with an object" means displaying the message object so that the user can understand that it is related to the object. For example, "displaying a message object in association with an object" means displaying a line or an image that associates a message object with an object, as shown in FIG.

By doing the above, the message object 48 displayed on the game screen 30 will be displayed in association with the object displayed on the game screen 30, so the user can determine which object the message indicated by the message object 48 corresponds to. It becomes easier to understand whether something is related.

[Modification 4] For example, step S209 in FIG. 14 may be executed on the terminal 20 side. That is, step S209 may be executed before step S208 is executed.

For example, if it is determined in step S207 that any object has been selected, the control unit 21 of the terminal 20 may obtain the message as a message input by the user. In this case, for example, an object table is stored in the storage unit 22 in advance, and the control unit 21 refers to the object table stored in the storage unit 22 and determines the object name associated with the object selected in step S207. get. Then, the control unit 21 replaces the tag included in the registration message selected in step S204 with the obtained object name. The control unit 21 acquires the message obtained in this manner as a message input by the user. Then, the control unit 21 transmits input message data indicating the message to the server 10 (S208).

For example, if it is determined in step S205 that the registered message selected in step S204 is not an object-related registered message, the control unit 21 acquires the registered message selected in step S204 as a message input by the user. You may also do so. In this case, the control unit 21 transmits input message data indicating the message to the server 10 (S208).

FIG. 18 shows a functional block diagram in this case. As shown in FIG. 18, in this case, the registered message data acquisition unit 86, registered message selection reception result acquisition unit 90, object selection reception result acquisition unit 94, and message acquisition unit 96 control the terminal 20 (message input reception device). This will be realized by the section 21.

[Modification 5] In Modification 4, the registered message data storage section 72 may be realized by the terminal 20 (message input reception device). For example, user A's registration message may be stored in the storage unit 22 of user A's terminal 20.

Further, in this case, the designation reception result acquisition unit 76, the registration control unit 78, the change reception result acquisition unit 82, and the update control unit 84 may also be implemented in the terminal 20 (message input reception device).

Note that since the message object 48 is displayed on the display unit 25 by the control unit 21 of the terminal 20, the message object display control unit 98 can also be considered to be realized by the terminal 20 (message input reception device).

[Other variations] For example, in the embodiment described above, the tag included in the registration message selected by the user is replaced with the name of the object acquired by the user. The tag may be inserted into the name of the object obtained by the user after or before the tag included in the registered registration message. In this case, the tag will remain in the message, but the tag may be ignored when displaying the message object 48. That is, when displaying the message object 48, the tag may not be displayed.

Further, for example, on the game screen 30 shown in FIG. 4, a plurality of markers 44 (that is, a plurality of body part objects 33) may be selectable.

Further, for example, only one marker 44 may be displayed on the game screen 30 shown in FIG. 4. For example, only one object selectable by the user may be displayed on the game screen 30.

Further, for example, it is not essential to display the marker 44 on the game screen 30 shown in FIG. 4, and the marker 44 may not be displayed. For example, on the game screen 30 shown in FIG. 4, the user may directly specify any one of the plurality of body part objects 33.

Furthermore, for example, the registration message does not need to be set for each user. For example, a registration message common to all users may be set in advance. Further, in this case, the designation reception unit 74, designation reception result acquisition unit 76, registration control unit 78, change reception unit 80, change reception result acquisition unit 82, and update control unit 84 may be omitted.

Further, for example, on the game screen 30 shown in FIG. 6, a message object 48 indicating a message input by the user is displayed, but the message input by the user may be outputted as voice. . Further, in this case, the data for audio outputting the message input by the user may be generated by the terminal 20 of the user who inputs the message, or may be generated by the server 10. However, the message may be generated by the terminal 20 that outputs the message.

Furthermore, for example, the games executed by the message system 1 are not limited to the games described above. For example, a plurality of enemy objects 32 may be displayed on the game screen 30. Then, the user may select one of the enemy objects 32 as an attack target. In this case, an <enemy> tag may be included in the registration message instead of the <part> tag.

Also, for example, the case where a plurality of users chat while playing a game has been described above. That is, a case has been described in which the present invention is applied to a game system that realizes a game in which a plurality of users participate. However, the present invention can also be applied to systems other than game systems. That is, the present invention can also be applied to a system in which a plurality of users chat regardless of the game. In short, the present invention can be applied to various systems in which a user inputs a message addressed to another person.

For example, when the user selects a building (object) on a map of the real world displayed on the screen, a message may be input in which the name of the building is inserted or replaced. For example, a registered message (object-related registered message) with a <place> tag such as "Let's go to <place>!" may be registered. Then, when the user selects Building A on the real world map displayed on the screen, the message "Let's go to Building A!" with the <location> tag replaced with the building name "Building A" is displayed. It may also be configured to be input.

Furthermore, for example, when the user selects a movie icon (object) displayed on the screen, a message may be input in which the name of the movie is inserted or replaced. For example, a registered message (object-related registered message) with a <movie> tag such as "Did you see <movie>?" may be registered. Then, when the user selects the movie icon for movie A displayed on the screen, the message ``Did you see movie A?'' with the <movie> tag replaced with the movie name ``Movie A'' will be input. You may also do so.

Further, for example, a program for realizing the functional blocks shown in FIG. 9 or FIG. 18 may be a part of an application program (for example, a game program that executes a game), or may be a separate program from the application program. There may be. For example, a program for implementing the functional blocks shown in FIG. 9 or 18 may be provided as middleware for providing message functions to various application programs (eg, game programs). Further, for example, a program for realizing the functional blocks shown in FIG. 9 or 18 may be provided as part of the operating system of the server 10 or the terminal 20.

[Summary of the Invention] From the above description, the present invention can be understood as follows, for example. Note that, in the following description, in order to facilitate understanding of the present invention, the symbols appearing in the drawings are written in parentheses, but the present invention is not limited to the illustrated embodiments.

The message input receiving device (10 or 20) according to the present invention is a registered message that is registered in advance, and is an object that is set so that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part. registered message data acquisition means (86) for acquiring registered message data stored in registered message data storage means (72) for storing registered message data indicating related registered messages; An object selection reception result acquisition means (94) that acquires the reception result of the object selection reception means (92) received from the user, and a symbol string associated with at least one object selected by the user in the object related registration message. and a message obtaining means (96) for obtaining a message obtained by inserting the message into the predetermined position or replacing the predetermined portion of the message as a message input by the user.

The message system (1) according to the present invention includes an object-related registration message that is registered in advance and is set such that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part. registered message data acquisition means (86) for acquiring the registered message data stored in the registered message data storage means (72) for storing the registered message data shown in FIG. an object selection reception result acquisition means (94) for acquiring the reception result of the selection reception means (92); and a symbol string associated with at least one object selected by the user at the predetermined position of the object-related registration message. Message acquisition means (96) for acquiring a message obtained by inserting or replacing the predetermined portion into the message input by the user.

The program according to the present invention is a registration message registered in advance, and registration message data indicating an object-related registration message set such that a symbol string related to at least one object can be inserted at a predetermined position or replaced with a predetermined part. registered message data acquisition means (86) for acquiring the registered message data stored in the registered message data storage means (72) for storing the registered message data; and object selection reception means (92) for accepting from the user a selection of objects to be displayed on the screen. an object selection reception result acquisition means (94) for acquiring a reception result of the object selection reception result, and inserting a symbol string associated with at least one object selected by the user into the predetermined position of the object-related registration message; This is a program for causing a computer to function as a message acquisition means (96) for acquiring a message obtained by replacing a predetermined part as a message input by the user.

Further, an information storage medium according to the present invention is a computer-readable information storage medium on which the above program is recorded.

According to the present invention, by selecting an object in consideration of the current situation, the user can input a message that matches the current situation. Moreover, it becomes possible to shorten the time required to input a message. That is, it is possible to reduce the time required to input a message while ensuring flexibility regarding message content.

In one aspect of the present invention, the registration message data includes insertion position information indicating a position where the symbol string can be inserted in the object-related registration message, or insertion position information that can be replaced with the symbol string in the object-related registration message. The message acquisition means (96) inserts the symbol string into the position indicated by the insertion position information of the object-related registration message, or replaces the symbol string with the part indicated by the replacement part information. The message obtained by doing this may also be obtained. In this way, it becomes possible to set the position at which a symbol string related to at least one object is inserted or the portion to be replaced with a symbol string for each object-related registration message. As a result, it becomes possible to input a message with more appropriate content.

In one aspect of the present invention, a reception result of a designation receiving means (74) that receives from the user a designation of the object-related registration message and a position where the symbol string can be inserted or a part that can be replaced with the symbol string. a specification reception result acquisition means (76) to obtain, an object-related registration message specified by the user, and the insertion position information indicating a position specified by the user or a portion specified by the user; It may also include a registration control means (78) that performs control to register registered message data including the replaced part information in the registered message data storage means (72). In this way, it becomes possible for the user to register in advance the content of the object-related registration message, the position at which the symbol string is inserted, or the portion to be replaced with the symbol string. As a result, it becomes possible for the user to imagine the situation when inputting a message and to pre-register a message with desired content suitable for that situation.

In one aspect of the present invention, a change reception result acquisition means ( 82), and update control means (82) that performs control to update the registered message data stored in the registered message storage means (72) based on the reception result acquired by the change reception result acquisition means (82). 84). In this way, it becomes possible for the user to change the content of the object-related registration message, the position at which the symbol string is inserted, or the portion to be replaced with the symbol string. As a result, the user can assume the situation in which the message will be input and change the content of the message registered in advance to the desired content that matches the situation.

In one aspect of the present invention, the registered message data indicates a plurality of registered messages registered in advance, at least one of the plurality of registered messages is the object-related registered message, and the message input reception device (10 or 20) includes a registration message selection reception result acquisition means (90) for acquiring a reception result of a registration message selection reception means (88) for accepting a selection of one of the plurality of registration messages from the user; The message acquisition means (96) acquires the message input by the user based on the reception result acquired by the registered message selection reception result acquisition means (90), and the message acquisition means (96) acquires the message input by the user. When the object-related registration message is selected by a user, inserting a symbol string associated with at least one object selected by the user into the predetermined position of the object-related registration message selected by the user. Alternatively, a message obtained by replacing the predetermined portion may be obtained as the message input by the user. In this way, the user can select the content of the message to be input from among a plurality of registered messages. As a result, the user can select a registered message with desired content that matches the current situation from among the plurality of registered messages.

In one aspect of the present invention, the registration message data includes object type information that can specify the type of object corresponding to the object-related registration message, and the object selection accepting means (92) Acceptance of selection of objects of types other than those corresponding to the object-related registration message may be restricted. In this way, acceptance of selections of objects other than those corresponding to the object-related registration message selected by the user will be restricted, so for example, objects that do not match the content of the object-related registration message selected by the user will be restricted. Acceptance of object selection is now restricted. As a result, it is possible to prevent the user from accidentally selecting an object that does not match the content of the object-related registration message selected by the user. That is, it is possible to avoid inputting an inappropriate message in which the content of the message does not match the symbol string to be inserted or replaced.

In one aspect of the present invention, the registration message data includes object type information that can specify the type of object corresponding to the object-related registration message, and the object selection receiving means (92) Among the objects, an object of a type corresponding to the object-related registration message selected by the user and other objects among the objects displayed on the screen are displayed so that the user can distinguish them. Good too. In this way, the type of object corresponding to the object-related registration message selected by the user and other objects will be displayed so that the user can distinguish between them. Objects that match the content of the message and objects that do not match the content of the object-related registration message selected by the user are displayed so that the user can distinguish them. As a result, it becomes possible to prompt the user to select an object that matches the content of the object-related registration message selected by the user.

In one aspect of the present invention, the registration message data includes object type information that can specify the type of object corresponding to the object-related registration message, and the registration message selection reception means (92) Acceptance of selection of registration messages other than the object-related registration message corresponding to the type of object selected by the user may be restricted. In this way, the selection of registered messages other than object-related registered messages corresponding to the type of object selected by the user will be restricted, so for example, the selection of registered messages that do not match the object selected by the user will be restricted. Reception of selection of object-related registration messages is now restricted. As a result, it is possible to prevent the user from accidentally selecting an object-related registration message whose content does not match the object selected by the user. That is, it is possible to avoid inputting an inappropriate message in which the content of the message does not match the symbol string to be inserted or replaced.

In one aspect of the present invention, the registration message data includes object type information that can specify the type of object corresponding to the object-related registration message, and the registration message selection reception means (88) The object-related registered message corresponding to the type of object selected by the user and other registered messages among the plurality of registered messages may be displayed so that the user can distinguish them. In this way, the object-related registered message corresponding to the type of object selected by the user and other registered messages are displayed in a way that allows the user to distinguish between the object-related registered message and other registered messages. The related registration message is displayed so that the user can distinguish it from the object related registration message whose contents do not match the object selected by the user. As a result, it becomes possible to prompt the user to select an object-related registration message whose content matches the object selected by the user.

In one aspect of the present invention, the registration message data includes object type information that can specify the type of object corresponding to the object-related registration message, and the message input receiving device (10 or 20) is configured to register the object-related registration message. The message acquisition means (96) includes a symbol string associated with at least one object selected by the user. is inserted into the predetermined position of the object-related registration message selected by the user, or a message obtained by replacing the predetermined part is obtained as a message input by the user, and is selectable by the user. Acceptance of selection of object-related registration messages corresponding to object types other than those listed above may be restricted. In this way, acceptance of selection of object-related registration messages corresponding to object types that are not selectable by the user is restricted, and the user is prevented from accidentally receiving object-related registration messages that are related to objects that cannot be selected by the user. It is possible to avoid making choices. As a result, it is possible to avoid inputting an inappropriate message in which the content of the message does not match the symbol string to be inserted or replaced.

In one aspect of the present invention, the registration message data includes object type information that can specify the type of object corresponding to the object-related registration message, and the message input reception device selects the object-related registration message. The message acquiring means (96) includes a means (90) for acquiring a reception result of the means (88) for accepting from a user, and the message acquiring means (96) receives a symbol string associated with at least one object selected by the user by the user. A message obtained by inserting into the predetermined position or replacing the predetermined part of the selected object-related registration message is obtained as a message input by the user, and the message is set as a type of object selectable by the user. A corresponding object-related registration message and an object-related registration message corresponding to a type of object that cannot be selected by the user among the plurality of messages may be displayed so that the user can distinguish them. In this way, the object-related registration messages corresponding to the object types that the user can select and the object-related registration messages corresponding to the object types that the user cannot select can be displayed so that the user can distinguish them. Therefore, it becomes possible to prompt the user to select an object-related registration message whose contents match the objects that the user can select.

In one aspect of the present invention, message object display control means (98) performs control to display a message object indicating a message acquired by the message acquisition means (96) on a screen on which one or more objects are displayed. ), the message object display control means (98) inserts a symbol string associated with the object selected by the user into the predetermined position of the object-related registration message or replaces the predetermined part with the object-related registration message. Control may be performed to display a message object indicating the obtained message in association with the selected object. In this way, the message object displayed on the screen will be displayed in association with the object displayed on the screen, making it easier to understand which object the message object is related to.

1 message system, 2 communication network, 10 server, 11, 21 control unit, 12, 22 storage unit, 13, 23 communication unit, 20 terminal, 24 operation unit, 25 display unit, 30 game screen, 32 enemy object, 33A, 33B, 33C Part object, 34A, 34B, 34C, 34D User object, 36X, 36Y, 36Z Item object, 38 Attack icon, 40 Chat icon, 42A, 42B, 42C, 42D, 42E, 42F Registered message object, 44A, 44B , 44C, 44D, 44E, 44F, 44G, 44H, 44I, 44J Marker, 46 Send icon, 48 Message object, 50 List screen, 52A, 52B, 52C, 52D, 52E, 52F Settings icon, 60 Registration screen, 62 Form , 64 virtual keyboard, 66A, 66B, 66C tag icon, 68 registration icon, 70 data storage section, 72 registration message data storage section, 74 specification reception section, 76 specification reception result acquisition section, 78 registration control section, 80 change reception section , 82 change reception result acquisition unit, 84 update control unit, 86 registered message data acquisition unit, 88 registered message selection reception unit, 90 registration message selection reception result acquisition unit, 92 object selection reception unit, 94 object selection reception result acquisition unit, 96 Message acquisition unit, 98 Message object display control unit, 100 Line.

Claims (4)

a first acquisition means for acquiring a selected message selected by a first operation from among the plurality of candidate messages;
a second acquisition means for acquiring a selected object selected by a second operation from among a plurality of objects displayed as the game progresses;
a message object indicating an acquired message obtained by inserting a symbol string associated with the selection object into a predetermined position of the selection message or replacing a predetermined part of the selection message; and the selection object; a generation means for generating data for displaying on a terminal in association with the
A message system including: The generating means further associates the message object with a speaker object indicating a speaker of the obtained message and generates the data for displaying on the terminal.
Message system according to claim 1. A program for causing a computer to function as the message system according to claim 1 or 2. a first acquisition step of acquiring a selected message selected by a first operation from among the plurality of candidate messages;
a second acquisition step of acquiring a selected object selected by a second operation from among a plurality of objects displayed as the game progresses;
a message object indicating an acquired message obtained by inserting a symbol string associated with the selection object into a predetermined position of the selection message or replacing a predetermined part of the selection message; and the selection object; a generation step of generating data for displaying on a terminal by associating the
Message generation methods, including:

Images