Method for establishing relationship title-related table, method and device for relationship title management

By establishing related tables and management methods for relationship titles, the problem that ordinary title systems cannot meet personalized needs is solved, and the management and display of relationship titles is realized, which improves the game experience and player activity.

CN114405003BActive Publication Date: 2025-06-13BEIJING PIXEL SOFTWARE TECH
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202111667621.1
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2021-12-31
Publication Date
2025-06-13
Estimated Expiration
2041-12-31

AI Technical Summary

Technical Problem

The ordinary title system in the existing large-scale multiplayer online role-playing game cannot meet the personalized needs of players, resulting in a decrease in freshness and a decrease in player activity.

Method used

By establishing related tables of relationship titles, including title category tables, title tables and title extension information tables, adding title type IDs and extension information table ID columns, deleting redundant columns, and realizing the management and display of relationship titles.

Benefits of technology

It has achieved the addition of relationship titles based on the existing ordinary title system to meet the personalized needs of players, improve the gaming experience, and increase the activity and freshness of players.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114405003B_ABST
    Figure CN114405003B_ABST
Patent Text Reader

Abstract

The present application provides a method and device for establishing a related table of relationship titles and managing relationship titles. By obtaining a title category table and a title table related to a general title system, a new title extension information table is created. An extension information table ID column for associating with the title extension information table is added to the title table, and redundant columns in the title table are deleted according to each column information in the target title category table to obtain a target title table. A title type ID column for associating with the title extension information table is added to the title category table to obtain a target title category table. When adding a relationship title, the relationship title is added based on the target title category table, the target title table, and the title extension information table. The present application can flexibly add personalized tabs by configuring tables on the basis of existing general titles, bringing a better gaming experience to users and improving the activity and freshness of game players.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of online games, and particularly to a method for establishing a relationship title-related table, a method for managing a relationship title, and a device therefor. Background Art

[0002] A massively multiplayer online role-playing game (MMORPG) generally includes a title system, and the titles included therein are ordinary titles with fixed names and appearances pre-set in the game. Although there are ordinary titles in the game, the ordinary titles can only achieve basic title functions and cannot allow players to flexibly add personalized tabs. As the game operation progresses, the freshness of players becomes lower and lower, and the ordinary titles cannot meet the growing personalized needs. Summary of the Invention

[0003] In view of the above problems, the present application proposes a method for establishing a relationship title-related table, a method for managing a relationship title, and a device therefor.

[0004] The present application proposes a method for establishing a relationship title-related table, the method comprising:

[0005] Obtaining a title category table and a title table related to an ordinary title system;

[0006] Creating a new title extension information table;

[0007] Adding a title type ID column for associating with the title extension information table to the title category table to obtain a target title category table;

[0008] Adding an extension information table ID column for associating with the title extension information table to the title table, and deleting redundant columns in the title table according to each column information in the target title category table to obtain a target title table.

[0009] In the method for establishing a relationship title-related table according to the present application, deleting redundant columns in the title table according to each column information in the target title category table includes:

[0010] Obtaining each column name in the target title category table;

[0011] Obtaining each column name in the title table;

[0012] Comparing each column name in the target title category table with each column name in the title table, and deleting the same columns from the title table between the target title category table and the title table.

[0013] The above method for establishing a relationship title related table, wherein the target title category table includes a target title category table ID column, a type ID column, a parent category ID column, and a title type ID column, and the title extension information table includes an extension information table ID column, a title subtype ID column, and a title type ID column, further comprising:

[0014] Determine the title type ID and the title subtype ID according to the relationship system corresponding to the relationship title to be added;

[0015] Add the title type ID to the title type ID column;

[0016] Determine the addition information for the target title category table ID column, the type ID column, and the parent category ID column according to the current information of the target title category table, and add the corresponding addition information to the target title category table ID column, the type ID column, and the parent category ID column respectively;

[0017] Determine the addition information for the extension information table ID column according to the current information of the title extension information table, and add the corresponding addition information to the extension information table ID column;

[0018] Add the title subtype ID to the title subtype ID column.

[0019] The present application proposes a method for managing relationship titles. The target title table includes a title ID column, a name text ID column, a picture ID column, a particle ID column, an extension information table ID column, a subcategory ID column, and a description text ID column. The target title category table includes a target title category table ID column, a type ID column, a parent category ID column, a name text ID column, and a title type ID column. The title extension information table includes the extension information table ID column, a title type ID column, and a title subtype ID column. The method includes:

[0020] When receiving a display instruction, obtain the current title type ID and the current title ID corresponding to the current relationship title;

[0021] Obtain general title information from the target title table, the target title category table, and the title extension information table through the current title ID. The general title information includes a name text ID, a picture ID, a particle ID, an extension information table ID, a subcategory ID, and a description text ID. Determine the current title type according to the current title type ID;

