{ "_fv": 57, "_type": "procedure", "definition": { "procedurexml": "thexthezno_ext_triggerThis assigns a belly ID and coords to a entity's NBT data.only do all this stuff if there is no belly already assignedthis is new nbt tag for 2.0.0 to indicate whether the belly data has been set. instead of using the belly name string like before. since that could be set externally by a command block or something, this is to make sure that wont glitchvoreSetupvoreSetupTRUElocal:thexMULTIPLYMINUSROUNDMULTIPLYRANDOM1005048local:thezMULTIPLYMINUSROUNDMULTIPLYRANDOM1005048this is the non backwards compatible change made in 2.0.0:\nnow the belly origin is separate from the offset and they are added upon teleport. makes it more datapack or commandblock freindly. those can be used to help make custom stomach configurationsbellyOriginXlocal:thexbellyOriginZlocal:thezCUSTOM:Vorebose[Vore Mod] Your belly origin is X: local:thexZ: local:thezbellyTypethis is set the belly name depending on the type of mobforge:stomach_noeatbellyTypenoeatnoEatTRUEforge:stomach_animalbellyTypeanimalORforge:stomach_anthroEntityPlayerbellyTypeanthroforge:stomach_rottenbellyTyperottenforge:stomach_rotten_animalbellyTyperotten_animalbellyTypenoeatnoEatTRUECUSTOM:Voreboseprint out in the log the name of the entity and belly name they get got assigned belly name of bellyTypethis is where the offsets are made depending on the belly nameORbellyTypeanimalbellyTyperotten_animalbellyOffsetX30bellyOffsetY17bellyOffsetZ10ORbellyTypeanthrobellyTyperottenbellyOffsetX9bellyOffsetY23bellyOffsetZ10eatText[prey] got eaten by [pred]as of 2.0.0, the exit command is stored in the pred's nbt and transfered to the prey when they are eated. then when the prey right clicks the exit block, the command is run instead of checking a belly origin block. and much like the origin block, if the command is 'uneat', it teleports the player back to the exit coord in their nbt.predExitCMDuneatCUSTOM:Vorebose" } }