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
TagSupplier.TagBakery currently requires the user to manually prefix the tag location given to queue(RL, RL) and queue(RL, Set<RL>) with the tag type folder name. It would be useful to have overloads of those two methods that take a ResourceKey<Registry<T>> and a TagKey<T> instead of the folder-prefixed tag location and then use Registries.elementsDirPath() to add the folder prefix. This would make the tag generator a bit more ergonomic to use, would avoid mistakes if Mojang decides to change folder names again and also ensures that generating tags for non-vanilla registries correctly prefixes the folder with the registry's namespace on NeoForge (I don't know whether Fabric or Quilt have similar prefixing).
The text was updated successfully, but these errors were encountered:
TagSupplier.TagBakery
currently requires the user to manually prefix the tag location given toqueue(RL, RL)
andqueue(RL, Set<RL>)
with the tag type folder name. It would be useful to have overloads of those two methods that take aResourceKey<Registry<T>>
and aTagKey<T>
instead of the folder-prefixed tag location and then useRegistries.elementsDirPath()
to add the folder prefix. This would make the tag generator a bit more ergonomic to use, would avoid mistakes if Mojang decides to change folder names again and also ensures that generating tags for non-vanilla registries correctly prefixes the folder with the registry's namespace on NeoForge (I don't know whether Fabric or Quilt have similar prefixing).The text was updated successfully, but these errors were encountered: