A method for managing game versions

Abstract

The present invention discloses a method for managing game versions, comprising the following steps: S1, starting a nodejs process through a batch processing bat file, and passing in the path of a jzTab file to be processed; S2, opening the jzTab file, holding the file handle of the jzTab file, and setting the jzTab file to a read-only state; S3, parsing the content of the jzTab file and converting it into an XML intermediate file; S4, opening and editing the XML intermediate file in an Excel program; S5, in steps S1-S4, the nodejs process monitors the status of the XML intermediate file in real time. If it is detected that the content of the XML intermediate file has been modified, the valid content of the XML intermediate file is reread and parsed, and the content of the jzTab file is reversely updated using the file handle. The present invention introduces the jzTab file to assist in version information update management while retaining the Excel editing method, greatly improving version management efficiency.

Description

Technical Field

[0001] The present invention relates to the field of computer technology, and in particular to a method for managing game versions. Background Art

[0002] During the game development process, there are often situations where multiple people are editing and multiple versions are being developed simultaneously. In version management, developers are usually accustomed to directly using Excel files as configuration files. Since Excel has powerful editing functions, for planners and other developers, using Excel as a configuration file can improve work efficiency. However, since Excel files cannot be merged automatically, each version synchronization requires manual processing, which is inefficient and not conducive to the efficient management of various game versions. Summary of the Invention

[0003] To solve the above problems, the present invention provides a method for managing game versions.

[0004] The present invention adopts the following technical solutions:

[0005] A method for managing game versions includes the following steps:

[0006] S1. Start the nodejs process through the batch processing bat file and pass in the path of the jzTab file to be processed;

[0007] S2. Open the jzTab file, hold the file handle of the jzTab file, and set the jzTab file to read-only state;

[0008] S3, parse the content of the jzTab file and convert it into an xml intermediate file;

[0009] S4. Open and edit the XML intermediate file in Excel program;

[0010] S5. In steps S1-S4, the nodejs process monitors the status of the xml intermediate file in real time. If it detects that the content of the xml intermediate file has been modified, it rereads and parses the valid content of the xml intermediate file and uses the file handle to reversely update the content of the jzTab file.

[0011] Furthermore, while converting into an XML intermediate file in step S3, the XML intermediate file is stored in a cache directory.

[0012] Furthermore, in step S4, the Excel is designated as the default opening program for the XML intermediate file.

[0013] Furthermore, in step S5, if it is monitored that the XML intermediate file becomes an unwritable state for the first time, it is confirmed that the Excel program has been successfully opened.

[0014] Furthermore, in step S5, if it is monitored that the xml intermediate file becomes readable and writable, it is confirmed that the excel program has been closed. At this time, the nodejs process saves the current xml intermediate file, modifies the jzTab file to a readable and writable state, releases the file handle, and exits the nodejs process at the same time.

[0015] Furthermore, when the nodejs process in step S5 saves the current XML intermediate file, it also copies the XML intermediate file stored in the cache directory in step S3 into a record copy.

[0016] Furthermore, the jzTab file is used to save the version table information.

[0017] After adopting the above technical solution, the present invention has the following advantages compared with the background technology:

[0018] The present invention introduces and designs a jzTab file to assist in updating version information. The jzTab file is converted into an XML intermediate file that can be edited in an Excel program, and then the nodejs process is used to automatically complete the reverse extraction of information from the XML intermediate file and the synchronous update of the jzTab file. The jzTab file is used to store the table information of the version, so that the file retains a larger proportion of valid information. When multiple people are editing, the version information can still be automatically updated and managed, and there is no need to manually merge multiple Excel files, which reduces the workload and greatly improves the efficiency of version management. In addition, the present invention uses the XML intermediate file method to retain the original habit of using Excel as a configuration file for editing, avoiding the slowdown of developers' work efficiency due to sudden changes in editing habits. BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Figure 1 Flow chart of the method of the present invention. DETAILED DESCRIPTION

[0020] In order to make the purpose, technical solutions and advantages of the present invention more clearly understood, the present invention will be further described in detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present invention and are not intended to limit the present invention. Example

[0021] like Figure 1 As shown, a method for managing game versions includes the following steps:

[0022] S1. Start the nodejs process through a batch processing bat file and pass in the path of the jzTab file to be processed; the jzTab file is used to save the version table information, and the batch processing bat file serves as the entry file for opening the jzTab file;

[0023] S2. Open the jzTab file, hold the file handle of the jzTab file, and set the jzTab file to read-only state to prevent file reuse;

[0024] S3. Parse the contents of the jzTab file and convert it into an XML intermediate file that can be directly opened and edited by Excel, and store the XML intermediate file in a cache directory;

[0025] S4. Open and edit the XML intermediate file in the Excel program. Specifically, in the Windows system, specify Excel as the default program for opening the XML intermediate file, and then directly call the system interface in the Node.js process to open the specified XML intermediate file. The content of the XML intermediate file can be viewed in the Excel program and edited.

[0026] S5. In steps S1-S4, the nodejs process monitors the status of the XML intermediate file in real time:

[0027] If the XML intermediate file is detected to be in an unwritable state for the first time, it is confirmed that the Excel program has been successfully opened. This is because it takes a certain amount of time for the Excel program to open, and it is impossible to immediately determine whether the Excel program has been successfully opened. A mark needs to be set for polling detection. When the XML intermediate file becomes in an unwritable state for the first time, it indicates that the Excel program has been successfully opened.

[0028] If it is detected that the content of the xml intermediate file is modified, the valid content of the xml intermediate file is re-read and parsed, and the information is extracted in reverse. By saving the file handle of the jzTab file, the reverse update of the jzTab file content is achieved.

[0029] If it is monitored that the XML intermediate file becomes readable and writable, it is confirmed that the Excel program has been closed. At this time, the nodejs process saves the current XML intermediate file, and copies the XML intermediate file stored in the cache directory in step S3 into a record copy, and modifies the jzTab file to a readable and writable state and releases the file handle, closes the jzTab file, and exits the nodejs process.

[0030] Specifically, the jzTab file is a customizable file format that retains as little data as possible to describe the contents of a table while retaining all valid content information. The main contents include tables, tabs, row data, and cell data. Each cell is saved as a separate line of text. The advantage of this format is that when multiple people modify the table at the same time, it can achieve maximum merging in version management and reduce conflicts. However, this file format cannot be directly opened and edited using the Excel program. The version information contained in the jzTab file content of this embodiment includes: loading diagram name, title, name, element, display picture, listing year, listing month, listing day, and the number of seconds on the listing day.

[0031] The XML intermediate file is constructed by parsing and extracting the contents of the jzTab file and automatically adding the corresponding data. This file can be directly opened and edited by Excel. When Excel saves the file, it parses and extracts the contents of the file and reverse-constructs it into a jzTab file, thus enabling editing and updating of the jzTab file. After Excel is edited and closed, the XML intermediate file is automatically deleted.

[0032] The batch processing bat file, i.e. the batch processing startup file, is named read.bat. It is a jzTab file startup program written using Windows batch processing. The program will start the corresponding nodejs program and start the process to perform subsequent processing on the jzTab file. Considering the version management inherited to this embodiment, the bat program will search several directories in the project directory to find the startup process. You can also directly use the installation version for design and directly call the last instruction.

[0033] The above description is merely a preferred embodiment of the present invention, but the scope of protection of the present invention is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in the present invention should be included in the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be based on the scope of protection of the claims.

Claims

1. A method for managing game versions, characterized by: The steps include: S1. Start the nodejs process through the batch processing bat file and pass in the path of the jzTab file to be processed; the jzTab file is used to save the version table information; S2. Open the jzTab file, hold the file handle of the jzTab file, and set the jzTab file to read-only state; S3, parse the content of the jzTab file and convert it into an xml intermediate file; In step S3, the XML intermediate file is converted into an intermediate file and stored in a cache directory; S4. Open and edit the XML intermediate file in Excel program; In step S4, the Excel file is designated as the default opening program for the XML intermediate file; S5. In steps S1-S4, the nodejs process monitors the status of the XML intermediate file in real time. If it is detected that the content of the XML intermediate file has been modified, the nodejs process rereads and parses the valid content of the XML intermediate file and uses the file handle to reversely update the content of the jzTab file. In step S5, if it is monitored that the XML intermediate file becomes unwritable for the first time, it is confirmed that the Excel program has been successfully opened; In step S5, if it is detected that the XML intermediate file becomes readable and writable, it is confirmed that the Excel program has been closed. At this time, the nodejs process saves the current XML intermediate file, modifies the jzTab file to a readable and writable state, releases the file handle, and exits the nodejs process at the same time; When the nodejs process saves the current XML intermediate file in step S5, it also copies the XML intermediate file stored in the cache directory in step S3 into a record copy.

Images