Skip to content

Releases: HarmfulBreeze/paktools

paktools-v1.0.1

06 Jan 10:59
2b84efa
Compare
Choose a tag to compare

A stable release at last :)

Improvements:

  • Added safety checks to the extraction process. paktools should now warn you when you try to extract an invalid or "weird" package file.
  • Some degree of cleanup

Bugfixes:

  • Fixed a bug with an odd error message
  • Native images should not have a double extension anymore

paktools-v0.2

05 Jan 16:43
7d67115
Compare
Choose a tag to compare
paktools-v0.2 Pre-release
Pre-release

Second prerelease. Still no safety checks so be a little careful with what you extract and make sure they are actual package files.

Breaking:

  • Command line usage has changed. You can now extract and rebuild package files really easily.
    Extracting to the myPackage folder: ./paktools myPackage.pak
    Extracting to the someFolderName folder: ./paktools -o someFolderName myPackage.pak
    Rebuilding using files in myFolder to create myFolder.pak: ./paktools myFolder
    Rebuilding using files in thisFolder to create myPackage.pak: ./paktools -o myPackage.pak thisFolder
    I think you get the gist.

Improvements:

  • Due to the changes to the CLI, you can now drag-and-drop files.
  • Now using picocli, check out the help by typing ./paktools --help
  • Added GraalVM, paktools is now a self-contained executable
  • Upgraded to Java 17, and we now use Gradle
  • Rewrote extraction and reconstruction logic to use ByteBuffers more efficiently (hello ByteChannels)

Bugfixes:

  • Dummy entries are now handled better

paktools-v0.1

19 Feb 15:46
be60fb9
Compare
Choose a tag to compare
paktools-v0.1 Pre-release
Pre-release

First release.
Extracting and rebuilding should both work just fine.

Be careful though: no safety checks were added yet!

Extracting: paktools.bat extract file.pak destinationFolder
Rebuilding: paktools.bat rebuild file.pak sourceFolder