NBTExplorer is a low-level graphical NBT data editor originally based on NBTedit. The key difference is NBTExplorer's full support for Minecraft .mcr/.mca region files, a directory-tree interface for easily exploring multiple worlds, and support for the latest NBT standard. NBTExplorer is built on top of Substrate.
NBTExplorer can read:
- Standard NBT files (e.g. level.dat)
- Schematic files
- Uncompressed NBT files (e.g. idcounts.dat)
- Minecraft region files (*.mcr)
- Minecraft anvil files (*.mca)
- Cubic Chunks region files
The NBTExplorer zip and installer packages for Windows now include a second utility, NBTUtil.exe, for command-line control of NBT data. NBTUtil currently has a limited featureset compared to NBTExplorer.
Windows Users
NBTExplorer is a Windows .NET application, and requires .NET framework 2.0 or higher to run. Note: If you run Windows 8 or later, you may get a SmartScreen warning when first running the program. See the related FAQ entry for more information.
Linux Users
NBTExplorer has been tested for compatibility with recent Mono runtimes. Minimally, your system needs the mono-core and mono-winforms packages, or whatever set of packages is equivalent.
Mac Users
A Mac-specific version of NBTExplorer is available with a native UX. It is compatible with Mac OS X 10.7 or higher. It will not run on 10.6, sorry.
As of August 22, 2013, I've begun signing NBTExplorer with an Apple Developer ID certificate. If you have GateKeeper configured to only allow software from the App Store, then you will need to change GateKeeper to allow running signed downloaded applications, or following these instructions to bypass GateKeeper:
- Download NBTExplorer
- Copy the NBTExplorer.app out of the zip, to your /Applications folder
- Open your Terminal, found in /Applications/Utilities
- At the prompt the Terminal gives you, type exactly the following: ", courier, monospace">xattr -rd com.apple.quarantine /Applications/NBTExplorer.app
If you have problems with the native client or you're running OS X 10.6 or older, you can still run the Windows version of NBTExplorer on your Mac by following the Linux instructions and installing the Mono runtime. You may still need to disable GateKeeper quarantine on the downloaded files.
Download: Windows / Linux (Version 2.8.0) [MSI installer or ZIP archive]
Download: Mac (Version 2.0.3)
Project Page: Github
I recommend backing up worlds before modifying them with this tool.
Frequently Asked Questions
Q: NBTExplorer didn't save my changes -- why?
A: It's possible you forgot to save. The more likely answer is NBTExplorer did save your changes, and if you were to immediately re-open your world in NBTExplorer, you would see that your changes are still there. Instead, Minecraft erased or ignored your changes when you loaded your world. The most common trap is editing player settings or inventory on a single-player world and making your changes in a .dat file instead of in level.dat. Minecraft will overwrite your .dat file on load with the contents of the player tag in level.dat.
Q: I'm on Windows and NBTExplorer crashed on start / didn't run.
A: Did you get a message box listing one or more exceptions? Reply to this thread with the information so you can be better helped.
If you didn't get any message box though, or you only received a standard "program has stopped working" message box, then you have deeper issues with your .NET environment. Do any other .NET programs run on your computer? If yes, then try deleting the NBTExplorer.exe.config file that was installed / came with the zip. This will cause NBTExplorer to prefer the .NET 2.x/3.x framework over the 4.x framework, and may allow the program to run if your .NET 4.x framework is toast. You should still do something about that, of course.
Q: I'm on Windows and NBTExplorer crashed with a scary warning.
A: Windows 8 and later includes a program filter called "SmartScreen" that prevents unrecognized software from running. Its warning looks something like this:
If you see this screen, press the "More info" link to get a "Run Anyway" button. This will launch the program, and you shouldn't see the warning again unless you update NBTExplorer.
NBTExplorer is SAFE and has an established reputation in the Minecraft community. However, you don't need to take my word at face-value. The source code is publicly available for inspection, and you can download and build your own copy if you so wish.
SmartScreen builds up reputation on individual files. So you may see this warning if you download a freshly released update of NBTExplorer, but not if you download a version that has been out for a while. Unfortunately the permanent fix for this is to buy very expensive signing certificates that must be renewed annually, which is not viable for a free tool like this.
Q: The Mac version doesn't run on my Mac!
A: If you're running OSX 10.6.x or earlier, the Mac version is confirmed to not work. It has been tested and confirmed to work for people on 10.7.x and 10.8.x, although that may still not be a guarantee that it will work for you, or that it will be bug-free.
If you're having problems running the Mac-specific version of NBTExplorer, there is still a high probability that you can run the Windows/Linux version instead. thhinds has posted a more detailed set of instructions here. It won't be as pretty -- you'll get a very crude looking version of Windows UI styling instead of native OSX styling, but it should still do the job. I can't do anything about this unless an experienced Cocoa developer that also has some .NET/Mono experience is willing to step up and help me determine why it won't run on older versions of OSX.
Q: When I run the Mac version, I see: OSStatus error -67053
A: It has been reported that this is caused by Gatekeeper disallowing NBTExplorer from running because it is not a properly signed application. Please refer to the instructions in the "Mac Users" section above for bypassing GateKeeper's check. NOTE: As of August 22, 2013, I have begun signing NBTExplorer. Try downloading the latest version first.
192
Error Reporting (where and how to report crashes)
- I will not read repetitive crashes
- look here for your problem, if it is not there, add a new issue
Instructions for making a new issueContent
Key-Bindings
- backslash '\'; -- changes the way the OneWay camo blocks are placed. this can be changed under the controls menu.
Commands- /srm-show -- toggles the visibility of the secret blocks. They only update in a certain radius though. so going around breaking blocks is a sure way to update the Camo blocks around them. It may be a good idea to toggle this command multiple times.
Blocks and Items1) Torch lever
BlockID = 2020
BROKEN IMAGE
Works like a normal lever, but looks exactly like a torch. It even sheds light.
2) OneWay Camo
BlockID = 2021
BROKEN IMAGE
One side camo, all the rest glass. Looks like glass in the inventory. When placed, camo side is either towards or away from you. This can be toggled with the BackSlash key, \.
3) Secret Gate
BlockID = 2022
BROKEN IMAGE
Camoflages to the blocks arround it, and when its powered, it extends up to 10 blocks. Try for your self in an open area.Its orrientation is the same as the OneWayCamo blocks.
4) CamoDummy (shelfgate extension)
BlockID = 2023
-- NO RECIPE --
Camoflauges to the blocks arround them.
5) Camo TrapDoor
BlockID = 2024
BROKEN IMAGE
A TrapDoor that camouflages itself to the surrounding blocks. it is open-able with clicking or right-clicking, Be careful not to forget where you put it. It can be placed flush with the floor, and flush with a cieling depending on where you right-click to place it.
6) ShelfGate Extension
BlockIDs = 2025 & 2026
ItemIDs = 4106 & 4107
BROKEN IMAGE -- BROKEN IMAGE
Doors that camouflage. AS usual, the iron doors are only openabble by a redstone signal while the wooden doors can be opened with a click.
7) Camo Paste
ItemIDs = 4108
BROKEN IMAGE
You can see them, but walk right through them.
9) Secret Lever
BlockID = 2028
BROKEN IMAGE
Camoflages like all the other "camo" blocks, but his one works like a lever.
10) Secret Redstone
BlockID = 2029
BROKEN IMAGE
Another Camo Block. but this one carries a redstone current just like normal redstone. The redstone works exactly liek vanilla redstone, and is nearly 100% interchangeable with it. Like vanilla redstone, it decays within 15 blocks, and needs to be refreshed with a redstone torch or repeater.
11) Secret Button
BlockID = 2030 (metadata is 0 for stone, and 1 for wood)
BROKEN IMAGE -- BROKEN IMAGE
Another Camo block, but works like a button.
12 -15) Secret Pressure-Plates
BlockIDs = 2031 -- 2034
BROKEN IMAGE -- BROKEN IMAGE
BROKEN IMAGE -- BROKEN IMAGE
These are very special camo blocks. when something passes over them, they emit a redstone signal. The wooden one on the left powers when anything goes over it. The Stone version on the right only provides power when a player passes over it. The Gold and Iron versions are weighted pressure plates and behave like their vanilla counterparts
16) Secret Stairs
BlockID = 2035
BROKEN IMAGE
Works like stairs. You place them like you would any other, and ofcourse, they are camouflaged.
** works best with the Ghost BlocksThe recipe for this block now works with all the different types of wooden stairs that exist.
17 & 18) Secret Chests (and trapped chest)
BlockID = 2036 2037
BROKEN IMAGE
Works like a chest, just camouflages like everything else, and doesn't open up like other chests. Camo trapped chests can be crafted the exact same way, simply with the trapped chest in the center rather than a normal chest
19) Secret Light Detector (and trapped chest)
BlockID = 2038
BROKEN IMAGE
Works like a vanilla light detector, simply camouflaged.
20) Solid Air
BlockID = 2038
BROKEN IMAGE
Solid air is entirely invisible, yet solid. The other Secret blocks can camouflage to its entirely transparent texture in order to make completely invisible passages and structures.
Copyright and modpack permissions
The full body of the licence can be found here: https://github.com/AbrarSyed/SecretRoomsMod-forge/blob/master/LICENSE.txt
TLDR;
Changelog
Modloader = changes in only the ModLoader version.
both = changes in both versions. (also forge.. since only forge versions now.)
Todo list
striked red- Fixed/Addedgreen - working on for next update
blue - coming, kinda down the line though
Credits
Idea and more ideas from iampeppino
1.6.4 updated by CaptainShadows
Stay up to date!
Follow me on twitter for updates @AbrarSyed101!
Use #SecretRoomsMod in tweets!
Support Banners
thanks KeKoSlayer29
thanks Btrpo
1
This includes issues with the SecretRedstone and placing camo blocks as well as quirks in the ownership system.
1
as for the Malsis Doors compatability issues. They have now been fixed, grab build #380 from the download page.
2
I am a member of the MinecraftForge team. Between helping with the Forge update, helping with sponge, and IRL school and stuff, I haven't had time to work on this mod, either to add features or fix bugs. The mod is OpenSource, so if anyone feels they can help in any way, feel free to make a pull request.
As far as a 1.7.10 recommended edition. I really wanted to get through my anti-camo stuff features before releasing the recommended. Thats unlikely to happen with my current schedule. That being said.. the current beta for 1.7.10 is working mostly fine except for the odd error. So you can use that.
As far as 1.8 goes... This mod depends on the MinecraftForge, and cannot update until a a version of Forge is available for 1.8. As a member of the MinecraftForge team, I can say that the rumors of a MinecraftForge beta release are not true. Forge is still being worked on for 1.8, an will not be ready for at least a week yet.
As for pictures and screenshots.. This mod is camouflage. A picture wont tell you much. Thats why there is an embedded video.
1
1
1
if its a good review, I will
I dont mean that if it makes my mod look good, I mean if its well done.
1
This is not required, nor strictly even recommended. It is also a general stumbling block for new users. The Forge S package comes with the gradle wrapper. This allows you to use the gradlew (in linux/mac) and gradlew.bat (in windows) commands instead of using the gradle command that you would use if you had installed gradle. If you install gradle, use the gradle command and completely ignore the gradle wrapper stuff. If you choose to use the gradle wrapper, then there is no point in going through the hassle of installing gradle. That being said.. this isn't really an issue with the tutorial, just something worth mentioning.
That section about --refresh-dependencies is simply not true. The reason for --refresh-dependencies is just so that you can ensure that you have the very latest version of ForgeGradle. If you are running this for the first time on your computer, then this is unnecessary because you will get the latest. This only matters if you have run gradle commands in the forge workspace before,
The information about running the 'eclipse' and 'idea' tasks is mostly correct. To begin with, this issue no longer exists, ive fixed it. ALso, your explanation of the issue is not that the gradlew command is used instead of the gradle command. It was because you cannot run 'setupDecompWorkspace' and 'eclipse'/'idea' in the same command as you have in your code snippet. Doing that is what caused the error. To fix it, one must simply run the following 2 commands.
Again.. this has already been fixed.. so its not really an issue anymore.
From here on you are making life harder for yourself and your readers. From here on, I mean this quoted section, and your entire second tutorial. Gradle was not meant to be used this way. There was never meant to be a forge project, and other projects that link against it only in eclipse. No. The ForgeSrc package is nothing but a 100% example project. Thats what every project should look like (minus all the license crap). Like so: https://github.com/A...tRoomsMod-forge . You understand what im saying?
Each mod you have should be its very own project. There should not be a central forge project with multiple other eclipse projects linking to it in eclipse. Instead each project should be setup separate with the setupDecompWorkspace command run separately for each one. You may think this is stupid and duplicates forge everywhere. Dont worry, its not. Gradle caches the things that will be used between projects.. so subsequent setups will run 100x faster than the first time.
If you have any questions or stuff... reply here, il get it. or catch me on IRC in #ForgGradle on esper.net or even PM me on the forums.
1
1
Ive already found and fixed that issue, go ahead and grab the latest version again.. Last thing I need to do now is fix the localizations....