Nbtexplorer spawn protection mac os x#
Nbtexplorer spawn protection full#
Nbtexplorer spawn protection software#
Nbtexplorer spawn protection windows 8#

dat file on load with the contents of the player tag in level.dat. The most common trap is editing player settings or inventory on a single-player world and making your changes in a. Instead, Minecraft erased or ignored your changes when you loaded your world. 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. Q: NBTExplorer didn't save my changes - why?Ī: It's possible you forgot to save. I recommend backing up worlds before modifying them with this tool. You may still need to disable GateKeeper quarantine on the downloaded files.ĭownload: Windows / Linux (Version 2.8.0) 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. This will clear the quarantine attributes that prevent NBTExplorer from running. ', courier, monospace'>xattr -rd /Applications/NBTExplorer.app At the prompt the Terminal gives you, type exactly the following:.Open your Terminal, found in /Applications/Utilities.Copy the NBTExplorer.app out of the zip, to your /Applications folder.Here are some instructions to bypass GateKeeper for NBTExplorer:

Nbtexplorer spawn protection software#

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:įor older unsigned versions of NBTExplorer, you may also receive a cryptic 'OSStatus error -67053' if you try to bypass GateKeeper the normal way by right-clicking the app and selecting 'Open'. It will not run on 10.6, sorry.Īs of August 22, 2013, I've begun signing NBTExplorer with an Apple Developer ID certificate.

Nbtexplorer spawn protection mac os x#

It is compatible with Mac OS X 10.7 or higher.

Minimally, your system needs the mono-core and mono-winforms packages, or whatever set of packages is equivalent.Ī Mac-specific version of NBTExplorer is available with a native UX. NBTExplorer has been tested for compatibility with recent Mono runtimes. See the related FAQ entry for more information.

Nbtexplorer spawn protection windows 8#

Note: If you run Windows 8 or later, you may get a SmartScreen warning when first running the program. NBTUtil currently has a limited featureset compared to NBTExplorer. The NBTExplorer zip and installer packages for Windows now include a second utility, NBTUtil.exe, for command-line control of NBT data.

NBTExplorer is built on top of Substrate. mcr/.mca region files, a directory-tree interface for easily exploring multiple worlds, and support for the latest NBT standard.

Nbtexplorer spawn protection full#

The key difference is NBTExplorer's full support for Minecraft. The would-be explosion radius reaches outside the zone, add some extra 'buffer' to the borders of it.NBTExplorer is a low-level graphical NBT data editor originally based on NBTedit. If you're someone wondering why your zones seem to disregard the explosion protection: So, even though the explosion starts within the zone, one has to make sure that the maximum radius of it is also contained within the zone. if the explosion's to-be-radius would reach outside of the zone border then it seem that the permission was checked against the (higher-prio) outside world. It was about the distance of the explosion to the zone border. It wasn't about any permissions or any wrong setup. The debug log showed that FE checked for fe.protection.explosion within instead of the custom zone.Īfter a sudden idea and some experimentation I finally figured out what the problem seemed to be.

Fire up some TNT, which then exploded (not expected).

/p test fe.protection.explosion -> Result: false (which was expected).

Go inside a malfunctioning protection zone.

After enabling debugging I did the following: At first I thought I was going insane because the explosion protection seemed to work with some zones but not others.