[0022] When the current title type is a general title type, display the corresponding general title based on the general title information. The target title table, the target title category table, and the title extension information table are obtained by using the above method for establishing a relationship title related table.

[0023] A method for managing relationship titles described in this application further includes:

[0024] When the current title type is a relationship title type, obtain the current target ID corresponding to the current relationship title, obtain relationship title information from the corresponding relationship system through the current target ID, and display the corresponding relationship title based on the general title information and the relationship title information. The relationship title information includes a target name and a title subtype ID.

[0025] A method for managing relationship titles described in this application further includes:

[0026] When the current title type is the general title type, store the current title ID and the current title type ID.

[0027] The above method for managing relationship titles further includes:

[0028] When the current title type is the relationship title type, obtain current relationship data from the current relationship system corresponding to the relationship title, use the current relationship data to obtain the current target name, the title subtype ID, and the current target ID, and store the current title ID, the current title type ID, the title subtype ID, the current target ID, and the current target name.

[0029] This application proposes a device for adding relationship titles. The device includes:

[0030] An acquisition module, when receiving a display instruction, acquires the current title type ID and the current title ID corresponding to the current relationship title;

[0031] A determination module, obtains general title information from the target title table, the target title category table, and the title extension information table through the current title ID. The general title information includes a name text ID, a picture ID, a particle ID, an extension information table ID, a subcategory ID, and a description text ID, and determines the current title type according to the current title type ID;

[0032] A general module, when the current title type is the general title type, displays the corresponding general title based on the general title information. The target title table, the target title category table, and the title extension information table are obtained by using the method for establishing relationship title-related tables.

[0033] This application proposes a terminal device, including a memory and a processor. The memory stores a computer program, and when the computer program runs on the processor, it executes the above method for managing relationship titles.

[0034] The present application provides a readable storage medium storing a computer program, which, when running on a processor, executes the above-mentioned method for managing relationship titles.

[0035] The present application obtains a title category table and a title table related to a general title system, creates a new title extension information table, adds an extension information table ID column for associating with the title extension information table to the title table, and deletes redundant columns in the title table according to each column information in the target title category table to obtain a target title table. A title type ID column for associating with the title extension information table is added to the title category table to obtain a target title category table. When adding relationship titles, relationship titles are added based on the target title category table, the target title table, and the title extension information table. By configuring tables to add relationship titles on the basis of existing general titles, the present application can flexibly add personalized tabs, bringing a better gaming experience to users and increasing the activity and freshness of game players. BRIEF DESCRIPTION OF THE DRAWINGS

[0036] To more clearly illustrate the technical solutions of the present invention, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show some embodiments of the present invention and should not be regarded as limiting the protection scope of the present invention. In each drawing, similar components are numbered similarly.

[0037] Figure 1 FIG. shows a schematic flowchart of a method for establishing a relationship title-related table proposed by an embodiment of the present application;

[0038] Figure 2 FIG. shows a schematic flowchart of deleting redundant columns in a title table in a method for establishing a relationship title-related table proposed by an embodiment of the present application;

[0039] Figure 3 FIG. shows a schematic flowchart of another method for establishing a relationship title-related table proposed by an embodiment of the present application;

[0040] Figure 4 FIG. shows a schematic flowchart of a method for managing relationship titles proposed by an embodiment of the present application;

[0041] Figure 5 FIG. shows a schematic flowchart of another method for managing relationship titles proposed by an embodiment of the present application;

[0042] Figure 6 FIG. shows a schematic structural diagram of a device for managing relationship titles proposed by an embodiment of the present application.

[0043] MAIN ELEMENT SYMBOL DESCRIPTION:

[0044] 10 - Relationship Title Management Device; 11 - Acquisition Module; 12 - Determination Module; 13 - General Module. Detailed Implementation Manner

[0045] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only a part of the embodiments of the present invention, rather than all the embodiments.

[0046] Generally, the components of the embodiments of the present invention described and illustrated herein can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present invention provided in the drawings is not intended to limit the scope of the claimed present invention, but merely represents selected embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative efforts fall within the scope of protection of the present invention.

[0047] Hereinafter, the terms "including", "having" and their cognates that can be used in various embodiments of the present invention are only intended to represent specific features, numbers, steps, operations, elements, components or combinations of the foregoing items, and should not be construed as first excluding the existence of one or more other features, numbers, steps, operations, elements, components or combinations of the foregoing items or increasing the possibility of one or more features, numbers, steps, operations, elements, components or combinations of the foregoing items.

[0048] In addition, the terms "first", "second", "third", etc. are only used for distinguishing descriptions and cannot be construed as indicating or implying relative importance.

