Closed TerrenceXW closed 2 years ago
Same Problem The Editor needs an Update for the Version 1.13
Yep, waiting for update. Seems like the encryption has changed.
Same issue, just gotta wait I guess
Why do the Dungeons Devs even change the encryption for the game's pak files anyway? It doesn't make any sense as far as I know.
Oof I fixed it locally but the repo ignores the Secrets.cs file so i can't push the fix for you guys.
Oof I fixed it locally but the repo ignores the Secrets.cs file so i can't push the fix for you guys.
You can make the file manually using GitHub's web editor and pasting the contents, else upload the file here as an attachment to your comment, with instructions.
Oof I fixed it locally but the repo ignores the Secrets.cs file so i can't push the fix for you guys.
You can make the file manually using GitHub's web editor and pasting the contents, else upload the file here as an attachment to your comment, with instructions.
@Auirsblade Please do this, I don't know how to even edit a ".cs" file let alone find it and I can't be bothered to fix this myself if someone else has already done it and could just upload it.
There's the file, you'll just need to follow the "Compiling" directions in the ReadMe and use that as your secrets file.
There's the file, you'll just need to follow the "Compiling" directions in the ReadMe and use that as your secrets file.
Unfortunately, instructions for compiling MCDSaveEdit yourself aren't clear and I'm getting a lot of errors. I crash coursed my way through but ultimately was unable to r.ecompile.
git clone
I assume I then place your Secrets.cs file into .\MCDSaveEdit\Data\ folder as noted in the Readme.
Then when loading MCDSaveEdit's .sln file and trying to compile, I get a tonne of missing file errors, and missing "referenced components"
Ideally there'd be something in MCDEdit for us to manually load a Secrets.cs file or otherwise provide an AESKey in-app to decrypt the PAK files, to save having to recompile everytime Mojang changes the key.
@TreeBranches yea I'm guessing you are missing a using or a reference causing that first error in the AesEncryptionProvider. Can't really guide you step by step but if you solve that the rest of the not found errors will go away.
it happens to me too.........
You could try downloading the code from my fork. It compiled fine as of a few days ago.
You could try downloading the code from my fork. It compiled fine as of a few days ago.
why not upload the compiled stuff then?
if yall want a working version dm me Kylee#8666 i give you the file fully compiled
I added you on discord, I'm the one named Del.
Sorry for the delay everyone. It seems someone decided to publish on my behalf.
How can i fix it? 1.13 does not work