rmxp_extractor 1.8 → 1.9

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: 44327757aeff89ba4da0a15892c0fc52a49575328e5123a6b349ffb68399400e
-  data.tar.gz: 135c978c6f2020abdd78b043fcfbde117dee2cd295a96c4ddde57051b48e4d7e
+  metadata.gz: f5522ce0108647d1ac9bd5f35e1c948a9ac38ef8865e6fee7866a4041d7a8fd7
+  data.tar.gz: ff306e42d3e6965625deae7ed887fdc40fe99a6091e8fe882a795951293bc6dd
 SHA512:
-  metadata.gz: d712b59caf6a44943f6fcab88bb3cca49b996e1b8cc152241d3d0fb914ece8b4bbd1c5b2d10d979278d3bbcf824dac1f9fc37a9b689645fef84af596698ae59e
-  data.tar.gz: a861c3d40a3c33ffde367a2fc6f8fcdd85c53af5f25ddce6e21a094526a20d48b61689eb501cdf7004da15186aa10a0a5eaa865dab0dae517d38f9cab1ae7dc0
+  metadata.gz: ddbeed6f31321882427c236a69d198b5c5d71879b5cce4b2831ad23f2e0b5695dd73a47ab17d0b727da06af020e1a787d45dd0dcbf634c7d8c480096602b618c
+  data.tar.gz: 1e0257b3ea03a1a857c0996cf1c2e7bb392f31cdbaad90aeedb89fa3fa96cd38e3de72c85b0904e2cec174514e047726b6402b46c049e0e90b03b1771df900cf

data/CODE_OF_CONDUCT.md

