Game control system based on multi-developer real-time cooperation and implementation method thereof

Abstract

The invention discloses a game control system based on multi-developer real-time cooperation and an implementation method thereof, and the system comprises a version control system, a communication system and a plurality of developers, and the version control system is in communication connection with the communication system. The version control system comprises a clone warehouse module, a branch management module, a code change submission module, a remote warehouse module, a local warehouse module and a code review merging module, the clone warehouse module is used for storing clone codes, and a developer clones and stores the codes of projects of the remote warehouse module to the clone warehouse module; a developer creates a new branch through the branch management module to perform new function development or BUG repair; the developer sends the code to the remote warehouse module in a local submission mode; the code changing and submitting module comprises a temporary storage area which is used for storing temporary codes; according to the scheme, tight cooperation and efficient communication of the developers in the development team can be ensured, so that the game development efficiency and quality are improved.

Description

Technical Field

[0001] The present invention belongs to the technical field of game development, and in particular relates to a game control system based on real-time collaboration among multiple developers and an implementation method thereof. Background Art

[0002] The game development control system is a system that integrates multiple functional modules such as project management, version control, code editing, resource management, test verification, etc. Its main purpose is to ensure that each link in the game development process can be carried out efficiently and orderly through a process-based and standardized management method, thereby improving the quality and market competitiveness of the game.

[0003] Game development usually involves the collaboration of multiple departments, including programming, art, sound effects, planning, etc. How to effectively coordinate the work between departments to ensure the progress and quality of the project is a major challenge in game project management. During the game development process, project requirements may change due to market conditions, player needs or technical limitations. How to respond to changes in requirements and ensure that the project proceeds as planned is another major challenge in game project management. During the game development process, various vulnerabilities and errors may occur. If these vulnerabilities and errors are not discovered and fixed in time, they will seriously affect the quality of the game and user experience. Members of the game development team may come from different backgrounds and professional fields, and poor communication is a common problem, which may lead to misunderstandings and wrong decisions. Secondly, during team collaboration, if tasks are unevenly distributed or responsibilities are unclear, some members may be overloaded or underworked.

[0004] Therefore, the present solution provides a multi-developer real-time collaborative game control system and an implementation method thereof to solve the current problem of low communication efficiency among multiple developers. Summary of the invention

[0005] In view of the problems raised by the above background technology, the purpose of the present invention is to provide a game control system based on real-time collaboration among multiple developers and its implementation method,

[0006] In order to achieve the above technical objectives, the technical solution adopted by the present invention is as follows:

[0007] A game control system based on multi-developer real-time collaboration, comprising a version control system, a communication system and a plurality of developers, wherein the version control system is communicatively connected with the communication system, the version control system comprises a clone warehouse module, a branch management module, a code change submission module, a remote warehouse module, a local warehouse module and a code review and merge module, and the developers are communicatively connected with the clone warehouse module, the branch management module, the code change submission module, the remote warehouse module, the local warehouse module and the code review and merge module respectively;

[0008] The clone warehouse module is used to store cloned code. The developer clones the code of the project in the remote warehouse module and stores it in the clone warehouse module;

[0009] The developer creates a new branch through the branch management module to develop new functions or fix bugs;

[0010] The developer sends the code to the remote repository module by submitting it locally;

[0011] The code change submission module includes a temporary storage area, and the temporary storage area is used to store temporary codes;

[0012] The local warehouse module is used to store local codes;

[0013] The developer reviews the code using a code review merge module;

[0014] The remote warehouse module is used to receive the developer's change command;

[0015] The communication system includes a workspace creation module, a channel creation module and a notification reminder module;

[0016] The create workspace module is used to create a new workspace, and developers can be invited to join this workspace;

[0017] The channel creation module is used to create a channel for developers to communicate, and the channel is provided with a real-time communication area for developers to communicate and discuss in real time;

[0018] The notification and reminder module is used to convey the reminder information to each developer.

[0019] In a further definition, the developer includes a main developer and multiple sub-developers, and the sub-developers send the code to the main developer by way of local submission.

[0020] It is further defined that the real-time communication area can provide text, voice, video chat, file sharing and screen sharing functions for multiple developers.

[0021] It is further defined that the channels include a general discussion channel, a development discussion channel and a technical support channel.

[0022] In a further aspect, the version control system may adopt GIT, and the communication system may adopt Slack (a work efficiency management platform).

[0023] A method for implementing a game control system based on real-time collaboration among multiple developers comprises the following steps:

[0024] Step 1: Create a local warehouse. Developers create a local warehouse through the local warehouse module and create a remote warehouse through the remote warehouse module;

[0025] Step 2: Clone the remote warehouse. The developer clones the remote warehouse to the local through the clone warehouse module and runs the remote warehouse.

[0026] Step 3: Branch management Each developer creates an independent branch locally. The branch is an independent workflow, and the developer develops the game on the independent branch.

[0027] Step 4: Development. Each developer develops the game on their own independent branch. After modifying the code, the developer adds the modified file to the temporary storage area, and the modification record is submitted to the local warehouse module by the code change submission module;

[0028] Step 5: Pull the latest code. The developer enters the operation command to pull the latest code from the remote warehouse to the local warehouse;

[0029] Step 6: Push changes. After completing local development, the developer pushes the changes in the local branch to the remote repository by entering operation instructions, so that other developers can see and pull these changes.

[0030] Step 7: Merge branches. The code review merge module merges branches of the code that has successfully passed the review, that is, merges each independent branch into a main branch.

[0031] Step 8: Regular cleanup. The remote warehouse module and the local warehouse module are equipped with regular cleanup functions, which are used to regularly delete unnecessary branches in the local warehouse and remote warehouse.

[0032] In a further definition, in the step 1, when the developer creates the ontology warehouse, a local warehouse URL is generated, and when the developer creates the remote warehouse, a remote warehouse URL is generated, and the local warehouse URL and the remote warehouse URL are sent to each developer.

[0033] It is further defined that a project management tool is included, wherein the project management tool is used to track and assign tasks.

[0034] Beneficial effects of the present invention:

[0035] This solution provides a game control system based on real-time collaboration among multiple developers and its implementation method. By setting up a version control system and a communication system, each developer uses the communication system for real-time discussion and communication, which improves the efficiency of problem solving and makes it easier for each developer to reach a consensus. When project requirements may change, they can communicate and change the code in a timely manner. Secondly, various vulnerabilities and errors that appear in the game development process are modified in a timely manner to avoid vulnerabilities and errors that are not discovered and repaired in time, which affects the quality of the game and user experience. Secondly, in the process of team collaboration, if the tasks are unevenly distributed or the responsibilities are not clear, it may cause some members to be overloaded or underworked. This solution sets up a project management tool to track and assign tasks to solve this problem.

[0036] In summary, this solution can ensure close collaboration and efficient communication among developers in the development team, thereby improving the efficiency and quality of game development. BRIEF DESCRIPTION OF THE DRAWINGS

[0037] The present invention can be further illustrated by the non-limiting examples given in the accompanying drawings;

[0038] Figure 1 A system module diagram of an embodiment of a multi-developer real-time collaborative game control system and an implementation method thereof according to the present invention;

[0039] Figure 2 The present invention is a flowchart of a multi-developer real-time collaborative game control system and an implementation method thereof. DETAILED DESCRIPTION

[0040] In order to enable those skilled in the art to better understand the present invention, the technical solution of the present invention is further described below in conjunction with the accompanying drawings and embodiments. The technical solution in the embodiments of the present invention will be clearly and completely described below in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present invention.

[0041] It should be noted that all directional indications in the embodiments of the present invention (such as up, down, left, right, front, back, etc.) are only used to explain the relative position relationship, movement status, etc. between the components under a certain specific posture (as shown in the accompanying drawings). If the specific posture changes, the directional indication will also change accordingly.

[0042] In addition, the descriptions of "first", "second", etc. in the present invention are only used for descriptive purposes and cannot be understood as indicating or implying their relative importance or implicitly indicating the number of the indicated technical features. Therefore, the features defined as "first" and "second" may explicitly or implicitly include at least one of the features. In addition, the technical solutions between the various embodiments can be combined with each other, but it must be based on the ability of ordinary technicians in the field to implement. When the combination of technical solutions is contradictory or cannot be implemented, it should be deemed that such a combination of technical solutions does not exist and is not within the scope of protection required by the present invention. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not used to limit the present invention.

[0043] like Figure 1-Figure 2 As shown, a game control system based on real-time collaboration among multiple developers of the present invention includes a version control system, a communication system and a plurality of developers, wherein the version control system is communicatively connected with the communication system, the version control system includes a clone warehouse module, a branch management module, a code change submission module, a remote warehouse module, a local warehouse module and a code review and merge module, and the developers are communicatively connected with the clone warehouse module, the branch management module, the code change submission module, the remote warehouse module, the local warehouse module and the code review and merge module respectively;

[0044] The clone warehouse module is used to store cloned code. The developer clones the code of the project in the remote warehouse module and stores it in the clone warehouse module;

