You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Being able to customize individual spawned entity NBT and apply wave modifiers in the JSON of each gate is great, it offers a surprisingly robust method of custom encounter creation.
However, it would be useful to be able to apply some kind of global NBT or modifier that applies to the entire Gate, and maybe per wave NBT additions as well.
Say I wanted a Gate where every entity has the same custom NBT tag; as a simple example, giving all of them the custom name "Bob." As of now, I'd have to add
after every single entity in the list of entities spawned in each wave. It'd work, certainly, but doing it this way is tedious and lengthens the code considerably. Being able to just put this in once at the top of a gate's JSON or in a wave's parameters to have it apply to the entirety of the gate or wave would help to streamline the process considerably.
The text was updated successfully, but these errors were encountered:
Bubbline5
changed the title
Gate and Wave-Specifc Universal Modifiers/Compound Tags for Data Packs
Suggestion: Gate and Wave-Specifc Universal Modifiers/Compound Tags for Data Packs
Sep 12, 2024
Being able to customize individual spawned entity NBT and apply wave modifiers in the JSON of each gate is great, it offers a surprisingly robust method of custom encounter creation.
However, it would be useful to be able to apply some kind of global NBT or modifier that applies to the entire Gate, and maybe per wave NBT additions as well.
Say I wanted a Gate where every entity has the same custom NBT tag; as a simple example, giving all of them the custom name "Bob." As of now, I'd have to add
"nbt": { "CustomNameVisible": 1, "CustomName": {"Bob"}}
after every single entity in the list of entities spawned in each wave. It'd work, certainly, but doing it this way is tedious and lengthens the code considerably. Being able to just put this in once at the top of a gate's JSON or in a wave's parameters to have it apply to the entirety of the gate or wave would help to streamline the process considerably.
The text was updated successfully, but these errors were encountered: