chore(pack): make config files opt-in and ship a PetProtect default
.packwizignore ignored config/ and defaultconfigs/ wholesale. They are now ignored per-entry (config/*) with deliberately authored files re-included at the bottom of the file, so one config can ship without any risk of pulling every runtime-generated config into the index - which matters because this repo doubles as a server directory. Ships config/petprotect.json disabling BOTH pet damage and death protection. PetProtect's isInvulnerableTo mixin gates on prevent_pet_damage alone, so disabling prevent_pet_death by itself leaves pets invulnerable to nearly all damage and Pet Cemetery's death -> collar -> respawn loop still never fires. prevent_pet_attack remains true, so pets are not provoked into fights. Without this file the two mods cancel each other: PetProtect's defaults keep pets immortal, so Pet Cemetery is dead weight. The config installs on clients as well as the server; that is harmless since petprotect itself is side = "server", but packwiz has no per-file side flag for non-metafile entries.
This commit is contained in:
1 parent
e371e51856
commit
387ee1ef9b
4 files changed
+27
-5
No files matched your search
@@ -6,7 +6,7 @@ pack-format = "packwiz:1.1.0"
|
||||
[index]
|
||||
file = "index.toml"
|
||||
hash-format = "sha256"
|
||||
hash = "8777e7fc3042b6fed9025bd5af4846c49f4a208cabe06dc5a8ea7b0e15c3f8d5"
|
||||
hash = "29cee97f1dd3e093e11e3e565cbf11dd1ddc6203a82e7e81b93016e601fa9989"
|
||||
|
||||
[versions]
|
||||
minecraft = "1.21.1"
|
||||
|
||||
Reference in new issue
Block a user