A feedback area designed for scripting and mods suggestions and feedback. Please note bug reports and support issues will be removed.

3

Self references of loot tables

2 Comments

Please sign in to leave a comment.

Sorted by oldest
  • 0
    Registered User commented
    Comment actions Permalink

    I like this idea. I had a similar idea where you'd actually get to use real loot-table tag-types and list up and target all your loot-tables more freely.

    Your approach would require datapacks to be loaded in a certain order to get the desired order of execution of "parent" loot-tables. And loot-tables would also need to allow to be extended (just like real tags) instead of just being overridden if the next datapack loads the same resource-location.

    I guess it'd be more consistent/cleaner to add a new tag-type instead since they serve that purpose exactly and self-references usually (or actually always) result in recursive/circular behavior (think about mcfunction recursion).

  • 0
    Registered User commented
    Comment actions Permalink

    I don’t think this is the best way to solve the problem. Self-references could happen by pure accident, and the mechanism you’re suggesting doesn’t support operations such as adding a new entry to an existing pool of a loot table.