.gitignore

@@ -1,2 +1,2 @@
 /target
-inventory-fix.png
+out.png

Cargo.toml

@@ -5,7 +5,7 @@ license = "MIT"
 authors = ["endernon"]
 repository = "https://git.frfrnocap.men/endernon/rpfixer"
 readme = "readme.md"
-version = "0.4.2"
+version = "0.4.1"
 edition = "2021"
 
 [dependencies]

readme.md

@@ -1,6 +1,6 @@
-# rpfixer (formerly respack-decrypter)
+# rpfixer
 
-This tool allows you to fix corrupted images' metadata in a resource pack, where the images have been corrupted to be protected.
+This tool allows you to unfuck corrupted images metadata in a resource pack that have been corrupted to be protected.
 
 This tool will not overcome any protection to the zip archive itself. See a program such as [MCRPX](https://github.com/Speedy11CZ/mcrpx) for that.
 
@@ -15,8 +15,8 @@ This tool will not overcome any protection to the zip archive itself. See a prog
 - run `cargo build --release` in the directory
 - check `./target/release`
 - run 
-  - `rpfixer` if you are on linux/mac (RUN `chmod +x rpfixer` ON IT FIRST) 
+  - `respack-decrypter` if you are on linux/mac (RUN `chmod +x respack-decrypter` ON IT FIRST) 
-  - `rpfixer` if you are on windows
+  - `respack-decrypter.exe` if you are on windows
 #### Cargo
 - Download the Rust-Lang for your system
 - run `cargo install rpfixer`
@@ -28,8 +28,8 @@ This tool will not overcome any protection to the zip archive itself. See a prog
 ```rust
 use std::fs;
 fn main() {
-    let frfr: Vec<u8> = fs::read("filepath.png").expect("wtf the path doesnt exist");
+    let frfr = fs::read("filepath.png").expect("wtf the path doesnt exist");
-    let mut fr: Vec<u8> = rpfixer::idk::fix(frfr);
+    let mut fr = rpfixer::idk::fix(frfr);
     fs::write("filepath.png", fr).expect("file could not write btw");
 }
 ```
@@ -44,6 +44,6 @@ Example syntax:
 
 # License
 
-It's all MIT, except the example corrupted inventory.png and inventory-fix.png which is courtesy of Wynncraft. 
+It's all MIT, except the example corrupted inventory.png which is courtesy of Wynncraft. 
 
-Zeer you better not come after me for this one, you guys still haven't answered my gdpr req yet
+Zeer you better not come after me for this one, you still haven't answered my gdpr req yet