[0049] Unless otherwise defined, all terms (including technical terms and scientific terms) used herein have the same meaning as commonly understood by those of ordinary skill in the art to which the various embodiments of the present invention belong. The terms (such as those defined in a commonly used dictionary) will be interpreted as having the same meaning as the contextual meaning in the relevant technical field and will not be interpreted as having an idealized meaning or an overly formal meaning unless clearly defined in the various embodiments of the present invention.

[0050] Embodiment 1

[0051] An embodiment of the present application, as Figure 1 shown, a method for establishing a relationship title related table includes the following steps:

[0052] S110: Obtain a title category table and a title table related to the general title system.

[0053] Titles are common items in the game, representing the appellations and titles of players, which can be used to personalized display the achievements of characters. After players meet specific conditions, they can obtain the corresponding titles. Usually, there are common titles in the game, which are pre-set in the game. The content, appearance, etc. of the titles are fixed. When players complete the tasks corresponding to one of the pre-set common titles, they can obtain the common title. After obtaining the title in the game, all titles in the game can be classified and displayed based on the title set. The title set can be classified and managed into a first-level tab and a second-level tab, and the second-level tab is a sub-tab of the first-level tab. The title set is beneficial for players to view the titles they have and have not obtained. For the titles they have obtained, players can choose to wear or remove the title. If a player chooses to wear the title, then other players can see the title of the player's character. The common title system includes a title category table and a title table. The title category table is only used to determine the name of the title category table. Different categories are configured in the title category table. Each row represents a category, and each category corresponds to a tab in the title set. The title category table includes two fields: the title category table ID and the title category name text ID; the title table includes the title preset data. Each row of the title table represents a common title, including a title ID column, a name text ID column, a picture ID column, a particle ID column, a parent category ID column, a sub-category ID column, and a description text ID column. The title ID is the identification mark of the pre-set common title in the game, used to distinguish different common titles. The name text ID is a text, and the content of the text is the name of the title; the picture ID is a static background picture below or around the name text ID, used to decorate the title; the particle ID corresponds to a particle special effect, a dynamic special effect below or around the name text ID, used to decorate the title; the parent category ID represents the parent category, corresponding to the first-level tab in the title set, and used to associate the title category table ID; the sub-category ID represents the sub-category, corresponding to the second-level tab in the title set, and used to associate the title category table ID; the description text ID is used to explain the title in detail, such as the acquisition source of the title, the meaning it represents, and other information.

[0054] S120: Create a new title extension information table.

[0055] In this embodiment, it is a relational title system, which is realized by transforming the existing common title system. Based on the original title table and title category table of the common title system, a new title extension information table is added. At this time, the relational title system can support both the common title function and the relational title function. The newly created title extension information table includes a title type ID column and a title sub-type ID column. The title type ID is used to distinguish relational titles from common titles, and the title sub-type ID is used to represent the sub-types of relational titles.

[0056] S130: Add a title type ID column for associating with the title extension information table to the title category table to obtain a target title category table.

[0057] In this embodiment, a title type ID column, a type ID column, and a parent category ID column can be added to the title category table of ordinary titles. The type ID is used to distinguish whether the title category is a parent category or a subcategory. The parent category ID only needs to be filled in when the type ID is a subcategory. When the type ID is a subcategory, fill in the title type ID column, which is used to associate with the title extension information table and can also represent the title type of a certain subcategory. The title type ID can be used to distinguish ordinary titles and relationship titles, and can also be used to distinguish different types of relationship titles. For example, the title types include ordinary titles and relationship titles, and the relationship titles can include types such as friend titles and guild titles. Therefore, the title type ID can be used to distinguish ordinary titles, friend titles, guild titles, etc.

[0058] It can be understood that in this embodiment, the title category of the title is determined by the type ID and the parent category ID in the target title category table. At this time, the determination of the title category can only depend on the target title category table and no longer depends on the target title table, which is beneficial to the flexible configuration of the title set tab.

[0059] S140: Add a title extension information table ID column for associating with the title extension information table to the title table, and delete the redundant columns in the title table according to the column information in the target title category table to obtain a target title table.

[0060] In this embodiment, a title extension information table ID column is added to the title table of the obtained ordinary title system. The title extension information table ID column is used to associate with the title extension information table, and the title extension information table only includes the information of relationship titles. Therefore, when writing data into the target title table, ordinary titles do not need to fill in the title extension information table ID column, and only relationship titles need to fill in. Each relationship title is associated with an ordinary title. The data of an ordinary title is a row in the target title table, but each row in the target title table does not represent a specific relationship title, but only represents the ordinary title associated with a specific subtype of relationship title. For example, a friend title is associated with an ordinary title. A row in the target title table only represents the data of the ordinary title and does not represent the friend title. It can be seen that ordinary titles do not need to be associated with the title extension information table, and usually the quantity of relationship titles in the game is much smaller than that of ordinary titles. Only associating relationship titles with the extension information table is beneficial to controlling the size of the table data storage and will not cause pressure on the memory.

