https://forge.gemwire.uk/index.php?action=history&feed=atom&title=DynamicOps%2F1.18DynamicOps/1.18 - Revision history2026-05-22T22:54:33ZRevision history for this page on the wikiMediaWiki 1.35.0https://forge.gemwire.uk/index.php?title=DynamicOps/1.18&diff=3176&oldid=prevShrimpBot: Copy DynamicOps to MC1.18 archive2022-06-10T07:44:22Z<p>Copy <a href="/wiki/DynamicOps" title="DynamicOps">DynamicOps</a> to MC1.18 archive</p>
<p><b>New page</b></p><div>The <code>DynamicOps</code> class is part of mojang's DataFixerUpper serialization library; DynamicOps are used alongside [[codecs/1.18|codecs]] to convert java objects to a serialized format and back. While Codecs describe how a java object is to be serialized, DynamicOps describe the format the object is to be serialized to.<br />
<br />
The DataFixerUpper library includes several DynamicOps for serializing to json; vanilla minecraft also includes a DynamicOps for serializing to minecraft's [[Using NBT/1.18|NBT]] format.<br />
<br />
= Builtin DynamicOps =<br />
<br />
== JsonOps ==<br />
<br />
The <code>JsonOps</code> DynamicOps are used to serialize and deserialize json data. These are instances of <code>DynamicOps<JsonElement></code>, meaning that they are used to convert java objects to and from <code>JsonElement</code> instances. These can used in conjunction with codecs to serialize/deserialize objects from assets and datapacks.<br />
<br />
There are two public instances of JsonOps: <code>JsonOps.INSTANCE</code> and <code>JsonOps.COMPRESSED</code>. Compressed data is represented as a single string to read/write. However, this is never used within vanilla itself.<br />
<br />
== NbtOps ==<br />
<br />
The <code>NbtOps.INSTANCE</code> is an instance of <code>DynamicOps<Tag></code>, meaning it is used to convert java objects to and from <code>Tag</code> instances. This can be used for serializing data into packets to send across networks, as well as serializing persistent data for entities and similar objects.<br />
<br />
There is only one public instance of NbtOps: <code>NbtOps.INSTANCE</code>.<br />
<br />
= Using DynamicOps =<br />
<br />
== Serializing and Deserializing ==<br />
<br />
By combining a <code>Codec<SomeJavaType></code> with a <code>DynamicOps<SomeSerializedFormat></code>, the proper java object can be converted to the serialized form and back. See [[codecs/1.18|codecs]] for details on this subject.<br />
<br />
== Format Conversion ==<br />
<br />
By using the <code>DynamicOps#convertTo</code> instance method with a second DynamicOps instance, data can be converted between two different serialized formats, such as JsonElement to Tag and back.<br />
<br />
<syntaxhighlight lang=java><br />
// converting Tag to JsonElement<br />
JsonElement someJsonElement = NbtOps.INSTANCE.convertTo(JsonOps.INSTANCE, someTag);<br />
<br />
// converting JsonElement to Tag<br />
Tag someTag = JsonOps.INSTANCE.convertTo(NbtOps.INSTANCE, someJsonElement);<br />
</syntaxhighlight><br />
<br />
Depending on the implementation of the DynamicOps used, this may throw an exception or return an empty object if the two formats are incompatible.<br />
<br />
In particular, it is '''not''' safe to convert lists of numbers to NBT in this manner, due to the NBT format's strong typing and the way the NbtOps attempts to create lists of numbers.<br />
<br />
= External Links =<br />
* [https://kvverti.github.io/Documented-DataFixerUpper/snapshot/com/mojang/serialization/DynamicOps.html DynamicOps unofficial javadocs]</div>ShrimpBot