[0045] The developer creates a new branch through the branch management module to develop new functions or fix bugs;

[0046] The developer sends the code to the remote repository module by submitting it locally;

[0047] The code change submission module includes a temporary storage area, and the temporary storage area is used to store temporary codes;

[0048] The local warehouse module is used to store local codes;

[0049] The developer reviews the code using a code review merge module;

[0050] The remote warehouse module is used to receive the developer's change command;

[0051] The communication system includes a workspace creation module, a channel creation module and a notification reminder module;

[0052] The create workspace module is used to create a new workspace, and developers can be invited to join this workspace;

[0053] The channel creation module is used to create a channel for developers to communicate, and the channel is provided with a real-time communication area for developers to communicate and discuss in real time;

[0054] The notification and reminder module is used to convey the reminder information to each developer.

[0055] Specifically, developers can create different channels according to different needs.

[0056] Preferably, the developers include a main developer and multiple sub-developers, and the sub-developers send the code to the main developer by local submission.

[0057] Preferably, the real-time communication area can provide text, voice, video chat, file sharing and screen sharing functions for multiple developers.

[0058] Preferably, the channels include a general discussion channel, a development discussion channel and a technical support channel.

[0059] Preferably, the version control system may adopt GIT, and the communication system may adopt Slack.

[0060] A method for implementing a game control system based on real-time collaboration among multiple developers comprises the following steps:

[0061] Step 1: Create a local warehouse. Developers create a local warehouse through the local warehouse module and create a remote warehouse through the remote warehouse module;

[0062] Specifically, each developer needs to install Git in their own development environment and configure the Git username and email address so that their identity can be correctly identified when submitting changes.

[0063] Step 2: Clone the remote warehouse. The developer clones the remote warehouse to the local through the clone warehouse module and runs the remote warehouse.

[0064] Specifically, developers can use the command line to run the git clone <remote repository URL> command to clone the remote repository.

[0065] Step 3: Branch management Each developer creates an independent branch locally. The branch is an independent workflow, and the developer develops the game on the independent branch.

[0066] Specifically, developers use the git checkout-b new-branch-name command to create and switch to an independent branch;

[0067] Use the git checkout <branch name> or git switch <branch name> command to switch to the branch. Each branch represents an independent workflow, and developers can develop on their own branches without affecting the work of other developers.

[0068] Step 4: Development. Each developer develops the game on their own independent branch. After modifying the code, the developer adds the modified file to the temporary storage area, and the modification record is submitted to the local warehouse module by the code change submission module;

[0069] Specifically, developers use git add . or git add <filename>command to add code changes to the staging area; developers use the "git commit -m commit message" command to commit changes in the staging area to the local repository and attach the commit message.

[0070] Step 5: Pull the latest code. The developer enters the operation command to pull the latest code from the remote warehouse to the local warehouse. The advantage of pulling the latest code in this way is that the code can be kept synchronized at any time.

[0071] Specifically, developers can use the git pull origin <branch name> command to pull the latest code from the remote repository to the local repository and automatically merge it into the current branch.

[0072] Step 6: Push changes. After completing local development, the developer pushes the changes in the local branch to the remote repository by entering operation instructions, so that other developers can see and pull these changes.

[0073] Specifically, developers use the git push origin new-branch-name command to push changes to the branch to the remote repository.

[0074] Step 7: Merge branches. The code review merge module merges branches of the code that has successfully passed the review, that is, merges each independent branch into a main branch.

[0075] Specifically, developers can use the git merge <branch name> command to merge a branch into the current branch. It is worth noting that code review should be performed before merging branches to ensure the quality and consistency of the code.

[0076] Step 8: Regular cleaning. The remote warehouse module and the local warehouse module have regular cleaning functions, which are used to regularly delete unnecessary branches in the local warehouse and the remote warehouse; this can keep the local warehouse and the remote warehouse tidy;

[0077] Specifically, developers can use the git branch -d <branch name> command to delete local branches, and use the git pushorigin --delete <branch name> command to delete remote branches.

[0078] Preferably, in the step 1, when a developer creates an ontology repository, a local repository URL is generated, and when a remote repository is created, a remote repository URL is generated, and the local repository URL and remote repository URL are sent to each developer.

[0079] Preferably, a project management tool is also included, wherein the project management tool is used to track and assign tasks.

[0080] The working principle and beneficial effects of this solution are:

[0081] By setting up a version control system and a communication system, each developer uses the communication system for real-time discussion and communication, which improves the efficiency of problem solving and makes it easier for each developer to reach a consensus. When project requirements may change, they can communicate and change the code in a timely manner. Secondly, various vulnerabilities and errors that appear in the game development process are modified in a timely manner to avoid vulnerabilities and errors that are not discovered and repaired in time, which affects the quality of the game and user experience. Secondly, in the process of team collaboration, if the tasks are unevenly distributed or the responsibilities are not clear, it may cause some members to be overloaded or underworked. This solution sets up a project management tool to track and assign tasks to solve this problem.

[0082] In summary, this solution can ensure close collaboration and efficient communication among developers in the development team, thereby improving the efficiency and quality of game development. The above embodiments are merely illustrative of the principles and effects of the present invention, and are not intended to limit the present invention. Anyone familiar with the technology may modify or change the above embodiments without violating the spirit and scope of the present invention. Therefore, all equivalent modifications or changes made by those with ordinary knowledge in the technical field without departing from the spirit and technical ideas disclosed by the present invention should still be covered by the claims of the present invention.< / filename>

Claims

1. A game control system based on real-time collaboration among multiple developers, characterized by: It includes a version control system, a communication system and a plurality of developers, wherein the version control system is in communication connection with the communication system, the version control system includes a clone warehouse module, a branch management module, a code change submission module, a remote warehouse module, a local warehouse module and a code review and merge module, and the developers are in communication connection with the clone warehouse module, the branch management module, the code change submission module, the remote warehouse module, the local warehouse module and the code review and merge module respectively; The clone warehouse module is used to store cloned code. The developer clones the code of the project in the remote warehouse module and stores it in the clone warehouse module; The developer creates a new branch through the branch management module to develop new functions or fix bugs; The developer sends the code to the remote repository module by submitting it locally; The code change submission module includes a temporary storage area, and the temporary storage area is used to store temporary codes; The local warehouse module is used to store local codes; The developer reviews the code using a code review merge module; The remote warehouse module is used to receive the developer's change command; The communication system includes a workspace creation module, a channel creation module and a notification reminder module; The create workspace module is used to create a new workspace, and developers can be invited to join this workspace; The channel creation module is used to create a channel for developers to communicate, and the channel is provided with a real-time communication area for developers to communicate and discuss in real time; The notification and reminder module is used to convey the reminder information to each developer.

2. A multi-developer real-time collaborative game control system according to claim 1, characterized in that: The developers include a main developer and multiple sub-developers, and the sub-developers send codes to the main developer by local submission.

3. A multi-developer real-time collaborative game control system according to claim 1, characterized in that: The real-time communication area can provide text, voice, video chat, file sharing and screen sharing functions for multiple developers.

4. A game control system based on multi-developer real-time collaboration according to claim 1, characterized in that: The channels include a general discussion channel, a development discussion channel, and a technical support channel.

5. The game control system based on multi-developer real-time collaboration according to claim 1, characterized in that: The version control system may adopt GIT, and the communication system may adopt Slack.

6. A method for implementing a multi-developer real-time collaborative game control system, characterized in that: The steps include: Step 1: Create a local warehouse. Developers create a local warehouse through the local warehouse module and create a remote warehouse through the remote warehouse module; Step 2: Clone the remote warehouse. The developer clones the remote warehouse to the local through the clone warehouse module and runs the remote warehouse. Step 3: Branch management Each developer creates an independent branch locally. The branch is an independent workflow, and the developer develops the game on the independent branch. Step 4: Development. Each developer develops the game on their own independent branch. After modifying the code, the developer adds the modified file to the temporary storage area, and the modification record is submitted to the local warehouse module by the code change submission module; Step 5: Pull the latest code. The developer enters the operation command to pull the latest code from the remote warehouse to the local warehouse; Step 6: Push changes. After completing local development, the developer pushes the changes in the local branch to the remote repository by entering operation instructions, so that other developers can see and pull these changes. Step 7: Merge branches. The code review merge module merges branches of the code that has successfully passed the review, that is, merges each independent branch into a main branch. Step 8: Regular cleanup. The remote warehouse module and the local warehouse module are equipped with regular cleanup functions, which are used to regularly delete unnecessary branches in the local warehouse and remote warehouse.

7. The method for implementing a multi-developer real-time collaborative game control system according to claim 6, characterized in that: In the step 1, when a developer creates an ontology warehouse, a local warehouse URL is generated, and when a remote warehouse is created, a remote warehouse URL is generated. The local warehouse URL and the remote warehouse URL are sent to each developer.

8. The method for implementing a multi-developer real-time collaborative game control system according to claim 6, characterized in that: Also included is a project management tool for tracking and assigning tasks.

Images