[0061] Further, as Figure 2 shown, in this embodiment, step S140 includes:

[0062] S141: Obtain each column name in the target title category table;

[0063] After obtaining the target title category table by adding type-related columns to the title category table, obtain each column name in the target title table. The column names of the target title category table include title category table ID, title category name text ID, type ID, parent category ID, and title type ID.

[0064] S142: Obtain each column name in the title table;

[0065] The column names of the title table in the ordinary title system include title ID, name text ID, picture ID, particle ID, parent category ID, sub-category ID, and description text ID.

[0066] S143: Compare each column name in the target title category table with each column name in the title table, and delete the columns that are the same in the target title category table and the title table from the title table.

[0067] Compare the column names of the target title category table: title category table ID, title category name text ID, type ID, parent category ID, and title type ID with the column names of the title table: title ID, name text ID, picture ID, particle ID, parent category ID, sub-category ID, and description text ID. The same column name is the parent category ID. Delete the parent category ID column from the title table, and then associate the title category table ID of the target title category table with the sub-category ID of the target title table, so that the determination of the title category no longer depends on the title table, which is beneficial to the flexible configuration of the title set tab.

[0068] Further, as Figure 3 shown, the method for establishing the related table of relationship titles in this embodiment further includes:

[0069] S150: Determine the title type ID and title sub-type ID according to the relationship system corresponding to the relationship title to be added.

[0070] The target title category table includes columns such as the target title category table ID column, the type ID column, the parent category ID column, and the title type ID column. The target title table includes columns such as the name text ID column, the title ID column, the description text ID column, and the extended information table ID column. The title extended information table includes columns such as the title type ID column, the extended information table ID column, and the title subtype ID column. When developers need to add relationship titles in the game, the corresponding title type ID and title subtype ID can be determined according to the relationship system corresponding to the relationship title to be added in the game. Among them, the added relationship title should be a secondary tab, and the primary tab and the secondary tab correspond to the parent category and the subcategory respectively. For example, the title type ID of the general title system is 1, and the title type ID of the friend title is 6. When the relationship system corresponding to the relationship title to be added is the friend system, the title type ID of the friend title can be obtained as 6. In the friend system, the friend level can be divided into level one, level two, and level three. Different friend levels can be converted into different title subtype IDs. It can be determined that the title type ID is 6 and there are three different title subtype IDs, which can be represented by 1, 2, and 3.

[0071] S160: Add the title type ID to the title type ID column.

[0072] It can be understood that the title type ID determined by the relationship system corresponding to the relationship title is added to the title type ID columns of the target title category table and the title extended information table.

[0073] S170: Determine the addition information for the target title category table ID column, the type ID column, and the parent category ID column according to the current information of the target title category table, and add the corresponding addition information to the target title category table ID column, the type ID column, and the parent category ID column respectively.

[0074] It is understandable that the relationship title system is achieved by transforming the existing ordinary title system. The ordinary title system includes a title category table and a title table. The target title category table and the target title table in the relationship title system are based on the original title category table and title table. Moreover, the relationship title system can support both relationship titles and ordinary titles. Therefore, the target title category table and the target title table also include information related to ordinary titles. Each row in the target title category table represents a category information, that is, corresponding to a category. A category represents a tab in the title set. The title set is used to classify and display all titles in the game, facilitating players to view the titles they have and have not obtained. The current information of the target title category table is the information that already exists in the target title category table, such as the target title category table ID, type ID, and parent category ID corresponding to the ordinary title, etc. When adding a relationship title, a secondary tab is added to the title set, and a corresponding primary tab can be added simultaneously, or a secondary tab can be added based on the existing primary tab. One primary tab can contain multiple secondary tabs, and one secondary tab can only have one corresponding primary tab. Determine the target title category table ID to be added according to the last target title category table ID in the target title category table ID column; among them, the type ID is used to distinguish the parent category from the subcategory. In the current information, if the primary tab and the secondary tab are represented by different data, determine whether each added row is a parent category or a subcategory, and then fill it into the type ID column of the corresponding row; if the added information is the information corresponding to the primary tab, the corresponding parent category ID is not filled. If the added information is the information corresponding to the secondary tab, that is, the subcategory, the corresponding parent category ID should be filled with the target title category table ID of its corresponding primary tab, that is, the parent category; the title type ID column in the target title category table is filled with the title type ID corresponding to the added row. If the added information is the primary tab, the corresponding title type ID is not written. If the added information is the secondary tab, the corresponding title type ID is filled according to the relationship system to determine the title type ID.

[0075] Exemplary, the title type ID of the general title is 1, and the title type ID of the friend title is 6. When the type ID represents the parent type, it is 0, and when it represents the child type, it is 1. When the corresponding relationship system is the friend system, it can be determined that the title type ID added to the target title category table is 6. At this time, the last target title category table ID in the target title category table ID column of the target title category table is 10. When adding a relationship title in the relationship title system with only general titles, two new rows need to be added in the target title category table, representing the first-level tab and the second-level tab of the friend title respectively. When adding the first-level tab of the friend title, the target title category table ID of the added first-level tab is 11. Therefore, when adding the first-level tab, the type ID is set to 0, indicating the parent category, and at this time, the corresponding parent category ID column of the first-level tab will not be filled; when adding the second-level tab of the friend title, the second-level tab represents the child category, the target title category table ID is 12, and the parent category ID of the second-level tab is the target title category table ID of the first-level tab, which is 11. At this time, the corresponding parent category ID of the second-level tab is 1. In addition, game developers can add personalized tabs according to the actual situation. For example, when adding a favorite tab, only a new title category needs to be added, and the title type field of this category is the favorite type, so that a personalized tab can be added.

[0076] S180: Determine the addition information of the extension information table ID column according to the current information of the title extension information table, and add the corresponding addition information to the extension information table ID column.

[0077] S190: Add the title subtype ID to the title subtype ID column.

[0078] Each row in the title extension information table represents the extension information of a relationship title. Each piece of extension information includes the corresponding title subtype ID, extension information table ID, title type ID, etc. During the game development process, the title subtype ID column can be determined through the subtype of the relationship title in the relationship system, that is, the title subtype ID. The determined title subtype ID is added to the title subtype ID column. The number of rows added to the title extension information table is the same as the number of title subtype IDs, and the added extension information table ID is incremented sequentially based on the current extension information table ID of the title extension information table, and the title type ID corresponding to the relationship title is added to the title type ID column of the title extension information table.

[0079] Exemplarily, when the relationship system is a friend system, if there are three different title subtype IDs, three rows are added to the title extension information table. The title subtype IDs 1, 2, and 3 correspond to friend levels one, two, and three respectively. If there is no information in the ID column of the current extension information table, 1, 2, and 3 are filled in the ID column of the extension information table in sequence, and the title type ID column is all added as 6.

[0080] The target title table includes columns such as the name text ID column, title ID column, description text ID column, particle ID column, and extension information table ID column. Each relationship title is associated with an ordinary title, that is, each newly added row in the title extension information table is associated with a certain row in the original row of the target title table. When three rows of information are added to the title extension information table, that is, when the relationship title system can support three relationship levels, there are three different title extension information table IDs in the extension information table ID column. At this time, three corresponding rows of information will be added to the target title table on the existing basis. Among them, the information in the extension information table ID column of the target title table is correspondingly added with the information in the extension information table ID column of the title extension information table. The title IDs in the target title table are added in sequence on the existing basis, and the name text IDs in the target title table use fixed fields, that is, represented by a template. The template can be represented in any way. When displaying the relationship title, the real name of the player is obtained from the relationship system, and the real name text ID is used to replace the template; the particle ID column is not filled; the description text ID can be edited according to the actual situation, which can add relationship titles more quickly and conveniently and is also beneficial to modifying the table.

[0081] Exemplarily, when the relationship system is a friend relationship system, the friend levels are divided into three levels, and three rows are added to the corresponding title extension information table. When the three rows in the extension information table ID column of the title extension information table are 1, 2, and 3 respectively, 1, 2, and 3 are correspondingly added to the extension information table ID column of the target title table. And if the last target title table ID in the target title table ID column of the original target title table is 400, the corresponding target title table ID for the newly added friend level one is 401, the corresponding target title table ID for the friend level two is 402, and the corresponding target title table ID for the friend level three is 403. Among them, the name text IDs are all filled with the same content, such as 12345, and the corresponding text content is a fixed template, such as playname. When the name of the player needs to be displayed, the real name of the player is used for replacement. When the player's name is Zhang San, the friend title is Zhang San's friend.

[0082] In addition, when a new relationship is added in the game, such as a new guild or friend system in the game, corresponding relationship titles need to be added to enhance the playing pleasure of players. When developers add relationship titles, they can add information to the target title category table, the target title table, and the title extension information table through the corresponding title type ID and title subtype ID in the relationship system. In addition, after deleting the redundant columns in the title table, if it is necessary to modify the corresponding relationship between the parent and child categories, only the target title category table needs to be modified, without changing the target title table, which can greatly reduce the labor cost and operation risk. Moreover, only the subcategories are associated in the target title table, which can reduce the complexity of table configuration. When adding a common title, usually only the subcategory in the target title table needs to be modified, and the target title category table generally remains unchanged.

