Skip to content

I got fed up with all the other implementations of NBT in go, so I made my own.

Notifications You must be signed in to change notification settings

Nightgunner5/go.nbt

Repository files navigation

All the other Go NBT libraries I tried fell short of my expectations. Either they had their own type system which I had to convert into maps or parse a second time into my structs or they had cryptic error messages or custom "error handling" that omitted important details like where exactly the problem occurred.

I built go.nbt to solve two problems: NBT parsing (NBT is Mojang's "Named Binary Tag" format used heavily in Minecraft) and meaningful error handling.

But that's enough of the trivial details. You're here to use the library, not hear a story about how it was made.

Setup

To set up go.nbt, simply run:

go get github.com/Nightgunner5/go.nbt

Or use go get with no parameters in the package you use it in and it will be automagically downloaded and compiled.

But you already knew that.

Example 1

package example

import (
	"github.com/Nightgunner5/go.nbt"
	"io"
)

// Just define your struct the way you normally would. Most data types can be used with no modifications.
type Example1 struct {
	Name string `nbt:"name"` // If you need a lowercase first letter for an NBT field name or
	                         // your field name is invalid as an identifier in Go, you can
	                         // use tags similar to encoding/json and encoding/xml.

	Data [256]byte // go.nbt supports both arrays and slices for TAG_Byte_Array and TAG_Int_Array.

	Children []Example1 // Any type that can be used as a TAG_Compound can also be used as an element
	                    // in a TAG_List.
}

func ReadExample1(in io.Reader) (Example1, error) {
	var out Example1

	err := nbt.Unmarshal(nbt.Uncompressed, in, &out)

	return out, err
}

Example 2

What if we tried to read with a missing or incorrect field? Instead of silently ignoring the problem or saying "oops, there was an error" and not giving any information, there's a stack trace and a readable error message. For example, what if the elements of Example1.Children have an additional field "Index"?

Here's the error that would be returned:

nbt: Unhandled TAG_Int (0x03)
		at struct field "Index"
		at list index 0
		at struct field "Children"

About

I got fed up with all the other implementations of NBT in go, so I made my own.

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages