Data Generators - Revision history

imported>ZWORX52: /* Registries report */ add missing comma in JSON

2024-10-05T12:42:42Z

Registries report: add missing comma in JSON

← Older revision		Revision as of 12:42, 5 October 2024
Line 201:		Line 201:
	}		}
	}		}
	}		},
	"minecraft:mob_effect": {		"minecraft:mob_effect": {
	"protocol_id": 2,		"protocol_id": 2,

imported>LPT4: /* Packets report */ added status state to list

2024-09-14T13:10:52Z

Packets report: added status state to list

← Older revision		Revision as of 13:10, 14 September 2024
Line 77:		Line 77:
	The report is saved in <code>reports/packets.json</code>		The report is saved in <code>reports/packets.json</code>

	At the root of the packets report are a key for each state of the protocol, currently these are "handshake", "login", "configuration" and "play". Each state key maps to an object with two keys, "clientbound" and "serverbound" storing the clientbound and serverbound packets of each state respectively, these two keys map to an object acting as a map of all packets indexed by a unique resource location. Similar to other reports the packets are encoded as an object with the singular key "protocol_id" which is the numeric ID used over the protocol.		At the root of the packets report are a key for each state of the protocol, currently these are "handshake", "status", "login", "configuration" and "play". Each state key maps to an object with two keys, "clientbound" and "serverbound" storing the clientbound and serverbound packets of each state respectively, these two keys map to an object acting as a map of all packets indexed by a unique resource location. Similar to other reports the packets are encoded as an object with the singular key "protocol_id" which is the numeric ID used over the protocol.

	It should be noted that the "handshake" object is the only state object without a "clientbound" key as this state doesn't have any packets that are sent to the client, this may be important to note when attempting to parse the report.		It should be noted that the "handshake" object is the only state object without a "clientbound" key as this state doesn't have any packets that are sent to the client, this may be important to note when attempting to parse the report.

imported>LPT4: /* Packets report */ changed section level for packets report

2024-09-14T12:10:11Z

Packets report: changed section level for packets report

← Older revision		Revision as of 12:10, 14 September 2024
Line 73:		Line 73:
	\|}		\|}

	== Packets report ==		=== Packets report ===
	A report that contains all packets used by both the server and client. This file stores both a resource location and numeric id for each packet used in each state of the protocol. The presence of both a resource location and the numeric id makes it easier to identify the new packet IDs sent by both the server and client as resource locations are more human readable and are less likely to change between versions.		A report that contains all packets used by both the server and client. This file stores both a resource location and numeric id for each packet used in each state of the protocol. The presence of both a resource location and the numeric id makes it easier to identify the new packet IDs sent by both the server and client as resource locations are more human readable and are less likely to change between versions.
	The report is saved in <code>reports/packets.json</code>		The report is saved in <code>reports/packets.json</code>

imported>LPT4: Added packets report as considering the context of this wiki, is probably something one would be interested in.

2024-09-14T11:32:35Z

Added packets report as considering the context of this wiki, is probably something one would be interested in.

@@ Line 72: / Line 72: @@
   | {{no}} || {{no}} || {{yes}} || {{no}}
   |}
 === Blocks report ===

imported>LassiPulkkinen: s/global palette/block state registry/g

2023-11-27T16:10:03Z

s/global palette/block state registry/g

← Older revision		Revision as of 16:10, 27 November 2023
Line 75:		Line 75:
	=== Blocks report ===		=== Blocks report ===

	A report that contains all block states in the ~~global palette~~. Notably, this contains numeric IDs as used on the protocol, so it can be used to get the proper IDs for a version. The report is saved in <code>reports/blocks.json</code>.		A report that contains all block states in the block state registry. Notably, this contains numeric IDs as used on the protocol, so it can be used to get the proper IDs for a version. The report is saved in <code>reports/blocks.json</code>.

	A few sample entries:		A few sample entries:

imported>Pokechu22: /* Command line */ command has changed slightly now that libraries are bundled

2021-12-04T01:42:25Z

Command line: command has changed slightly now that libraries are bundled

← Older revision		Revision as of 01:42, 4 December 2021
Line 7:		Line 7:
	<pre>		<pre>
	java -cp minecraft_server.jar net.minecraft.data.Main		java -cp minecraft_server.jar net.minecraft.data.Main
			</pre>

			Starting in 1.18, this command is used instead due to the server jar bundling libraries instead of merging them into a single file:

			<pre>
			java -DbundlerMainClass=net.minecraft.data.Main -jar minecraft_server.jar
	</pre>		</pre>

imported>Jochembroekhoff: Update table with available registries

2020-04-13T13:52:07Z

Update table with available registries

@@ Line 183: / Line 183: @@
 The key within the root object is the registry's own ID, and the <code>protocol_id</code> there is the ID for the registry over the network (is this used?).  <code>default</code> indicates a default value to be used when one is needed or an unknown value is used.  <code>entries</code> is the actual content of the registry; keys in it are the name of the element and <code>protocol_id</code> is the actual relevant ID.
-The different registries:
+The different registries (ordered by their protocol ID):
 {| class="wikitable"
@@ Line 227: / Line 227: @@
   | <code>minecraft:biome</code>
   | Biome IDs.
   |-
   | <code>minecraft:particle_type</code>
@@ Line 259: / Line 274: @@
   |-
   | <code>minecraft:rule_test</code>
+  |
   |-
@@ Line 275: / Line 293: @@
   | <code>minecraft:recipe_serializer</code>
   | Indicates the format of a recipe when serialized to JSON or over the network; also controls the actual behavior.  For instance, <code>minecraft:crafting_shaped</code> and <code>minecraft:crafting_shapeless</code>.
   |-
   | <code>minecraft:stat_type</code>
@@ Line 284: / Line 305: @@
   | <code>minecraft:villager_profession</code>
   | Professions used by villagers.
   |}

imported>Pokechu22: Recipe-related registries

2019-01-18T02:27:02Z

Recipe-related registries

← Older revision		Revision as of 02:27, 18 January 2019
Line 269:		Line 269:
	\| <code>minecraft:menu</code>		\| <code>minecraft:menu</code>
	\| Different [[inventory]] windows.		\| Different [[inventory]] windows.
			\|-
			\| <code>minecraft:recipe_type</code>
			\| Not used for anything over the network or in recipe JSON files. Internally indicates the device with which a recipe can be used. For instance, <code>minecraft:crafting</code>.
			\|-
			\| <code>minecraft:recipe_serializer</code>
			\| Indicates the format of a recipe when serialized to JSON or over the network; also controls the actual behavior. For instance, <code>minecraft:crafting_shaped</code> and <code>minecraft:crafting_shapeless</code>.
	\|-		\|-
	\| <code>minecraft:stat_type</code>		\| <code>minecraft:stat_type</code>

imported>Pokechu22: /* Registries report */ minecraft:menu was added in 19w02a

2019-01-09T20:18:46Z

Registries report: minecraft:menu was added in 19w02a

← Older revision		Revision as of 20:18, 9 January 2019
Line 256:		Line 256:
	\|-		\|-
	\| <code>minecraft:structure_piece</code>		\| <code>minecraft:structure_piece</code>
	\| IDs for components of structures themselves; see {{Minecraft Wiki\|Generated structures data file format}} (possibly outdated). These IDs are extremely terse; as an example "nesclt" means something like "'''ne''ther fortress ''s''mall ''c''orridor ''l''eft ''t''urn.		\| IDs for components of structures themselves; see {{Minecraft Wiki\|Generated structures data file format}} (possibly outdated). These IDs are extremely terse; as an example "nesclt" means something like "''ne''ther fortress ''s''mall ''c''orridor ''l''eft ''t''urn.
	\|-		\|-
	\| <code>minecraft:rule_test</code>		\| <code>minecraft:rule_test</code>
Line 266:		Line 266:
	\| <code>minecraft:structure_pool_element</code>		\| <code>minecraft:structure_pool_element</code>
	\|		\|
			\|-
			\| <code>minecraft:menu</code>
			\| Different [[inventory]] windows.
	\|-		\|-
	\| <code>minecraft:stat_type</code>		\| <code>minecraft:stat_type</code>

imported>Pokechu22: Information on the registries report, still WIP and I need to write something about the practical applications of it (possibly a separate article on registries in general)

2018-12-13T06:28:19Z

Information on the registries report, still WIP and I need to write something about the practical applications of it (possibly a separate article on registries in general)

Show changes