[0083] Embodiment 2

[0084] The second embodiment of this application is as Figure 4 shown, and a relationship title management method is proposed, including the following steps:

[0085] S210: When receiving a display instruction, obtain the current title type ID and the current title ID corresponding to the current relationship title.

[0086] S220: Obtain common title information from the target title table, the target title category table, and the title extension information table through the current title ID. The common title information includes a name text ID, a picture ID, a particle ID, an extension information table ID, a subcategory ID, and a description text ID, and determine the current title type according to the current title type ID.

[0087] The target title table includes columns of title ID, name text ID, picture ID, particle ID, extension information table ID, subcategory ID, and description text ID. The target title category table includes columns of target title category table ID, type ID, parent category ID, name text ID, and title type ID. The title extension information table includes columns of extension information table ID, title type ID, and title subtype ID. When the server and the client are started, common title information is obtained from the target title table, the target title category table, and the title extension information table through the current title ID. The common title information includes a name text ID, a picture ID, a particle ID, an extension information table ID, a subcategory ID, and a description text ID, and the current title type is determined according to the current title type ID. Among them, the subcategory ID column is equivalent to the target title category table ID column.

[0088] Read the target title category table, target title table, and title extension information table to determine the corresponding category of each title, whether it is a parent category or a sub-category, and its title name, etc. When the player logs in, the server sends the current title information of the player character to the client, and the client will display the player's title. In this application, when receiving the display instruction of the player's title, it is judged whether the player is currently wearing a title. If the player is currently wearing a title, it is the current title. The current title includes the title type ID and the title ID. According to the current title type ID, it can be determined whether the current title is a relationship title or a common title. A common title is used to identify different titles through the title ID, and a relationship title inherits the common title through the title ID. The title type ID is used to distinguish between common titles and relationship titles. Thus, it can be seen that a relationship title can not only inherit the characteristics of the associated common title but also has its own unique characteristics. Among them, the relationship title is realized through the inheritance and extension of the common title, inheriting the information such as pictures and particles of the common title, and extending the title name information for personalized display.

[0089] S230: When the current title type is a common title type, display the corresponding common title based on the common title information. The target title table, the target title category table, and the title extension information table are obtained by using the above method for establishing the relationship title-related tables.

[0090] The corresponding title ID and title type ID can be determined according to the title information stored in the current title. Judge the type of the title currently worn by the player according to the title type ID of the current title. The current title type includes a common title type and a relationship title type. When the type of the title currently worn by the player is a common title type, the corresponding common title information in the target title table is obtained through the title ID of the player's current title. The common title information includes the name text ID, picture ID, particle ID, extension information table ID, sub-category ID, and description text ID. Determine the current title type and other information according to the current title type ID. When it is a common title, the extension information table ID in the common title information is empty. Display the corresponding common title based on the common title information, and display the name, picture, and particle special effect information of the title currently worn by the player at the place where it needs to be displayed. Thus, it can be seen that when the type of the title currently worn by the player is a common title, the corresponding title information can be determined through the target title table and the target title category table.

[0091] S240: When the current title type is a relationship title type, obtain the current target ID corresponding to the current relationship title, obtain the relationship title information from the corresponding relationship system through the current target ID, and display the corresponding relationship title based on the common title information and the relationship title information. The relationship title information includes the target name and the title sub-type ID.

[0092] When the current title type is a relationship title type, obtain the current target ID corresponding to the current relationship title, obtain relationship title information from the corresponding relationship system through the current target ID, and display the corresponding relationship title based on the general title information and the relationship title information. The relationship title information includes information such as the target name and the title subtype ID. By obtaining the general title information corresponding to the relationship title in the target title category table, the title extension information table, and the target title table, where the general title information includes information such as the name text ID, the picture ID, the particle ID, the extension information table ID, the subcategory ID, and the description text ID, and obtaining the current relationship title information from the relationship system corresponding to the relationship title, the current relationship title information includes the target name and the title subtype ID, and display the corresponding relationship title based on the general title information and the current relationship title information. The relationship title information includes that when the current title type of the title currently worn by the player is a relationship title type, the general title can be inherited through the title ID of the title currently worn by the player, and obtain the corresponding information in the target title table. Because the target title table includes the title extension information table ID column, the particle ID, the picture ID, the description text ID, and the title subtype ID can be obtained according to the target title category table, the title extension information table, and the target title table.

[0093] In addition, relationship title information including information such as the target ID and the target name can be obtained from the corresponding relationship system according to the title ID. The relationship title only depends on the corresponding relationship system. When the player has a certain relationship, the relationship title information can be dynamically obtained from the corresponding relationship system, so as to obtain the corresponding relationship title. For example, for the friend title, the friend relationship data can be directly obtained from the friend system in real time. By obtaining the data in real time, the storage pressure on the server can be reduced.

[0094] The friend relationship information may include information such as the friend ID, the friend relationship level between friends, and the friend name. Through meaning conversion, the friend relationship level is converted into the title subtype ID, the friend name is converted into the target name, and the friend ID is converted into the target ID. The target ID, the title subtype ID, and the target name are all abstract fields, and the target ID field is used to identify a person or thing with a specific relationship. Each relationship type can obtain the corresponding target name to be added and the title subtype ID to be added through meaning conversion. The relationship system may include friend types, guild types, etc., where the target name is equivalent to the name text ID. It can be seen that by obtaining the data in the relationship title and the information in each table in real time to display the relationship title, a better gaming experience can be brought to users, and the activity and freshness of game players can be improved.

[0095] When displaying the title currently worn by the player, the picture and particle effect information of the title are displayed, and the name text ID in the target title table is displayed using the target name text ID. It can be seen that when the type of the title currently worn by the player is a relationship title, the data in the target title category table, the title extension information table, and the target title table can be read for display.

[0096] Furthermore, a storage procedure for a relationship title management method is proposed, as Figure 5 shown, including the following steps:

[0097] S250: When the current title type is the common title type, store the current title ID and the current title type ID.

[0098] After the player wears or removes a title, the server will store the title ID, title type ID, title subtype ID, target ID, and target name of the title currently worn by the player. According to the title type ID, it is distinguished whether the title currently worn by the player is a common title or a relationship title. When the type of the current title is the common title type, the server only needs to store the current title ID and the current title type ID of the title currently worn by the player, and the list of obtained title IDs of the player whose title type is the common title type. If the player obtains a new common title, the title ID list needs to be stored again.

[0099] S260: When the current title type is the relationship title type, obtain the current relationship data from the current relationship system corresponding to the relationship title, use the current relationship data to obtain the current target name, the title subtype ID, and the current target ID, and store the current title ID, the current title type ID, the title subtype ID, the current target ID, and the current target name.

[0100] When the current title type is the relationship title type, it is not necessary to store the list of relationship titles that the player has obtained, and only the current title information of the title currently worn by the player needs to be stored. It can be understood that in the title system, the list of relationship titles that the player has obtained is not stored, and only needs to be dynamically obtained from the corresponding relationship system, which is beneficial to reducing the storage pressure of the server.

[0101] Embodiment 3

[0102] The third embodiment of the present application, as Figure 6 shown, proposes a relationship title management device 10, and the relationship title management device 10 includes: an acquisition module 11, a determination module 12, and a common module 13.

[0103] The acquisition module 11, when receiving a display instruction, acquires the current title type ID and the current title ID corresponding to the current relationship title; the determination module 12 acquires general title information from the target title table, the target title category table, and the title extension information table through the current title ID. The general title information includes a name text ID, a picture ID, a particle ID, an extension information table ID, a subcategory ID, and a description text ID, and determines the current title type according to the current title type ID; the general module 13, when the current title type is a general title type, displays the corresponding general title based on the general title information. The target title table, the target title category table, and the title extension information table are obtained by using the relationship title related table establishment method.

[0104] In this embodiment, the relationship title management device 10 is used to execute the relationship title management method described in the above embodiment through the cooperation of the acquisition module 11, the determination module 12, and the general module 13. The implementation schemes and beneficial effects involved in the above embodiment are equally applicable in this embodiment and will not be elaborated here.

[0105] Embodiment 4

[0106] The fourth embodiment of the present application proposes a computer device, including a memory and a processor. The memory stores a computer program, and when the computer program runs on the processor, it executes the relationship title management method described in the above embodiment.

[0107] Embodiment 5

[0108] The fifth embodiment of the present application proposes a readable storage medium that stores a computer program, and when the computer program runs on a processor, it executes the relationship title management method described in the embodiments of the present application.

[0109] In several embodiments provided by the present application, it should be understood that the disclosed devices and methods can also be implemented in other ways. The device embodiments described above are merely illustrative. For example, the flowcharts and block diagrams in the accompanying drawings show the possible architectures, functions, and operations of devices, methods, and computer program products according to multiple embodiments of the present invention. In this regard, each block in the flowchart or block diagram may represent a module, a program segment, or a part of code, and the module, program segment, or part of code contains one or more executable instructions for implementing the specified logical function. It should also be noted that in an alternative implementation, the functions marked in the blocks may occur in a different order than that marked in the accompanying drawings. For example, two consecutive blocks may actually be executed substantially in parallel, and they may sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram and / or flowchart, as well as the combination of blocks in the block diagram and / or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or actions, or can be implemented by a combination of dedicated hardware and computer instructions.

