Version 1.0 of Inside Job, a free/open source Minecraft Alpha inventory editor for Mac, is now available. Features include:
- Native Cocoa interface
- Drag & drop inventory editing with item images
- Item list searchable by name or item number
- Experimental "time of day" editing
- Requires Mac OS X 10.6
You can check out a screenshot and download the app or its source code on GitHub: http://preble.github.com/InsideJob/ Click the "Downloads" button toward the upper right for the binary app download link. The readme contains basic instructions.
Although I believe that Inside Job does a good job of not destroying your saved world data, please backup your saved worlds before running it as it has not been tested on more than a few systems. (Inside Job does make a copy of your level.dat file before overwriting it each time you save.)
Beautiful! Hopefully, I can now explode that annoying skeleton nest with loads of TNT!
Greatly helpful for noobs like me who hate working and love hacking. :smile.gif:
Hi all. Glad to hear some of you like what you see, sorry to see that some of you are having trouble.
If you're having trouble running Inside Job (nothing appears to happen when you run it), please check:
- Are you running Mac OS X 10.6+? At this time Inside Job requires 10.6 and up.
- If you are running Mac OS X 10.6+, please check your ~/Library/Logs/CrashReporter folder for a file named "Inside Job <date>.crash". If you have a file like this, please PM it to me here and I'll look into it.
Feel free to PM me details on problems you encounter with Inside Job, or create an issue on GitHub. Thanks.
Bah you beat me, was finishing up the finish touches for my mac editor :tongue.gif:
I hope you still plan on releasing it. I'd be interested to see it.
Quote from Xiili »
[EDIT]
Naturally you're welcome to download and modify the source. I should point out that you can effectively trash an item if you drag it out of its slot and then release it where there isn't a slot. I'd like to have a better mechanism in Inside Job for selecting individual items and performing actions on them (maxing them to 64, removing them as you point out, etc.) but I decided to keep it simple for 1.0.
Re: wrong section, as a couple people have pointed out: I've PM'd a moderator and requested that they move the topic.
I seem to not be able to work out how to use this? I whack stuff in my inventory and save, but then when I re-open minecraft it just deletes all my saves? It worked the first time, now just whenever I generate a new world, save it, exit minecraft, put some stuff in inventory, save InsideJob, then re-open minecraft, the worlds are all gone?
What version of os are you running?
Side note, it just did it for me, after looking into it, it seems that the app is either removing or relocating the level file, my actual data is still there but the level file, I'll do some crunching and see what could cause this.
I seem to not be able to work out how to use this? I whack stuff in my inventory and save, but then when I re-open minecraft it just deletes all my saves? It worked the first time, now just whenever I generate a new world, save it, exit minecraft, put some stuff in inventory, save InsideJob, then re-open minecraft, the worlds are all gone?
Is the level.dat for the modified world missing, as Xiili reported (hopefully I understood that correctly)?
You should see a level.dat.insidejobbackup file in that same folder, which is the original level.dat, so theoretically you could reverse Inside Job's changes. Is the backup file there, and if you rename it to level.dat does it fix the problem?
Lastly, can you open Console (in Applications/Utilities) and see if you see any messages from Inside Job in the "All Messages" section?
I seem to not be able to work out how to use this? I whack stuff in my inventory and save, but then when I re-open minecraft it just deletes all my saves? It worked the first time, now just whenever I generate a new world, save it, exit minecraft, put some stuff in inventory, save InsideJob, then re-open minecraft, the worlds are all gone?
Is the level.dat for the modified world missing, as Xiili reported (hopefully I understood that correctly)?
You should see a level.dat.insidejobbackup file in that same folder, which is the original level.dat, so theoretically you could reverse Inside Job's changes. Is the backup file there, and if you rename it to level.dat does it fix the problem?
Lastly, can you open Console (in Applications/Utilities) and see if you see any messages from Inside Job in the "All Messages" section?
Thanks; my apologies for the inconvenience!
Here is what the folder looks like after using InsideJob:
Deleting level.dat and renaming level.dat.insidejobbackup to level.dat fixes the issue. With regards to the console, the only 'odd' looking log is this one:
14/10/2010 07:48:17 Inside Job[1405] Unhandled list type: 1
Well, I'll be honest, at first, I downloaded the source code and files without realizing it...I was completely lost. Then I downloaded the right one. Download the 'InsideJob100.zip' then extract it and run. Simple as that.
I've posted a new version to the Inside Job page on GitHub, 1.0.1 beta 1. Here's a summary of the changes:
[*:3qjfpqrj] Fixed an issue that could result in the modified world not being properly saved. If you have had an issue with saving in the past this should fix it. The problem is related to an oddity in the way Minecraft saves empty inventories. Thanks for your patience with this issue.
[*:3qjfpqrj] Improved error handling and messaging when an error occurs while saving the world.
[*:3qjfpqrj] Improved handling after selecting a world that does not exist.
[*:3qjfpqrj] Inside Job will now prompt to save a changed world before closing the application or switching to a different world.
Thanks to those of you who wrote with suggestions, or filed issues on GitHub.
And as a reminder: if you encounter any crashes, please check for a Inside Job .crash file in ~/Library/Logs/CrashReporter. Sending that file to me in a PM along with a description of what you were doing when the application crashed will make it much easier for me to solve the problem. Thanks.
- Native Cocoa interface
- Drag & drop inventory editing with item images
- Item list searchable by name or item number
- Experimental "time of day" editing
- Requires Mac OS X 10.6
You can check out a screenshot and download the app or its source code on GitHub: http://preble.github.com/InsideJob/ Click the "Downloads" button toward the upper right for the binary app download link. The readme contains basic instructions.
Although I believe that Inside Job does a good job of not destroying your saved world data, please backup your saved worlds before running it as it has not been tested on more than a few systems. (Inside Job does make a copy of your level.dat file before overwriting it each time you save.)
Hope you find it useful!
Adam
EDIT: Updated URLs.
I would really like a good editor for my desktop.
Greatly helpful for noobs like me who hate working and love hacking. :smile.gif:
If you're having trouble running Inside Job (nothing appears to happen when you run it), please check:
- Are you running Mac OS X 10.6+? At this time Inside Job requires 10.6 and up.
- If you are running Mac OS X 10.6+, please check your ~/Library/Logs/CrashReporter folder for a file named "Inside Job <date>.crash". If you have a file like this, please PM it to me here and I'll look into it.
Feel free to PM me details on problems you encounter with Inside Job, or create an issue on GitHub. Thanks.
But very well done, I like it, runs very smooth!
[EDIT]
I hope you still plan on releasing it. I'd be interested to see it.
Naturally you're welcome to download and modify the source. I should point out that you can effectively trash an item if you drag it out of its slot and then release it where there isn't a slot. I'd like to have a better mechanism in Inside Job for selecting individual items and performing actions on them (maxing them to 64, removing them as you point out, etc.) but I decided to keep it simple for 1.0.
Re: wrong section, as a couple people have pointed out: I've PM'd a moderator and requested that they move the topic.
Didn't try that, a lot easier :biggrin.gif: thx!
What version of os are you running?
Side note, it just did it for me, after looking into it, it seems that the app is either removing or relocating the level file, my actual data is still there but the level file, I'll do some crunching and see what could cause this.
Is the level.dat for the modified world missing, as Xiili reported (hopefully I understood that correctly)?
You should see a level.dat.insidejobbackup file in that same folder, which is the original level.dat, so theoretically you could reverse Inside Job's changes. Is the backup file there, and if you rename it to level.dat does it fix the problem?
Lastly, can you open Console (in Applications/Utilities) and see if you see any messages from Inside Job in the "All Messages" section?
Thanks; my apologies for the inconvenience!
Here is what the folder looks like after using InsideJob:
Deleting level.dat and renaming level.dat.insidejobbackup to level.dat fixes the issue. With regards to the console, the only 'odd' looking log is this one:
14/10/2010 07:48:17 Inside Job[1405] Unhandled list type: 1
Hope this helps
EDIT:: Ninja'd x.x
[*:3qjfpqrj] Fixed an issue that could result in the modified world not being properly saved. If you have had an issue with saving in the past this should fix it. The problem is related to an oddity in the way Minecraft saves empty inventories. Thanks for your patience with this issue.
[*:3qjfpqrj] Improved error handling and messaging when an error occurs while saving the world.
[*:3qjfpqrj] Improved handling after selecting a world that does not exist.
[*:3qjfpqrj] Inside Job will now prompt to save a changed world before closing the application or switching to a different world.
Thanks to those of you who wrote with suggestions, or filed issues on GitHub.
And as a reminder: if you encounter any crashes, please check for a Inside Job .crash file in ~/Library/Logs/CrashReporter. Sending that file to me in a PM along with a description of what you were doing when the application crashed will make it much easier for me to solve the problem. Thanks.