@@ -1,74 +1,74 @@
-# Contributor Covenant Code of Conduct
-
-## Our Pledge
-
-In the interest of fostering an open and welcoming environment, we as
-contributors and maintainers pledge to making participation in our project and
-our community a harassment-free experience for everyone, regardless of age, body
-size, disability, ethnicity, gender identity and expression, level of experience,
-nationality, personal appearance, race, religion, or sexual identity and
-orientation.
-
-## Our Standards
-
-Examples of behavior that contributes to creating a positive environment
-include:
-
-* Using welcoming and inclusive language
-* Being respectful of differing viewpoints and experiences
-* Gracefully accepting constructive criticism
-* Focusing on what is best for the community
-* Showing empathy towards other community members
-
-Examples of unacceptable behavior by participants include:
-
-* The use of sexualized language or imagery and unwelcome sexual attention or
-advances
-* Trolling, insulting/derogatory comments, and personal or political attacks
-* Public or private harassment
-* Publishing others' private information, such as a physical or electronic
-  address, without explicit permission
-* Other conduct which could reasonably be considered inappropriate in a
-  professional setting
-
-## Our Responsibilities
-
-Project maintainers are responsible for clarifying the standards of acceptable
-behavior and are expected to take appropriate and fair corrective action in
-response to any instances of unacceptable behavior.
-
-Project maintainers have the right and responsibility to remove, edit, or
-reject comments, commits, code, wiki edits, issues, and other contributions
-that are not aligned to this Code of Conduct, or to ban temporarily or
-permanently any contributor for other behaviors that they deem inappropriate,
-threatening, offensive, or harmful.
-
-## Scope
-
-This Code of Conduct applies both within project spaces and in public spaces
-when an individual is representing the project or its community. Examples of
-representing a project or community include using an official project e-mail
-address, posting via an official social media account, or acting as an appointed
-representative at an online or offline event. Representation of a project may be
-further defined and clarified by project maintainers.
-
-## Enforcement
-
-Instances of abusive, harassing, or otherwise unacceptable behavior may be
-reported by contacting the project team at matthew@nowaffles.com. All
-complaints will be reviewed and investigated and will result in a response that
-is deemed necessary and appropriate to the circumstances. The project team is
-obligated to maintain confidentiality with regard to the reporter of an incident.
-Further details of specific enforcement policies may be posted separately.
-
-Project maintainers who do not follow or enforce the Code of Conduct in good
-faith may face temporary or permanent repercussions as determined by other
-members of the project's leadership.
-
-## Attribution
-
-This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
-available at [https://contributor-covenant.org/version/1/4][version]
-
-[homepage]: https://contributor-covenant.org
-[version]: https://contributor-covenant.org/version/1/4/
+# Contributor Covenant Code of Conduct
+
+## Our Pledge
+
+In the interest of fostering an open and welcoming environment, we as
+contributors and maintainers pledge to making participation in our project and
+our community a harassment-free experience for everyone, regardless of age, body
+size, disability, ethnicity, gender identity and expression, level of experience,
+nationality, personal appearance, race, religion, or sexual identity and
+orientation.
+
+## Our Standards
+
+Examples of behavior that contributes to creating a positive environment
+include:
+
+* Using welcoming and inclusive language
+* Being respectful of differing viewpoints and experiences
+* Gracefully accepting constructive criticism
+* Focusing on what is best for the community
+* Showing empathy towards other community members
+
+Examples of unacceptable behavior by participants include:
+
+* The use of sexualized language or imagery and unwelcome sexual attention or
+advances
+* Trolling, insulting/derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or electronic
+  address, without explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Our Responsibilities
+
+Project maintainers are responsible for clarifying the standards of acceptable
+behavior and are expected to take appropriate and fair corrective action in
+response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or
+reject comments, commits, code, wiki edits, issues, and other contributions
+that are not aligned to this Code of Conduct, or to ban temporarily or
+permanently any contributor for other behaviors that they deem inappropriate,
+threatening, offensive, or harmful.
+
+## Scope
+
+This Code of Conduct applies both within project spaces and in public spaces
+when an individual is representing the project or its community. Examples of
+representing a project or community include using an official project e-mail
+address, posting via an official social media account, or acting as an appointed
+representative at an online or offline event. Representation of a project may be
+further defined and clarified by project maintainers.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported by contacting the project team at matthew@nowaffles.com. All
+complaints will be reviewed and investigated and will result in a response that
+is deemed necessary and appropriate to the circumstances. The project team is
+obligated to maintain confidentiality with regard to the reporter of an incident.
+Further details of specific enforcement policies may be posted separately.
+
+Project maintainers who do not follow or enforce the Code of Conduct in good
+faith may face temporary or permanent repercussions as determined by other
+members of the project's leadership.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
+available at [https://contributor-covenant.org/version/1/4][version]
+
+[homepage]: https://contributor-covenant.org
+[version]: https://contributor-covenant.org/version/1/4/

data/Gemfile

@@ -1,13 +1,13 @@
-source "https://rubygems.org"
-
-# Specify your gem's dependencies in rmxp_extractor.gemspec
-gemspec
-
-gem "oj"
-gem "ruby-progressbar"
-gem "fileutils"
-gem "pathname"
-gem "zlib"
-gem "json"
-gem "yaml"
-gem "amazing_print"
+source "https://rubygems.org"
+
+# Specify your gem's dependencies in rmxp_extractor.gemspec
+gemspec
+
+gem "oj"
+gem "ruby-progressbar"
+gem "fileutils"
+gem "pathname"
+gem "zlib"
+gem "json"
+gem "yaml"
+gem "amazing_print"

data/Gemfile.lock

@@ -1,7 +1,7 @@
 PATH
   remote: .
   specs:
-    rmxp_extractor (1.7)
+    rmxp_extractor (1.9)
       fileutils
       json
       oj

data/LICENSE.txt

@@ -1,21 +1,21 @@
-The MIT License (MIT)
-
-Copyright (c) 2021 Speak2Erase
-
-Permission is hereby granted, free of charge, to any person obtaining a copy
-of this software and associated documentation files (the "Software"), to deal
-in the Software without restriction, including without limitation the rights
-to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
-copies of the Software, and to permit persons to whom the Software is
-furnished to do so, subject to the following conditions:
-
-The above copyright notice and this permission notice shall be included in
-all copies or substantial portions of the Software.
-
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
-LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
-OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
-THE SOFTWARE.
+The MIT License (MIT)
+
+Copyright (c) 2021 Speak2Erase
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in
+all copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN
+THE SOFTWARE.

data/README.md

@@ -1,35 +1,35 @@
-# RMXP-Extractor
-
-A tool designed to dump rxdata to various git compatible formats. Some work better than others, though.
-YAML is slow in comparison to JSON. I'd suggest sticking to JSON generally.
-
-Originally, I used a complex monkey patched system to dump things to a hash that was very slow and imprecise. 
-Now, it uses some neat tricks to do it relatively efficiently. 
-
-Only problem is, classes dumped or loaded dump their instance variables, meaning that classes are **not** initialized with their default values at all. 
-
-This is important if you are handwriting the config files for whatever reason.
-
-Pretty print is also a format, but it uses eval for loading. There's likely a better way of doing this out there, but eh, I'm not bothered.
-It's fairly readable though.
-
-There is a minor problem right now with string encoding, especially with oneshot since there's some foul text that's encoded weirdly. 
-I'll try to fix that later.
-
-Usage:
-
-`rmxp_extractor import | export <type> | scripts"`
-# Script
-
-Allows you to export Scripts/xScripts to a specified folder. You can also import said specified folder back into Scripts/xScripts.
-The last argument `[x]` is optional. Placing just `x` there will extract Scripts.
-
-# Is it flawless?
-
-Running export followed by import should produce an almost identical file with some minor differences.
-
-As far as I'm aware from my testing, a file diff may say the the two are different, but loading them via marshal provides the exact same instance give or take.
-Ruby reports the original and imported instances as being different when loaded from Marshal, but pretty printing each instance to a file shows this is not the case.
-RPG Maker XP probably doesn't exactly follow Marshal spec and cuts some corners, which is why the file diff shows up differently.
-
-A diff check tool is provided if you want to try it yourself.
+# RMXP-Extractor
+
+A tool designed to dump rxdata to various git compatible formats. Some work better than others, though.
+YAML is slow in comparison to JSON. I'd suggest sticking to JSON generally.
+
+Originally, I used a complex monkey patched system to dump things to a hash that was very slow and imprecise. 
+Now, it uses some neat tricks to do it relatively efficiently. 
+
+Only problem is, classes dumped or loaded dump their instance variables, meaning that classes are **not** initialized with their default values at all. 
+
+This is important if you are handwriting the config files for whatever reason.
+
+Pretty print is also a format, but it uses eval for loading. There's likely a better way of doing this out there, but eh, I'm not bothered.
+It's fairly readable though.
+
+There is a minor problem right now with string encoding, especially with oneshot since there's some foul text that's encoded weirdly. 
+I'll try to fix that later.
+
+Usage:
+
+`rmxp_extractor import | export <type> | scripts"`
+# Script
+
+Allows you to export Scripts/xScripts to a specified folder. You can also import said specified folder back into Scripts/xScripts.
+The last argument `[x]` is optional. Placing just `x` there will extract Scripts.
+
+# Is it flawless?
+
+Running export followed by import should produce an almost identical file with some minor differences.
+
+As far as I'm aware from my testing, a file diff may say the the two are different, but loading them via marshal provides the exact same instance give or take.
+Ruby reports the original and imported instances as being different when loaded from Marshal, but pretty printing each instance to a file shows this is not the case.
+RPG Maker XP probably doesn't exactly follow Marshal spec and cuts some corners, which is why the file diff shows up differently.
+
+A diff check tool is provided if you want to try it yourself.

data/Rakefile

@@ -1,6 +1,6 @@
-require "bundler/gem_tasks"
-require "rspec/core/rake_task"
-
-RSpec::Core::RakeTask.new(:spec)
-
-task :default => :spec
+require "bundler/gem_tasks"
+require "rspec/core/rake_task"
+
+RSpec::Core::RakeTask.new(:spec)
+
+task :default => :spec

data/bin/rmxp_extractor

@@ -1,13 +1,13 @@
-#!/usr/bin/env ruby
-
-require "bundler/setup"
-require "rmxp_extractor"
-
-# You can add fixtures and/or initialization code here to make experimenting
-# with your gem easier. You can also use a different console, if you like.
-
-# (If you use this, don't forget to add pry to your Gemfile!)
-# require "pry"
-# Pry.start
-
-RMXPExtractor.process ARGV
+#!/usr/bin/env ruby
+
+require "bundler/setup"
+require "rmxp_extractor"
+
+# You can add fixtures and/or initialization code here to make experimenting
+# with your gem easier. You can also use a different console, if you like.
+
+# (If you use this, don't forget to add pry to your Gemfile!)
+# require "pry"
+# Pry.start
+
+RMXPExtractor.process ARGV

data/bin/setup

@@ -1,8 +1,8 @@
-#!/usr/bin/env bash
-set -euo pipefail
-IFS=$'\n\t'
-set -vx
-
-bundle install
-
-# Do any other automated setup that you need to do here
+#!/usr/bin/env bash
+set -euo pipefail
+IFS=$'\n\t'
+set -vx
+
+bundle install
+
+# Do any other automated setup that you need to do here

data/diff_check.rb

@@ -1,13 +1,13 @@
-require_relative "lib/rmxp_extractor/classnames"
-require "amazing_print"
-
-f = File.open("Data_OLD/Map266.rxdata")
-ins1 = Marshal.load(f)
-
-f2 = File.open("Data/Map266.rxdata")
-ins2 = Marshal.load(f2)
-
-f = File.open("ins1", "w")
-f2 = File.open("ins2", "w")
-f.puts ins1.ai(plain: true, raw: true, object_id: false)
-f2.puts ins2.ai(plain: true, raw: true, object_id: false)
+require_relative "lib/rmxp_extractor/classnames"
+require "amazing_print"
+
+f = File.open("Data_OLD/Map266.rxdata")
+ins1 = Marshal.load(f)
+
+f2 = File.open("Data/Map266.rxdata")
+ins2 = Marshal.load(f2)
+
+f = File.open("ins1", "w")
+f2 = File.open("ins2", "w")
+f.puts ins1.ai(plain: true, raw: true, object_id: false)
+f2.puts ins2.ai(plain: true, raw: true, object_id: false)