The data files are exported as YAML files and the RGSS scripts are exported as normal Ruby files. I've been careful to make sure that the RGSS objects are always exported in the same way, so that unnecessary conflicts are avoided. Now, anytime two people change a map, a script, or any other game data, all of the conflicts can be easily resolved in plain text. I've also written scripts which can read these exported text files and import them back into.rxdata files so that RMXP can read them. This allows for implementing more advanced functionality, such as exporting scripts and data from.rxdata files (scripts, system data, maps, etc.) into plain-text files which are human-readable and can be easily versioned with a versioning system such as Git, Subversion or Mercurial. README.markdown #Rxdata Versioning Utility #Version: 1.0.5 #By: Raku () #Updated by: Gegerlan () # Introduction Have you ever wanted to work on an RPG Maker XP (RMXP) or RPG Maker VX (RMVX) game with a group of friends, but ran into trouble with conflicts when multiple people edit the same rxdata files? If you want to safely and efficiently version the data in your game, then read on! I have written a general plugin system for RPG Maker XP and VX so that scripts can be run externally (using the normal Ruby interpreter) at startup and/or shutdown of RMXP.
0 kommentar(er)