[0110] In addition, each functional module or unit in various embodiments of the present invention may be integrated together to form an independent part, or each module may exist alone, or two or more modules may be integrated to form an independent part.

[0111] If the above functions are implemented in the form of software functional modules and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a smart phone, a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs that can store program codes.

[0112] The above is only the specific implementation manner of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of changes or substitutions, which should all be covered by the protection scope of the present invention.

Claims

1. A method for establishing a related table of relationship titles, characterized in that, the method includes: Obtain a title category table and a title table related to the ordinary title system; Create a new title extension information table; Add a title type ID column for associating with the title extension information table to the title category table to obtain a target title category table; Add an extension information table ID column for associating with the title extension information table to the title table, and delete redundant columns in the title table according to each column information in the target title category table to obtain a target title table; Wherein, the deleting redundant columns in the title table according to each column information in the target title category table includes: Obtain each column name in the target title category table; Obtain each column name in the title table; Compare each column name in the target title category table with each column name in the title table, and delete the same columns from the title table between the target title category table and the title table.

2. The method for establishing a related table of relationship titles according to claim 1, characterized in that, The target title category table includes a target title category table ID column, a type ID column, a parent category ID column, and a title type ID column. The title extension information table includes an extension information table ID column, a title subtype ID column, and a title type ID column. It also includes: Determine the title type ID and the title subtype ID according to the relationship system corresponding to the relationship title to be added; Add the title type ID to the title type ID column; Determine the addition information of the target title category table ID column, the type ID column, and the parent category ID column according to the current information of the target title category table, and add the corresponding addition information to the target title category table ID column, the type ID column, and the parent category ID column respectively; Determine the addition information of the extension information table ID column according to the current information of the title extension information table, and add the corresponding addition information to the extension information table ID column; Add the title subtype ID to the title subtype ID column.

3. A method for managing relationship titles, characterized in that, The target title table includes a title ID column, a name text ID column, a picture ID column, a particle ID column, an extension information table ID column, a subcategory ID column, and a description text ID column. The target title category table includes a target title category table ID column, a type ID column, a parent category ID column, a name text ID column, and a title type ID column. The title extension information table includes the extension information table ID column, the title type ID column, and the title subtype ID column. The method includes: When receiving a display instruction, obtain the current title type ID and the current title ID corresponding to the current relationship title; Obtain ordinary title information from the target title table, the target title category table, and the title extension information table through the current title ID. The ordinary title information includes a name text ID, a picture ID, a particle ID, an extension information table ID, a subcategory ID, and a description text ID. Determine the current title type according to the current title type ID; When the current title type is a common title type, display the corresponding common title based on the common title information, where the target title table, the target title category table, and the title extension information table are obtained by using the relationship title - related table establishment method according to any one of claims 1 - 2.

4. The relationship title management method according to claim 3, characterized in that, further comprising: When the current title type is a relationship title type, obtain the current target ID corresponding to the current relationship title, obtain the relationship title information from the corresponding relationship system through the current target ID, and display the corresponding relationship title based on the common title information and the relationship title information, where the relationship title information includes the target name and the title sub - type ID.

5. The relationship title management method according to claim 3, characterized in that, further comprising: When the current title type is the common title type, store the current title ID and the current title type ID.

6. The relationship title management method according to claim 4, characterized in that, further comprising: When the current title type is the relationship title type, obtain the current relationship data from the current relationship system corresponding to the relationship title, obtain the current target name, the title sub - type ID, and the current target ID by using the current relationship data, and store the current title ID, the current title type ID, the title sub - type ID, the current target ID, and the current target name.

7. A relationship title management device, characterized in that, the device includes: An acquisition module, when receiving a display instruction, obtain the current title type ID and the current title ID corresponding to the current relationship title; A determination module, obtain the common title information from the target title table, the target title category table, and the title extension information table through the current title ID, where the common title information includes the name text ID, the picture ID, the particle ID, the extension information table ID, the sub - category ID, and the description text ID, and determine the current title type according to the current title type ID; A common module, when the current title type is a common title type, display the corresponding common title based on the common title information, where the target title table, the target title category table, and the title extension information table are obtained by using the relationship title - related table establishment method according to any one of claims 1 - 2.

8. A terminal device, characterized in that, it includes a memory and a processor, the memory stores a computer program, and when the computer program runs on the processor, it executes the relationship title management method according to any one of claims 3 to 6.

9. A readable storage medium, characterized in that, it stores a computer program, and when the computer program runs on a processor, it executes the relationship title management method according to any one of claims 3 to 6.

Citation Information

Patent Citations

  • Game system

    JP2016144687A

  • Database management device, method and program

    WO2006046669A1