Tags[]
I think function/block tags should be mentioned here, too, especially the #minecraft:tick-tag, as for most datapacks, it will be essential to add functions to them. Also, this is one of the few examples, where you actually need to modify contents of a namespace that is not your own. 178.201.167.142 18:02, 1 January 2018 (UTC)
Issue with pack.mcmeta[]
I have noticed that the game doesn't recognize otherwise correct pack.mcmeta files that are written with raw text editors. Instead, using a JSON editor works. I'm not sure if this issue is exclusive to my operating system (macOS), so I'd want to hear if anyone else has encountered the same issue. Maybe it should be mentioned in Troubleshooting. – Erufailon4 (talk) 09:46, 8 April 2018 (UTC)
The pack.mcmeta files are the same with the ones in resource packs. On my operating system (Windows), it works with both raw text editors and JSON editors. You can try https://jsonlint.com/ to check your json code.--Skylord wars (talk) 11:08, 8 April 2018 (UTC)
The pack.mcmeta file does work with a bare bones text editor though, if you have it plain text and Smart Quotes off, in which it works fine. Though I found in snapshot 20w15a, the pack_format 5 does not work, but 1 does.--71.227.116.150 09:14, 12 April 2020 (UTC)
Get Utilities their own article[]
I think that data pack utilities should get their own article.
This page should contain:
- Syntax-Plugins for the prominent text editors
- Generator Tools (Online): Command Generators and Structural Generators
- Generator Scripts (Offline)
- Transpilers and Frameworks – Unsigned comment added by PixelRayn (talk • contribs) at 14:12, 26 December 2020 (UTC). Sign comments with ~~~~
Remove "What not to do" section[]
The section "What not to do" is irrelevant, as it only lists things that are not reachable through or even relatable to data packs. I suggest removing it entirely. Any rejections? OneNose (talk) 11:37, 26 January 2021 (UTC)