rgss_db 1.0.3 → 1.0.4
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- checksums.yaml +4 -4
- data/CHANGELOG.md +33 -25
- data/README.md +347 -347
- data/lib/rgss_db/model/data_file.rb +42 -0
- data/lib/rgss_db/model/data_file_factory.rb +14 -4
- data/lib/rgss_db/version.rb +1 -1
- data/sig/rgss_db.rbs +27 -0
- metadata +17 -17
checksums.yaml
CHANGED
|
@@ -1,7 +1,7 @@
|
|
|
1
1
|
---
|
|
2
2
|
SHA256:
|
|
3
|
-
metadata.gz:
|
|
4
|
-
data.tar.gz:
|
|
3
|
+
metadata.gz: f317e62c4cd17a930f436ce31c07ec9e6d0e876e35085c81e32e513647cfe07e
|
|
4
|
+
data.tar.gz: f5126515cea7234cd070b35c42604dd8f9f229793a7bdf933b94e92c510cd814
|
|
5
5
|
SHA512:
|
|
6
|
-
metadata.gz:
|
|
7
|
-
data.tar.gz:
|
|
6
|
+
metadata.gz: 81483632c5ee641f12edd94e4d29f022990e52675604e5bfa9dcda25f864fbecb6f3b55b4f8468e4bcff5e3c75265817ed36f4ca140af336a3182b69e5b97185
|
|
7
|
+
data.tar.gz: e2ce89921e54089f254aa871a2718d92bbfb2834faf212b3bb66cb0362f3c405ed64e59f3f1de1bb1fed936956780b45d953e2a84823371bb2415f733d39aadc
|
data/CHANGELOG.md
CHANGED
|
@@ -1,25 +1,33 @@
|
|
|
1
|
-
## [Unreleased]
|
|
2
|
-
|
|
3
|
-
## [1.0.
|
|
4
|
-
|
|
5
|
-
### Fixed
|
|
6
|
-
|
|
7
|
-
- Fixed map data
|
|
8
|
-
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
|
|
14
|
-
|
|
15
|
-
-
|
|
16
|
-
|
|
17
|
-
|
|
18
|
-
|
|
19
|
-
|
|
20
|
-
|
|
21
|
-
|
|
22
|
-
|
|
23
|
-
|
|
24
|
-
|
|
25
|
-
-
|
|
1
|
+
## [Unreleased]
|
|
2
|
+
|
|
3
|
+
## [1.0.4] - 2025-03-14
|
|
4
|
+
|
|
5
|
+
### Fixed
|
|
6
|
+
|
|
7
|
+
- Fixed map data files for JSON files
|
|
8
|
+
- RPG Maker maps were not imported properly into RPG Maker
|
|
9
|
+
- Map events disappeared from the RPG Maker editor
|
|
10
|
+
|
|
11
|
+
## [1.0.3] - 2024-06-08
|
|
12
|
+
|
|
13
|
+
### Fixed
|
|
14
|
+
|
|
15
|
+
- Fixed map data file glob pattern
|
|
16
|
+
- Map files ending in 0 were not recognized by the tool
|
|
17
|
+
|
|
18
|
+
## [1.0.2] - 2024-05-25
|
|
19
|
+
|
|
20
|
+
### Changed
|
|
21
|
+
|
|
22
|
+
- Removed unused dependencies from the view
|
|
23
|
+
- Gemfile changes
|
|
24
|
+
|
|
25
|
+
## [1.0.1] - 2024-05-25
|
|
26
|
+
|
|
27
|
+
### Changed
|
|
28
|
+
|
|
29
|
+
- Removed unused dependencies
|
|
30
|
+
|
|
31
|
+
## [1.0.0] - 2024-05-25
|
|
32
|
+
|
|
33
|
+
- Initial release
|
data/README.md
CHANGED
|
@@ -1,347 +1,347 @@
|
|
|
1
|
-
<p align="center">
|
|
2
|
-
<img src='./img/logo.png'>
|
|
3
|
-
</p>
|
|
4
|
-
|
|
5
|
-
<h1 align="center">RPG Maker Database Tool</h1>
|
|
6
|
-
<h3 align="center">This extension should be used for development purposes only!</h3>
|
|
7
|
-
|
|
8
|
-
## Table of contents
|
|
9
|
-
|
|
10
|
-
- [Table of contents](#table-of-contents)
|
|
11
|
-
- [Introduction](#introduction)
|
|
12
|
-
- [Features](#features)
|
|
13
|
-
- [Screenshots](#screenshots)
|
|
14
|
-
- [Main Menu](#main-menu)
|
|
15
|
-
- [Settings Menu](#settings-menu)
|
|
16
|
-
- [Export Menu](#export-menu)
|
|
17
|
-
- [Import Menu](#import-menu)
|
|
18
|
-
- [Requirements](#requirements)
|
|
19
|
-
- [Installation](#installation)
|
|
20
|
-
- [Usage](#usage)
|
|
21
|
-
- [Command Syntax](#command-syntax)
|
|
22
|
-
- [Basic Information](#basic-information)
|
|
23
|
-
- [Skip CLI Menu](#skip-cli-menu)
|
|
24
|
-
- [Options](#options)
|
|
25
|
-
- [--debug](#--debug)
|
|
26
|
-
- [--backup, --no-backup](#--backup---no-backup)
|
|
27
|
-
- [-d, --directory](#-d---directory)
|
|
28
|
-
- [-t, --type](#-t---type)
|
|
29
|
-
- [-f, --files](#-f---files)
|
|
30
|
-
- [-i, --ids](#-i---ids)
|
|
31
|
-
- [-a, --action](#-a---action)
|
|
32
|
-
- [-v, --version](#-v---version)
|
|
33
|
-
- [-h, --help](#-h---help)
|
|
34
|
-
- [Known Issues](#known-issues)
|
|
35
|
-
- [Planned](#planned)
|
|
36
|
-
- [Contributing](#contributing)
|
|
37
|
-
- [License](#license)
|
|
38
|
-
- [Code of Conduct](#code-of-conduct)
|
|
39
|
-
|
|
40
|
-
## Introduction
|
|
41
|
-
|
|
42
|
-
RGSS Database is a tool designed for developers to export and import the database files of a game created in RPG Maker.
|
|
43
|
-
|
|
44
|
-
This gem is compatible with any RPG Maker editor based on RGSS, including:
|
|
45
|
-
|
|
46
|
-
- RPG Maker XP
|
|
47
|
-
- RPG Maker VX
|
|
48
|
-
- RPG Maker VX Ace
|
|
49
|
-
|
|
50
|
-
The purpose of this tool is to provide version control features on the RPG Maker database files if you are working on your game with a team and using any version control software.
|
|
51
|
-
|
|
52
|
-
Now, with JSON/YAML files you can see what's changed between versions on the database, something that was impossible with the RPG Maker binary format.
|
|
53
|
-
|
|
54
|
-
The only tool that does this that I know of is [rvpacker](https://github.com/ymaxkrapzv/rvpacker), but I haven't been able to get it to work and it doesn't seem to be maintained by anyone anymore, so I made my own tool for this.
|
|
55
|
-
|
|
56
|
-
Also, I have included some other cool features you may find useful!
|
|
57
|
-
|
|
58
|
-
List of all supported RPG Maker database files:
|
|
59
|
-
|
|
60
|
-
- Actors
|
|
61
|
-
- Animations
|
|
62
|
-
- Areas
|
|
63
|
-
- Armors
|
|
64
|
-
- Classes
|
|
65
|
-
- CommonEvents
|
|
66
|
-
- Enemies
|
|
67
|
-
- Items
|
|
68
|
-
- Map[001, 002, 003...]
|
|
69
|
-
- MapInfos
|
|
70
|
-
- Skills
|
|
71
|
-
- States
|
|
72
|
-
- System
|
|
73
|
-
- Tilesets
|
|
74
|
-
- Troops
|
|
75
|
-
- Weapons
|
|
76
|
-
|
|
77
|
-
The **Scripts database file is not supported** for
|
|
78
|
-
a few reasons:
|
|
79
|
-
|
|
80
|
-
- The format of the scripts database file is very different from the rest of the database files
|
|
81
|
-
- The scripts database file is just a collection of ruby script files
|
|
82
|
-
- These ruby script files depend (heavily) on a load order
|
|
83
|
-
- If this load order does not persist between import and export operations, you will lose this order and (probably) cause a lot of troubles on your project
|
|
84
|
-
- Script files can have duplicated names
|
|
85
|
-
- This can cause problems if these scripts are extracted individually
|
|
86
|
-
- Script file contents are compressed/decompressed
|
|
87
|
-
- It would not be just "plug-and-play"
|
|
88
|
-
- Support for this database file would be very basic and limited
|
|
89
|
-
- **I have made a [Visual Studio Code extension](https://github.com/SnowSzn/rgss-script-editor) which handles this file much better than this application could do**
|
|
90
|
-
- You can check out the features this VS Code extension offers on its repo.
|
|
91
|
-
|
|
92
|
-
## Features
|
|
93
|
-
|
|
94
|
-
- **Automatic detection of RPG Maker version**
|
|
95
|
-
- The RPG Maker version will be automatically detected when opening the data folder
|
|
96
|
-
- If the version cannot be determined, the application won't allow to perform any action to protect the data from corruption
|
|
97
|
-
- **Export RPG Maker database files**
|
|
98
|
-
- You can export all your RPG Maker database files into human-readable data files
|
|
99
|
-
- Supported file types:
|
|
100
|
-
- JSON
|
|
101
|
-
- YAML
|
|
102
|
-
- Alternatively, you can export specific files and also, specific objects inside some database files
|
|
103
|
-
- These files with custom objects are labeled like `Actors_custom`, `Items_custom`...
|
|
104
|
-
- You can also export objects into the binary format
|
|
105
|
-
- The binary file format will be determined based on the RPG Maker version
|
|
106
|
-
- **Import Extracted data into RPG Maker**
|
|
107
|
-
- You can import all your extracted data files into the RPG Maker editor
|
|
108
|
-
- You can import custom data files that merge them with the current RPG Maker data
|
|
109
|
-
- Any external data file created with specific objects
|
|
110
|
-
- All objects will be appended at the end to avoid problems
|
|
111
|
-
- **You must close the RPG Maker editor before importing data!**
|
|
112
|
-
- RPG Maker cannot load data files again if it is already running
|
|
113
|
-
- **Backup Creation**
|
|
114
|
-
- All your database data will be backed up every time you import data into RPG Maker as a security measure
|
|
115
|
-
- You can disable this behavior with a flag (see [options](#options))
|
|
116
|
-
|
|
117
|
-
## Screenshots
|
|
118
|
-
|
|
119
|
-
### Main Menu
|
|
120
|
-
|
|
121
|
-
|
|
122
|
-
|
|
123
|
-
### Settings Menu
|
|
124
|
-
|
|
125
|
-
|
|
126
|
-
|
|
127
|
-
### Export Menu
|
|
128
|
-
|
|
129
|
-
|
|
130
|
-
|
|
131
|
-
### Import Menu
|
|
132
|
-
|
|
133
|
-
|
|
134
|
-
|
|
135
|
-
## Requirements
|
|
136
|
-
|
|
137
|
-
- [Ruby v3.0+](https://www.ruby-lang.org/en/downloads/)
|
|
138
|
-
- [RPG Maker Editor](https://www.rpgmakerweb.com/)
|
|
139
|
-
|
|
140
|
-
## Installation
|
|
141
|
-
|
|
142
|
-
The gem is hosted at [RubyGems](https://rubygems.org/gems/rgss_db)
|
|
143
|
-
|
|
144
|
-
You can install this gem using the following command:
|
|
145
|
-
|
|
146
|
-
$ gem install rgss_db
|
|
147
|
-
|
|
148
|
-
## Usage
|
|
149
|
-
|
|
150
|
-
### Command Syntax
|
|
151
|
-
|
|
152
|
-
```sh
|
|
153
|
-
rgss-db data_directory [options]
|
|
154
|
-
```
|
|
155
|
-
|
|
156
|
-
### Basic Information
|
|
157
|
-
|
|
158
|
-
You can simply use this tool by calling the rgss-db command and supplying a RPG Maker data path:
|
|
159
|
-
|
|
160
|
-
```sh
|
|
161
|
-
# Opens the current directory
|
|
162
|
-
rgss-db .
|
|
163
|
-
```
|
|
164
|
-
|
|
165
|
-
The path needs to be the data folder where all binary database files are stored, otherwise the app won't work.
|
|
166
|
-
|
|
167
|
-
This will open the application's menu where you can manually perform the desired action.
|
|
168
|
-
|
|
169
|
-
The application has a number of options that allow you to customize the behavior and output of the application, you can check more about this below.
|
|
170
|
-
|
|
171
|
-
#### Skip CLI Menu
|
|
172
|
-
|
|
173
|
-
You can use the `-a` (`--action`) flag to skip the application's CLI menu, this will perform the specified action and finish execution, see more at [-a, --action](#-a---action)
|
|
174
|
-
|
|
175
|
-
### Options
|
|
176
|
-
|
|
177
|
-
#### --debug
|
|
178
|
-
|
|
179
|
-
You can set the application's debug mode with the following option.
|
|
180
|
-
|
|
181
|
-
A log file will be created inside the application's working directory.
|
|
182
|
-
|
|
183
|
-
```sh
|
|
184
|
-
rgss-db . --debug 0 # Disables debug functionality (default)
|
|
185
|
-
rgss-db . --debug 1 # Enables debug error level
|
|
186
|
-
rgss-db . --debug 2 # Enables debug warning level
|
|
187
|
-
rgss-db . --debug 3 # Enables debug info level
|
|
188
|
-
```
|
|
189
|
-
|
|
190
|
-
#### --backup, --no-backup
|
|
191
|
-
|
|
192
|
-
You can enable/disable the automatic backup creation with these flags.
|
|
193
|
-
|
|
194
|
-
```sh
|
|
195
|
-
rgss-db . --backup # Backups are created (default)
|
|
196
|
-
rgss-db . --no-backup # Backups are not created
|
|
197
|
-
```
|
|
198
|
-
|
|
199
|
-
#### -d, --directory
|
|
200
|
-
|
|
201
|
-
Sets the application's working directory (used for exporting and importing)
|
|
202
|
-
|
|
203
|
-
All extracted files will be created inside this directory.
|
|
204
|
-
|
|
205
|
-
```sh
|
|
206
|
-
rgss-db . -d "./rgss-db" # Data folder relative (default)
|
|
207
|
-
rgss-db . -d "C:/Absolute/Folder" # Absolute path
|
|
208
|
-
```
|
|
209
|
-
|
|
210
|
-
#### -t, --type
|
|
211
|
-
|
|
212
|
-
Sets the application's file format (used for exporting)
|
|
213
|
-
|
|
214
|
-
Supported file format types:
|
|
215
|
-
|
|
216
|
-
- YAML
|
|
217
|
-
- JSON
|
|
218
|
-
- BINARY
|
|
219
|
-
|
|
220
|
-
```sh
|
|
221
|
-
rgss-db . -t yaml # Uses YAML format (default)
|
|
222
|
-
rgss-db . -t json # Uses JSON format
|
|
223
|
-
rgss-db . -t binary # Uses Binary format
|
|
224
|
-
```
|
|
225
|
-
|
|
226
|
-
#### -f, --files
|
|
227
|
-
|
|
228
|
-
Sets a list of data files that will be affected by the action.
|
|
229
|
-
|
|
230
|
-
If not provided, it will consider all data files.
|
|
231
|
-
|
|
232
|
-
```sh
|
|
233
|
-
rgss-db . -f Actors.rvdata2 # Selects only the Actors file
|
|
234
|
-
rgss-db . -f Actors.json # Selects only the Actors file
|
|
235
|
-
rgss-db . -f Actors.rxdata Items.rxdata
|
|
236
|
-
```
|
|
237
|
-
|
|
238
|
-
#### -i, --ids
|
|
239
|
-
|
|
240
|
-
Sets a list of objects that will be affected by an action (per data file)
|
|
241
|
-
|
|
242
|
-
This option only works for data files that supports this behavior:
|
|
243
|
-
|
|
244
|
-
- Actors
|
|
245
|
-
- Animations
|
|
246
|
-
- Areas
|
|
247
|
-
- Armors
|
|
248
|
-
- Classes
|
|
249
|
-
- CommonEvents
|
|
250
|
-
- Enemies
|
|
251
|
-
- Items
|
|
252
|
-
- MapInfos
|
|
253
|
-
- Skills
|
|
254
|
-
- States
|
|
255
|
-
- Tilesets
|
|
256
|
-
- Troops
|
|
257
|
-
- Weapons
|
|
258
|
-
|
|
259
|
-
This option can be repeated for each data file provided, meaning that if you use:
|
|
260
|
-
|
|
261
|
-
```sh
|
|
262
|
-
# Selects the Actors.rvdata2, Items.rvdata2 and Weapons.rvdata2 database files
|
|
263
|
-
rgss-db . -f Actors.rvdata2 Items.rvdata2 Weapons.rvdata2
|
|
264
|
-
```
|
|
265
|
-
|
|
266
|
-
You can use the `-i` option three times to specify the IDs for each file, in the same order they are in the `-f` option
|
|
267
|
-
|
|
268
|
-
```sh
|
|
269
|
-
# Object IDs received:
|
|
270
|
-
# - Actors.rvdata2 => [420, 123]
|
|
271
|
-
# - Items.rvdata2 => [73, 3, 7]
|
|
272
|
-
# - Weapons.rvdata2 => [69, 79, 89]
|
|
273
|
-
rgss-db . -f Actors.rvdata2 Items.rvdata2 Weapons.rvdata2 -i 420 123 -i 73 3 7 -i 69 79 89
|
|
274
|
-
```
|
|
275
|
-
|
|
276
|
-
#### -a, --action
|
|
277
|
-
|
|
278
|
-
You can skip the application's CLI menu completely if you supply a supported action.
|
|
279
|
-
|
|
280
|
-
The application will start and perform the action, using the given files and object IDs (if any) and close itself when the action finishes
|
|
281
|
-
|
|
282
|
-
These are the possible actions:
|
|
283
|
-
|
|
284
|
-
- `export`: Exports RPG Maker database
|
|
285
|
-
- `export_custom`: Exports specific objects from the RPG Maker database
|
|
286
|
-
- `import`: Imports external data into the RPG Maker database
|
|
287
|
-
- `import_custom`: Imports custom external data into the RPG Maker database (merge)
|
|
288
|
-
|
|
289
|
-
Here's a few examples with the action option **using the default application directory**:
|
|
290
|
-
|
|
291
|
-
```sh
|
|
292
|
-
# Opens the current directory and export all data
|
|
293
|
-
rgss-db . -a export
|
|
294
|
-
|
|
295
|
-
# Opens the current directory and import all data
|
|
296
|
-
rgss-db . -a import
|
|
297
|
-
|
|
298
|
-
# Opens the current directory and export only the Items file
|
|
299
|
-
rgss-db . -a export -f Items.rvdata2
|
|
300
|
-
|
|
301
|
-
# Opens the current directory and export only the object with ID: 100 from the Items file
|
|
302
|
-
rgss-db . -a export_custom -f Items.rvdata2 -i 100
|
|
303
|
-
|
|
304
|
-
# Opens the current directory and export only the object with ID: 100 from the Items file to a JSON file
|
|
305
|
-
rgss-db . -a export_custom -f Items.rvdata2 -i 100 -t json
|
|
306
|
-
```
|
|
307
|
-
|
|
308
|
-
#### -v, --version
|
|
309
|
-
|
|
310
|
-
Prints the application version and exit.
|
|
311
|
-
|
|
312
|
-
```sh
|
|
313
|
-
rgss-db -v
|
|
314
|
-
rgss-db --version
|
|
315
|
-
```
|
|
316
|
-
|
|
317
|
-
#### -h, --help
|
|
318
|
-
|
|
319
|
-
Prints a help message on the standard output and exit.
|
|
320
|
-
|
|
321
|
-
```sh
|
|
322
|
-
rgss-db -h
|
|
323
|
-
rgss-db --help
|
|
324
|
-
```
|
|
325
|
-
|
|
326
|
-
## Known Issues
|
|
327
|
-
|
|
328
|
-
- None
|
|
329
|
-
|
|
330
|
-
## Planned
|
|
331
|
-
|
|
332
|
-
- Code Maintenance
|
|
333
|
-
- Feature Requests
|
|
334
|
-
|
|
335
|
-
## Contributing
|
|
336
|
-
|
|
337
|
-
Bug reports and pull requests are welcome on GitHub at the [issue tracker](https://github.com/SnowSzn/rgss-db-cli/issues).
|
|
338
|
-
|
|
339
|
-
This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/SnowSzn/rgss-db-cli/blob/main/CODE_OF_CONDUCT.md).
|
|
340
|
-
|
|
341
|
-
## License
|
|
342
|
-
|
|
343
|
-
The gem is available as open source under the terms of the [GNU General Public License version 3 License](https://opensource.org/license/gpl-3-0).
|
|
344
|
-
|
|
345
|
-
## Code of Conduct
|
|
346
|
-
|
|
347
|
-
Everyone interacting in the RGSS Database project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/SnowSzn/rgss-db-cli/blob/main/CODE_OF_CONDUCT.md).
|
|
1
|
+
<p align="center">
|
|
2
|
+
<img src='./img/logo.png'>
|
|
3
|
+
</p>
|
|
4
|
+
|
|
5
|
+
<h1 align="center">RPG Maker Database Tool</h1>
|
|
6
|
+
<h3 align="center">This extension should be used for development purposes only!</h3>
|
|
7
|
+
|
|
8
|
+
## Table of contents
|
|
9
|
+
|
|
10
|
+
- [Table of contents](#table-of-contents)
|
|
11
|
+
- [Introduction](#introduction)
|
|
12
|
+
- [Features](#features)
|
|
13
|
+
- [Screenshots](#screenshots)
|
|
14
|
+
- [Main Menu](#main-menu)
|
|
15
|
+
- [Settings Menu](#settings-menu)
|
|
16
|
+
- [Export Menu](#export-menu)
|
|
17
|
+
- [Import Menu](#import-menu)
|
|
18
|
+
- [Requirements](#requirements)
|
|
19
|
+
- [Installation](#installation)
|
|
20
|
+
- [Usage](#usage)
|
|
21
|
+
- [Command Syntax](#command-syntax)
|
|
22
|
+
- [Basic Information](#basic-information)
|
|
23
|
+
- [Skip CLI Menu](#skip-cli-menu)
|
|
24
|
+
- [Options](#options)
|
|
25
|
+
- [--debug](#--debug)
|
|
26
|
+
- [--backup, --no-backup](#--backup---no-backup)
|
|
27
|
+
- [-d, --directory](#-d---directory)
|
|
28
|
+
- [-t, --type](#-t---type)
|
|
29
|
+
- [-f, --files](#-f---files)
|
|
30
|
+
- [-i, --ids](#-i---ids)
|
|
31
|
+
- [-a, --action](#-a---action)
|
|
32
|
+
- [-v, --version](#-v---version)
|
|
33
|
+
- [-h, --help](#-h---help)
|
|
34
|
+
- [Known Issues](#known-issues)
|
|
35
|
+
- [Planned](#planned)
|
|
36
|
+
- [Contributing](#contributing)
|
|
37
|
+
- [License](#license)
|
|
38
|
+
- [Code of Conduct](#code-of-conduct)
|
|
39
|
+
|
|
40
|
+
## Introduction
|
|
41
|
+
|
|
42
|
+
RGSS Database is a tool designed for developers to export and import the database files of a game created in RPG Maker.
|
|
43
|
+
|
|
44
|
+
This gem is compatible with any RPG Maker editor based on RGSS, including:
|
|
45
|
+
|
|
46
|
+
- RPG Maker XP
|
|
47
|
+
- RPG Maker VX
|
|
48
|
+
- RPG Maker VX Ace
|
|
49
|
+
|
|
50
|
+
The purpose of this tool is to provide version control features on the RPG Maker database files if you are working on your game with a team and using any version control software.
|
|
51
|
+
|
|
52
|
+
Now, with JSON/YAML files you can see what's changed between versions on the database, something that was impossible with the RPG Maker binary format.
|
|
53
|
+
|
|
54
|
+
The only tool that does this that I know of is [rvpacker](https://github.com/ymaxkrapzv/rvpacker), but I haven't been able to get it to work and it doesn't seem to be maintained by anyone anymore, so I made my own tool for this.
|
|
55
|
+
|
|
56
|
+
Also, I have included some other cool features you may find useful!
|
|
57
|
+
|
|
58
|
+
List of all supported RPG Maker database files:
|
|
59
|
+
|
|
60
|
+
- Actors
|
|
61
|
+
- Animations
|
|
62
|
+
- Areas
|
|
63
|
+
- Armors
|
|
64
|
+
- Classes
|
|
65
|
+
- CommonEvents
|
|
66
|
+
- Enemies
|
|
67
|
+
- Items
|
|
68
|
+
- Map[001, 002, 003...]
|
|
69
|
+
- MapInfos
|
|
70
|
+
- Skills
|
|
71
|
+
- States
|
|
72
|
+
- System
|
|
73
|
+
- Tilesets
|
|
74
|
+
- Troops
|
|
75
|
+
- Weapons
|
|
76
|
+
|
|
77
|
+
The **Scripts database file is not supported** for
|
|
78
|
+
a few reasons:
|
|
79
|
+
|
|
80
|
+
- The format of the scripts database file is very different from the rest of the database files
|
|
81
|
+
- The scripts database file is just a collection of ruby script files
|
|
82
|
+
- These ruby script files depend (heavily) on a load order
|
|
83
|
+
- If this load order does not persist between import and export operations, you will lose this order and (probably) cause a lot of troubles on your project
|
|
84
|
+
- Script files can have duplicated names
|
|
85
|
+
- This can cause problems if these scripts are extracted individually
|
|
86
|
+
- Script file contents are compressed/decompressed
|
|
87
|
+
- It would not be just "plug-and-play"
|
|
88
|
+
- Support for this database file would be very basic and limited
|
|
89
|
+
- **I have made a [Visual Studio Code extension](https://github.com/SnowSzn/rgss-script-editor) which handles this file much better than this application could do**
|
|
90
|
+
- You can check out the features this VS Code extension offers on its repo.
|
|
91
|
+
|
|
92
|
+
## Features
|
|
93
|
+
|
|
94
|
+
- **Automatic detection of RPG Maker version**
|
|
95
|
+
- The RPG Maker version will be automatically detected when opening the data folder
|
|
96
|
+
- If the version cannot be determined, the application won't allow to perform any action to protect the data from corruption
|
|
97
|
+
- **Export RPG Maker database files**
|
|
98
|
+
- You can export all your RPG Maker database files into human-readable data files
|
|
99
|
+
- Supported file types:
|
|
100
|
+
- JSON
|
|
101
|
+
- YAML
|
|
102
|
+
- Alternatively, you can export specific files and also, specific objects inside some database files
|
|
103
|
+
- These files with custom objects are labeled like `Actors_custom`, `Items_custom`...
|
|
104
|
+
- You can also export objects into the binary format
|
|
105
|
+
- The binary file format will be determined based on the RPG Maker version
|
|
106
|
+
- **Import Extracted data into RPG Maker**
|
|
107
|
+
- You can import all your extracted data files into the RPG Maker editor
|
|
108
|
+
- You can import custom data files that merge them with the current RPG Maker data
|
|
109
|
+
- Any external data file created with specific objects
|
|
110
|
+
- All objects will be appended at the end to avoid problems
|
|
111
|
+
- **You must close the RPG Maker editor before importing data!**
|
|
112
|
+
- RPG Maker cannot load data files again if it is already running
|
|
113
|
+
- **Backup Creation**
|
|
114
|
+
- All your database data will be backed up every time you import data into RPG Maker as a security measure
|
|
115
|
+
- You can disable this behavior with a flag (see [options](#options))
|
|
116
|
+
|
|
117
|
+
## Screenshots
|
|
118
|
+
|
|
119
|
+
### Main Menu
|
|
120
|
+
|
|
121
|
+
|
|
122
|
+
|
|
123
|
+
### Settings Menu
|
|
124
|
+
|
|
125
|
+
|
|
126
|
+
|
|
127
|
+
### Export Menu
|
|
128
|
+
|
|
129
|
+
|
|
130
|
+
|
|
131
|
+
### Import Menu
|
|
132
|
+
|
|
133
|
+
|
|
134
|
+
|
|
135
|
+
## Requirements
|
|
136
|
+
|
|
137
|
+
- [Ruby v3.0+](https://www.ruby-lang.org/en/downloads/)
|
|
138
|
+
- [RPG Maker Editor](https://www.rpgmakerweb.com/)
|
|
139
|
+
|
|
140
|
+
## Installation
|
|
141
|
+
|
|
142
|
+
The gem is hosted at [RubyGems](https://rubygems.org/gems/rgss_db)
|
|
143
|
+
|
|
144
|
+
You can install this gem using the following command:
|
|
145
|
+
|
|
146
|
+
$ gem install rgss_db
|
|
147
|
+
|
|
148
|
+
## Usage
|
|
149
|
+
|
|
150
|
+
### Command Syntax
|
|
151
|
+
|
|
152
|
+
```sh
|
|
153
|
+
rgss-db data_directory [options]
|
|
154
|
+
```
|
|
155
|
+
|
|
156
|
+
### Basic Information
|
|
157
|
+
|
|
158
|
+
You can simply use this tool by calling the rgss-db command and supplying a RPG Maker data path:
|
|
159
|
+
|
|
160
|
+
```sh
|
|
161
|
+
# Opens the current directory
|
|
162
|
+
rgss-db .
|
|
163
|
+
```
|
|
164
|
+
|
|
165
|
+
The path needs to be the data folder where all binary database files are stored, otherwise the app won't work.
|
|
166
|
+
|
|
167
|
+
This will open the application's menu where you can manually perform the desired action.
|
|
168
|
+
|
|
169
|
+
The application has a number of options that allow you to customize the behavior and output of the application, you can check more about this below.
|
|
170
|
+
|
|
171
|
+
#### Skip CLI Menu
|
|
172
|
+
|
|
173
|
+
You can use the `-a` (`--action`) flag to skip the application's CLI menu, this will perform the specified action and finish execution, see more at [-a, --action](#-a---action)
|
|
174
|
+
|
|
175
|
+
### Options
|
|
176
|
+
|
|
177
|
+
#### --debug
|
|
178
|
+
|
|
179
|
+
You can set the application's debug mode with the following option.
|
|
180
|
+
|
|
181
|
+
A log file will be created inside the application's working directory.
|
|
182
|
+
|
|
183
|
+
```sh
|
|
184
|
+
rgss-db . --debug 0 # Disables debug functionality (default)
|
|
185
|
+
rgss-db . --debug 1 # Enables debug error level
|
|
186
|
+
rgss-db . --debug 2 # Enables debug warning level
|
|
187
|
+
rgss-db . --debug 3 # Enables debug info level
|
|
188
|
+
```
|
|
189
|
+
|
|
190
|
+
#### --backup, --no-backup
|
|
191
|
+
|
|
192
|
+
You can enable/disable the automatic backup creation with these flags.
|
|
193
|
+
|
|
194
|
+
```sh
|
|
195
|
+
rgss-db . --backup # Backups are created (default)
|
|
196
|
+
rgss-db . --no-backup # Backups are not created
|
|
197
|
+
```
|
|
198
|
+
|
|
199
|
+
#### -d, --directory
|
|
200
|
+
|
|
201
|
+
Sets the application's working directory (used for exporting and importing)
|
|
202
|
+
|
|
203
|
+
All extracted files will be created inside this directory.
|
|
204
|
+
|
|
205
|
+
```sh
|
|
206
|
+
rgss-db . -d "./rgss-db" # Data folder relative (default)
|
|
207
|
+
rgss-db . -d "C:/Absolute/Folder" # Absolute path
|
|
208
|
+
```
|
|
209
|
+
|
|
210
|
+
#### -t, --type
|
|
211
|
+
|
|
212
|
+
Sets the application's file format (used for exporting)
|
|
213
|
+
|
|
214
|
+
Supported file format types:
|
|
215
|
+
|
|
216
|
+
- YAML
|
|
217
|
+
- JSON
|
|
218
|
+
- BINARY
|
|
219
|
+
|
|
220
|
+
```sh
|
|
221
|
+
rgss-db . -t yaml # Uses YAML format (default)
|
|
222
|
+
rgss-db . -t json # Uses JSON format
|
|
223
|
+
rgss-db . -t binary # Uses Binary format
|
|
224
|
+
```
|
|
225
|
+
|
|
226
|
+
#### -f, --files
|
|
227
|
+
|
|
228
|
+
Sets a list of data files that will be affected by the action.
|
|
229
|
+
|
|
230
|
+
If not provided, it will consider all data files.
|
|
231
|
+
|
|
232
|
+
```sh
|
|
233
|
+
rgss-db . -f Actors.rvdata2 # Selects only the Actors file
|
|
234
|
+
rgss-db . -f Actors.json # Selects only the Actors file
|
|
235
|
+
rgss-db . -f Actors.rxdata Items.rxdata
|
|
236
|
+
```
|
|
237
|
+
|
|
238
|
+
#### -i, --ids
|
|
239
|
+
|
|
240
|
+
Sets a list of objects that will be affected by an action (per data file)
|
|
241
|
+
|
|
242
|
+
This option only works for data files that supports this behavior:
|
|
243
|
+
|
|
244
|
+
- Actors
|
|
245
|
+
- Animations
|
|
246
|
+
- Areas
|
|
247
|
+
- Armors
|
|
248
|
+
- Classes
|
|
249
|
+
- CommonEvents
|
|
250
|
+
- Enemies
|
|
251
|
+
- Items
|
|
252
|
+
- MapInfos
|
|
253
|
+
- Skills
|
|
254
|
+
- States
|
|
255
|
+
- Tilesets
|
|
256
|
+
- Troops
|
|
257
|
+
- Weapons
|
|
258
|
+
|
|
259
|
+
This option can be repeated for each data file provided, meaning that if you use:
|
|
260
|
+
|
|
261
|
+
```sh
|
|
262
|
+
# Selects the Actors.rvdata2, Items.rvdata2 and Weapons.rvdata2 database files
|
|
263
|
+
rgss-db . -f Actors.rvdata2 Items.rvdata2 Weapons.rvdata2
|
|
264
|
+
```
|
|
265
|
+
|
|
266
|
+
You can use the `-i` option three times to specify the IDs for each file, in the same order they are in the `-f` option
|
|
267
|
+
|
|
268
|
+
```sh
|
|
269
|
+
# Object IDs received:
|
|
270
|
+
# - Actors.rvdata2 => [420, 123]
|
|
271
|
+
# - Items.rvdata2 => [73, 3, 7]
|
|
272
|
+
# - Weapons.rvdata2 => [69, 79, 89]
|
|
273
|
+
rgss-db . -f Actors.rvdata2 Items.rvdata2 Weapons.rvdata2 -i 420 123 -i 73 3 7 -i 69 79 89
|
|
274
|
+
```
|
|
275
|
+
|
|
276
|
+
#### -a, --action
|
|
277
|
+
|
|
278
|
+
You can skip the application's CLI menu completely if you supply a supported action.
|
|
279
|
+
|
|
280
|
+
The application will start and perform the action, using the given files and object IDs (if any) and close itself when the action finishes
|
|
281
|
+
|
|
282
|
+
These are the possible actions:
|
|
283
|
+
|
|
284
|
+
- `export`: Exports RPG Maker database
|
|
285
|
+
- `export_custom`: Exports specific objects from the RPG Maker database
|
|
286
|
+
- `import`: Imports external data into the RPG Maker database
|
|
287
|
+
- `import_custom`: Imports custom external data into the RPG Maker database (merge)
|
|
288
|
+
|
|
289
|
+
Here's a few examples with the action option **using the default application directory**:
|
|
290
|
+
|
|
291
|
+
```sh
|
|
292
|
+
# Opens the current directory and export all data
|
|
293
|
+
rgss-db . -a export
|
|
294
|
+
|
|
295
|
+
# Opens the current directory and import all data
|
|
296
|
+
rgss-db . -a import
|
|
297
|
+
|
|
298
|
+
# Opens the current directory and export only the Items file
|
|
299
|
+
rgss-db . -a export -f Items.rvdata2
|
|
300
|
+
|
|
301
|
+
# Opens the current directory and export only the object with ID: 100 from the Items file
|
|
302
|
+
rgss-db . -a export_custom -f Items.rvdata2 -i 100
|
|
303
|
+
|
|
304
|
+
# Opens the current directory and export only the object with ID: 100 from the Items file to a JSON file
|
|
305
|
+
rgss-db . -a export_custom -f Items.rvdata2 -i 100 -t json
|
|
306
|
+
```
|
|
307
|
+
|
|
308
|
+
#### -v, --version
|
|
309
|
+
|
|
310
|
+
Prints the application version and exit.
|
|
311
|
+
|
|
312
|
+
```sh
|
|
313
|
+
rgss-db -v
|
|
314
|
+
rgss-db --version
|
|
315
|
+
```
|
|
316
|
+
|
|
317
|
+
#### -h, --help
|
|
318
|
+
|
|
319
|
+
Prints a help message on the standard output and exit.
|
|
320
|
+
|
|
321
|
+
```sh
|
|
322
|
+
rgss-db -h
|
|
323
|
+
rgss-db --help
|
|
324
|
+
```
|
|
325
|
+
|
|
326
|
+
## Known Issues
|
|
327
|
+
|
|
328
|
+
- None
|
|
329
|
+
|
|
330
|
+
## Planned
|
|
331
|
+
|
|
332
|
+
- Code Maintenance
|
|
333
|
+
- Feature Requests
|
|
334
|
+
|
|
335
|
+
## Contributing
|
|
336
|
+
|
|
337
|
+
Bug reports and pull requests are welcome on GitHub at the [issue tracker](https://github.com/SnowSzn/rgss-db-cli/issues).
|
|
338
|
+
|
|
339
|
+
This project is intended to be a safe, welcoming space for collaboration, and contributors are expected to adhere to the [code of conduct](https://github.com/SnowSzn/rgss-db-cli/blob/main/CODE_OF_CONDUCT.md).
|
|
340
|
+
|
|
341
|
+
## License
|
|
342
|
+
|
|
343
|
+
The gem is available as open source under the terms of the [GNU General Public License version 3 License](https://opensource.org/license/gpl-3-0).
|
|
344
|
+
|
|
345
|
+
## Code of Conduct
|
|
346
|
+
|
|
347
|
+
Everyone interacting in the RGSS Database project's codebases, issue trackers, chat rooms and mailing lists is expected to follow the [code of conduct](https://github.com/SnowSzn/rgss-db-cli/blob/main/CODE_OF_CONDUCT.md).
|
|
@@ -513,4 +513,46 @@ module RgssDb
|
|
|
513
513
|
end
|
|
514
514
|
end
|
|
515
515
|
end
|
|
516
|
+
|
|
517
|
+
#
|
|
518
|
+
# RPG Maker map data file
|
|
519
|
+
#
|
|
520
|
+
# This class expects the object to be a RPG::Map instance
|
|
521
|
+
#
|
|
522
|
+
# This class forces map events hash keys to be a number.
|
|
523
|
+
#
|
|
524
|
+
# **Reason: Creating a DataFile instance from a RPG Maker Map JSON file provokes undesired behavior.**
|
|
525
|
+
#
|
|
526
|
+
# JSON only allows key names to be strings, so all keys of the hash will be converted to string.
|
|
527
|
+
#
|
|
528
|
+
# This is undesired behavior because RPG Maker editor requires the map events hash keys to be numbers.
|
|
529
|
+
#
|
|
530
|
+
# So we need to convert all keys read from the JSON file to integers when importing the JSON file into the
|
|
531
|
+
# RPG Maker database, hence the inclusion of this class specification from DataFileHash.
|
|
532
|
+
#
|
|
533
|
+
# Otherwise the RPG Maker editor will fail to show the map events even though data still exists.
|
|
534
|
+
#
|
|
535
|
+
class DataFileMap < DataFile
|
|
536
|
+
# Data file object (not processed)
|
|
537
|
+
# @return [RPG::Map]
|
|
538
|
+
attr_reader :object
|
|
539
|
+
|
|
540
|
+
#
|
|
541
|
+
# Serializes the data file's object
|
|
542
|
+
#
|
|
543
|
+
# This method prepares the object as a RPG::Map object
|
|
544
|
+
#
|
|
545
|
+
# @return [Object]
|
|
546
|
+
#
|
|
547
|
+
def serialize
|
|
548
|
+
# Dups the original object
|
|
549
|
+
processed_object = object.dup
|
|
550
|
+
|
|
551
|
+
# Applies the selected object IDs (if any)
|
|
552
|
+
processed_object.events.transform_keys! { |key| key.to_s.to_i }
|
|
553
|
+
|
|
554
|
+
# Returns the formatted object
|
|
555
|
+
processed_object
|
|
556
|
+
end
|
|
557
|
+
end
|
|
516
558
|
end
|
|
@@ -68,11 +68,21 @@ module RgssDb
|
|
|
68
68
|
raise "could not find a valid data file type for the file: '#{data_file}'" if type.nil?
|
|
69
69
|
|
|
70
70
|
# Checks for a specific data file usage (bulk-check)
|
|
71
|
-
|
|
72
|
-
|
|
73
|
-
|
|
71
|
+
if FACTORY_ARRAY.any? { |f| f.casecmp?(type) }
|
|
72
|
+
# Object should be treated using a data file for arrays
|
|
73
|
+
return DataFileArray.new(type, data_file, object)
|
|
74
|
+
elsif FACTORY_HASH.any? { |f| f.casecmp?(type) }
|
|
75
|
+
# Object should be treated using a data file for hashes
|
|
76
|
+
return DataFileHash.new(type, data_file, object)
|
|
77
|
+
elsif FACTORY_HASH_NUMBER.any? { |f| f.casecmp?(type) }
|
|
78
|
+
# Object should be treated using a data file for hashes (forcing keys to numbers)
|
|
79
|
+
return DataFileHashNumber.new(type, data_file, object)
|
|
80
|
+
elsif type.casecmp?(DATA_FILE_MAPS)
|
|
81
|
+
# Object is a RPG Maker RPG::Map instance and should be treated in a special way
|
|
82
|
+
return DataFileMap.new(type, data_file, object)
|
|
83
|
+
end
|
|
74
84
|
|
|
75
|
-
# Assume a base data file
|
|
85
|
+
# Assume a base data file
|
|
76
86
|
DataFile.new(type, data_file, object)
|
|
77
87
|
end
|
|
78
88
|
|
data/lib/rgss_db/version.rb
CHANGED
data/sig/rgss_db.rbs
CHANGED
|
@@ -864,6 +864,33 @@ module RgssDb
|
|
|
864
864
|
def serialize: () -> ::Hash[untyped, untyped]
|
|
865
865
|
end
|
|
866
866
|
|
|
867
|
+
#
|
|
868
|
+
# RPG Maker map data file
|
|
869
|
+
#
|
|
870
|
+
# This class expects the object to be a RPG::Map instance
|
|
871
|
+
#
|
|
872
|
+
# This class forces map events hash keys to be a number.
|
|
873
|
+
#
|
|
874
|
+
# **Reason: Creating a DataFile instance from a RPG Maker Map JSON file provokes undesired behavior.**
|
|
875
|
+
#
|
|
876
|
+
# JSON only allows key names to be strings, so all keys of the hash will be converted to string.
|
|
877
|
+
#
|
|
878
|
+
# This is undesired behavior because RPG Maker editor requires the map events hash keys to be numbers.
|
|
879
|
+
#
|
|
880
|
+
# So we need to convert all keys read from the JSON file to integers when importing the JSON file into the
|
|
881
|
+
# RPG Maker database, hence the inclusion of this class specification from DataFileHash.
|
|
882
|
+
#
|
|
883
|
+
# Otherwise the RPG Maker editor will fail to show the map events even though data still exists.
|
|
884
|
+
class DataFileMap < RgssDb::DataFile
|
|
885
|
+
# Serializes the data file's object
|
|
886
|
+
#
|
|
887
|
+
# This method prepares the object as a RPG::Map object
|
|
888
|
+
def serialize: () -> Object
|
|
889
|
+
|
|
890
|
+
# Data file object (not processed)
|
|
891
|
+
attr_reader object: RPG::Map
|
|
892
|
+
end
|
|
893
|
+
|
|
867
894
|
#
|
|
868
895
|
# Utilities module
|
|
869
896
|
module Utilities
|
metadata
CHANGED
|
@@ -1,14 +1,14 @@
|
|
|
1
1
|
--- !ruby/object:Gem::Specification
|
|
2
2
|
name: rgss_db
|
|
3
3
|
version: !ruby/object:Gem::Version
|
|
4
|
-
version: 1.0.
|
|
4
|
+
version: 1.0.4
|
|
5
5
|
platform: ruby
|
|
6
6
|
authors:
|
|
7
7
|
- SnowSzn
|
|
8
8
|
autorequire:
|
|
9
9
|
bindir: bin
|
|
10
10
|
cert_chain: []
|
|
11
|
-
date:
|
|
11
|
+
date: 2025-03-14 00:00:00.000000000 Z
|
|
12
12
|
dependencies:
|
|
13
13
|
- !ruby/object:Gem::Dependency
|
|
14
14
|
name: colorize
|
|
@@ -58,14 +58,14 @@ dependencies:
|
|
|
58
58
|
requirements:
|
|
59
59
|
- - "~>"
|
|
60
60
|
- !ruby/object:Gem::Version
|
|
61
|
-
version: 3.
|
|
61
|
+
version: '3.2'
|
|
62
62
|
type: :runtime
|
|
63
63
|
prerelease: false
|
|
64
64
|
version_requirements: !ruby/object:Gem::Requirement
|
|
65
65
|
requirements:
|
|
66
66
|
- - "~>"
|
|
67
67
|
- !ruby/object:Gem::Version
|
|
68
|
-
version: 3.
|
|
68
|
+
version: '3.2'
|
|
69
69
|
- !ruby/object:Gem::Dependency
|
|
70
70
|
name: psych
|
|
71
71
|
requirement: !ruby/object:Gem::Requirement
|
|
@@ -184,84 +184,84 @@ dependencies:
|
|
|
184
184
|
requirements:
|
|
185
185
|
- - "~>"
|
|
186
186
|
- !ruby/object:Gem::Version
|
|
187
|
-
version: '1.
|
|
187
|
+
version: '1.74'
|
|
188
188
|
type: :development
|
|
189
189
|
prerelease: false
|
|
190
190
|
version_requirements: !ruby/object:Gem::Requirement
|
|
191
191
|
requirements:
|
|
192
192
|
- - "~>"
|
|
193
193
|
- !ruby/object:Gem::Version
|
|
194
|
-
version: '1.
|
|
194
|
+
version: '1.74'
|
|
195
195
|
- !ruby/object:Gem::Dependency
|
|
196
196
|
name: rubocop-performance
|
|
197
197
|
requirement: !ruby/object:Gem::Requirement
|
|
198
198
|
requirements:
|
|
199
199
|
- - "~>"
|
|
200
200
|
- !ruby/object:Gem::Version
|
|
201
|
-
version: '1.
|
|
201
|
+
version: '1.24'
|
|
202
202
|
type: :development
|
|
203
203
|
prerelease: false
|
|
204
204
|
version_requirements: !ruby/object:Gem::Requirement
|
|
205
205
|
requirements:
|
|
206
206
|
- - "~>"
|
|
207
207
|
- !ruby/object:Gem::Version
|
|
208
|
-
version: '1.
|
|
208
|
+
version: '1.24'
|
|
209
209
|
- !ruby/object:Gem::Dependency
|
|
210
210
|
name: rubocop-rake
|
|
211
211
|
requirement: !ruby/object:Gem::Requirement
|
|
212
212
|
requirements:
|
|
213
213
|
- - "~>"
|
|
214
214
|
- !ruby/object:Gem::Version
|
|
215
|
-
version: 0.
|
|
215
|
+
version: '0.7'
|
|
216
216
|
type: :development
|
|
217
217
|
prerelease: false
|
|
218
218
|
version_requirements: !ruby/object:Gem::Requirement
|
|
219
219
|
requirements:
|
|
220
220
|
- - "~>"
|
|
221
221
|
- !ruby/object:Gem::Version
|
|
222
|
-
version: 0.
|
|
222
|
+
version: '0.7'
|
|
223
223
|
- !ruby/object:Gem::Dependency
|
|
224
224
|
name: rubocop-rspec
|
|
225
225
|
requirement: !ruby/object:Gem::Requirement
|
|
226
226
|
requirements:
|
|
227
227
|
- - "~>"
|
|
228
228
|
- !ruby/object:Gem::Version
|
|
229
|
-
version: '
|
|
229
|
+
version: '3.5'
|
|
230
230
|
type: :development
|
|
231
231
|
prerelease: false
|
|
232
232
|
version_requirements: !ruby/object:Gem::Requirement
|
|
233
233
|
requirements:
|
|
234
234
|
- - "~>"
|
|
235
235
|
- !ruby/object:Gem::Version
|
|
236
|
-
version: '
|
|
236
|
+
version: '3.5'
|
|
237
237
|
- !ruby/object:Gem::Dependency
|
|
238
238
|
name: sord
|
|
239
239
|
requirement: !ruby/object:Gem::Requirement
|
|
240
240
|
requirements:
|
|
241
241
|
- - "~>"
|
|
242
242
|
- !ruby/object:Gem::Version
|
|
243
|
-
version: '
|
|
243
|
+
version: '7.0'
|
|
244
244
|
type: :development
|
|
245
245
|
prerelease: false
|
|
246
246
|
version_requirements: !ruby/object:Gem::Requirement
|
|
247
247
|
requirements:
|
|
248
248
|
- - "~>"
|
|
249
249
|
- !ruby/object:Gem::Version
|
|
250
|
-
version: '
|
|
250
|
+
version: '7.0'
|
|
251
251
|
- !ruby/object:Gem::Dependency
|
|
252
252
|
name: yard
|
|
253
253
|
requirement: !ruby/object:Gem::Requirement
|
|
254
254
|
requirements:
|
|
255
255
|
- - "~>"
|
|
256
256
|
- !ruby/object:Gem::Version
|
|
257
|
-
version: 0.9
|
|
257
|
+
version: '0.9'
|
|
258
258
|
type: :development
|
|
259
259
|
prerelease: false
|
|
260
260
|
version_requirements: !ruby/object:Gem::Requirement
|
|
261
261
|
requirements:
|
|
262
262
|
- - "~>"
|
|
263
263
|
- !ruby/object:Gem::Version
|
|
264
|
-
version: 0.9
|
|
264
|
+
version: '0.9'
|
|
265
265
|
description: |
|
|
266
266
|
rgss_db is a tool designed for developers to export and import the database files of a game created in RPG Maker.
|
|
267
267
|
|
|
@@ -461,7 +461,7 @@ required_rubygems_version: !ruby/object:Gem::Requirement
|
|
|
461
461
|
- !ruby/object:Gem::Version
|
|
462
462
|
version: '0'
|
|
463
463
|
requirements: []
|
|
464
|
-
rubygems_version: 3.5.
|
|
464
|
+
rubygems_version: 3.5.18
|
|
465
465
|
signing_key:
|
|
466
466
|
specification_version: 4
|
|
467
467
|
summary: Manipulates the RPG Maker database to export and import RPG Maker data
|