Open edayot opened 1 year ago
files named [".mcfunction","..mcfunction","...mcfunction"] are not copied during beet build
[".mcfunction","..mcfunction","...mcfunction"]
beet build
In vanilla it's possible to reference such function, and make loading existing datapack not build with beet not working at all.
Here's an example :
erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ cat beet.yaml data_pack: load: [.] resource_pack: load: [.] output: build pipeline: - add_header erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ cat add_header.py from beet import Context, Function def beet_default(ctx: Context): for f in ctx.data.functions.keys(): ctx.data.functions[f]=Function(f"say {f}") erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$ tree -la . ├── add_header.py ├── beet.yaml ├── build │ └── code_void_data_pack │ ├── data │ │ └── test │ │ └── functions │ │ ├── a │ │ │ ├── a.mcfunction │ │ │ ├── a.py.git.mcfunction │ │ │ └── .mcfunction.mcfunction │ │ ├── a.mcfunction │ │ ├── a.py.git.mcfunction │ │ ├── .mcfunction.mcfunction │ │ └── .mcfunction.mcfunction.mcfunction │ └── pack.mcmeta └── data └── test └── functions ├── a │ ├── a.mcfunction │ ├── a.py.git.mcfunction │ ├── ...mcfunction │ ├── ..mcfunction │ ├── .mcfunction │ └── .mcfunction.mcfunction ├── a.mcfunction ├── a.py.git.mcfunction ├── ...mcfunction ├── ..mcfunction ├── .mcfunction ├── .mcfunction.mcfunction └── .mcfunction.mcfunction.mcfunction 10 directories, 23 files erwan@erwan-pc-portable-ubuntu:~/Documents/Dev/beet/examples/code_void$
In the fork that I created here in the build directory there is now all the files.
But I don't know if it's the way to do it.
files named
[".mcfunction","..mcfunction","...mcfunction"]
are not copied duringbeet build
In vanilla it's possible to reference such function, and make loading existing datapack not build with beet not working at all.
Here's an example :