Talk:NBT - Revision history

imported>C4K3: /* String payload is 2 bytes little endian */

2016-06-19T13:52:56Z

String payload is 2 bytes little endian

← Older revision		Revision as of 13:52, 19 June 2016
Line 63:		Line 63:

	Thank you.		Thank you.
	~ It's a mistake by me, fixed, sorry for any trouble [[User:C4K3\|C4K3]] ([[User talk:C4K3\|talk]]) 13:52, 19 June 2016 (UTC)		:It's a mistake by me, fixed, sorry for any trouble [[User:C4K3\|C4K3]] ([[User talk:C4K3\|talk]]) 13:52, 19 June 2016 (UTC)

imported>C4K3 at 13:52, 19 June 2016

2016-06-19T13:52:31Z

← Older revision		Revision as of 13:52, 19 June 2016
Line 63:		Line 63:

	Thank you.		Thank you.
			~ It's a mistake by me, fixed, sorry for any trouble [[User:C4K3\|C4K3]] ([[User talk:C4K3\|talk]]) 13:52, 19 June 2016 (UTC)

imported>Tachyon: /* String payload is 2 bytes little endian */ new section

2016-06-18T17:53:35Z

String payload is 2 bytes little endian: new section

← Older revision		Revision as of 17:53, 18 June 2016
Line 55:		Line 55:
	http://wiki.vg/nbt/ is a dead link (in the abstract of the article)		http://wiki.vg/nbt/ is a dead link (in the abstract of the article)
	--[[User:Rom1504\|Rom1504]] ([[User talk:Rom1504\|talk]]) 07:56, 16 April 2015 (UTC)		--[[User:Rom1504\|Rom1504]] ([[User talk:Rom1504\|talk]]) 07:56, 16 April 2015 (UTC)

			== String payload is 2 bytes little endian ==

			Hello. In the wiki, it said that "The prefix [of a string] is an unsigned short (thus 2 bytes) in little-endian".
			However, the official mc wiki says is big endian. Checking the format of NBT files wroted by Minecraft also confirm is big-endian.
			So, why it is said is little ?

			Thank you.

imported>Homelessrobot: endianness confusion

2016-05-30T06:16:23Z

endianness confusion

← Older revision		Revision as of 06:16, 30 May 2016
Line 26:		Line 26:

	The shortTest example just above the examples section lists "127" as matching up with "7F FF" but 127 would be 00 7F and 7F 00 would be 32767. [[User:Lashtear\|Lashtear]] ([[User talk:Lashtear\|talk]]) 00:36, 22 August 2012 (MST)		The shortTest example just above the examples section lists "127" as matching up with "7F FF" but 127 would be 00 7F and 7F 00 would be 32767. [[User:Lashtear\|Lashtear]] ([[User talk:Lashtear\|talk]]) 00:36, 22 August 2012 (MST)

			== endianness confusion ==

			The table in the specification section states that the length part of the header for string values is little-endian while in the hello_world.nbt file it is clearly in big-endian. I have not tested my code thoroughly so I have not submitted an edit, but it seems to me that all numerical values regardless of significance (either as payloads or length values in headers) are encoded in a network byte order (big-endian). --[[User:Homelessrobot\|Homelessrobot]] ([[User talk:Homelessrobot\|talk]]) 06:16, 30 May 2016 (UTC)

	== Re: Annoying Format ==		== Re: Annoying Format ==

imported>Rom1504: /* dead link */

2015-04-16T07:56:42Z

dead link

← Older revision		Revision as of 07:56, 16 April 2015
Line 50:		Line 50:

	http://wiki.vg/nbt/ is a dead link (in the abstract of the article)		http://wiki.vg/nbt/ is a dead link (in the abstract of the article)
			--[[User:Rom1504\|Rom1504]] ([[User talk:Rom1504\|talk]]) 07:56, 16 April 2015 (UTC)

imported>Rom1504: /* dead link */ new section

2015-04-16T07:56:31Z

dead link: new section

← Older revision		Revision as of 07:56, 16 April 2015
Line 46:		Line 46:

	:Good thing we're not wikipedia, then [[User:Barneygale\|Barneygale]] ([[User talk:Barneygale\|talk]]) 23:58, 30 October 2012 (MST)		:Good thing we're not wikipedia, then [[User:Barneygale\|Barneygale]] ([[User talk:Barneygale\|talk]]) 23:58, 30 October 2012 (MST)

			== dead link ==

			http://wiki.vg/nbt/ is a dead link (in the abstract of the article)

imported>Barneygale at 06:58, 31 October 2012

2012-10-31T06:58:39Z

← Older revision		Revision as of 06:58, 31 October 2012
Line 22:		Line 22:

	~[[User:Drainedsoul\|Drainedsoul]] 15:06, 29 November 2011 (PST)		~[[User:Drainedsoul\|Drainedsoul]] 15:06, 29 November 2011 (PST)

			== shortTest example ==

			The shortTest example just above the examples section lists "127" as matching up with "7F FF" but 127 would be 00 7F and 7F 00 would be 32767. [[User:Lashtear\|Lashtear]] ([[User talk:Lashtear\|talk]]) 00:36, 22 August 2012 (MST)

			== Re: Annoying Format ==

			'''Just remember''',

			Wikipedia is ''not'' the place to voice personal opinions, in this case about whether or not creating a new file format was necessary.

			There are many reasons why Mojang ''may'' have chosen to use this format, ('''not endorsed by Mojang AB'''):

			*They felt that other data structures were inadequate
			*They wished to use all of their own code for the data structure (allows greater modification/control etc.)
			*They wanted it to be more difficult for people to edit data files
			*They believed that it would save space
			*They have some future use planned where it may be necessary
			Among others


			If even for the simple fact that they wanted to set themselves apart from the crowd, voice your opinion on a forum or blog (or this discussion page). Wikipedia is supposed to be a place where unbiased information is presented for public consumption.

			:Good thing we're not wikipedia, then [[User:Barneygale\|Barneygale]] ([[User talk:Barneygale\|talk]]) 23:58, 30 October 2012 (MST)

imported>Drainedsoul at 23:08, 29 November 2011

2011-11-29T23:08:57Z

← Older revision		Revision as of 23:08, 29 November 2011
Line 13:		Line 13:
	I have altered the bigtest.nbt example due to the fact the example readout was not correctly representing the UTF-8 encoding actually contained in the document.		I have altered the bigtest.nbt example due to the fact the example readout was not correctly representing the UTF-8 encoding actually contained in the document.

	The string purported to be "HELLO WORLD THIS IS A TEST STRING !" but was actually "HELLO WORLD THIS IS A TEST STRING !"		The string purported to be "HELLO WORLD THIS IS A TEST STRING !" but was actually "HELLO WORLD THIS IS A TEST STRING ÅÄÖ!"

	This can be verified by examining the bytes which make up the string:		This can be verified by examining the bytes which make up the string:

imported>Drainedsoul at 23:08, 29 November 2011

2011-11-29T23:08:34Z

← Older revision		Revision as of 23:08, 29 November 2011
Line 20:		Line 20:

	Using a [http://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder UTF-8 decoder] in "Freeflow Numeric" mode.		Using a [http://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder UTF-8 decoder] in "Freeflow Numeric" mode.

			~[[User:Drainedsoul\|Drainedsoul]] 15:06, 29 November 2011 (PST)

imported>Drainedsoul at 23:08, 29 November 2011

2011-11-29T23:08:03Z

← Older revision		Revision as of 23:08, 29 November 2011
Line 6:		Line 6:

	:"Tagged" imples: tag type, name, payload. "Untagged" implies just the payload. If you had a TAG_List of TAG_Shorts, each element of the list is just the short payload, i.e. 2 bytes per element. As such the children of TAG_Lists are unnamed. TAG_Lists define a "tagId" at the start of their payload so you know what kind of tag you're reading. Named tags exist only in two circumstances: 1) As children of TAG_Compound, 2) As the root node. [[User:Barneygale\|Barneygale]] 17:52, 25 November 2011 (MST)		:"Tagged" imples: tag type, name, payload. "Untagged" implies just the payload. If you had a TAG_List of TAG_Shorts, each element of the list is just the short payload, i.e. 2 bytes per element. As such the children of TAG_Lists are unnamed. TAG_Lists define a "tagId" at the start of their payload so you know what kind of tag you're reading. Named tags exist only in two circumstances: 1) As children of TAG_Compound, 2) As the root node. [[User:Barneygale\|Barneygale]] 17:52, 25 November 2011 (MST)

			:Thanks! Understood.

			----

			I have altered the bigtest.nbt example due to the fact the example readout was not correctly representing the UTF-8 encoding actually contained in the document.

			The string purported to be "HELLO WORLD THIS IS A TEST STRING !" but was actually "HELLO WORLD THIS IS A TEST STRING !"

			This can be verified by examining the bytes which make up the string:

			72 69 76 76 79 32 87 79 82 76 68 32 84 72 73 83 32 73 83 32 65 32 84 69 83 84 32 83 84 82 73 78 71 32 195 133 195 132 195 150 33

			Using a [http://software.hixie.ch/utilities/cgi/unicode-decoder/utf8-decoder UTF-8 decoder] in "Freeflow Numeric" mode.