You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I follow the comment in the config file "propertymodifier - common.toml",
according to the comment:
enchantedbook: buyItem1;[buyItem2;buyItemCount2;]enchantment[;level] - enchantment to use (e. g. minecraft:sharpness, supports regex), level for the level (randomly selected if not stated). Outputs an enchanted book, at which the amount of buyItem1 is scaled - a lvl 5 book costs approx. 5 times more than a lvl 1 book. Adding more than one enchantment is impossible
Villagers will provide sharpness 20 ON the book not IN the book, which means item "minecraft:enchanted_book" have nbt Enchantments:[] instead of StoredEnchantments:[], it makes that enchanted book cannot apply on weapon but can use the book as a weapon.
And the amount of buyItem1 is not scaled and it's always 1.
The text was updated successfully, but these errors were encountered:
Minecraft 1.16.5 Forge 36.2.35 PropertyModifier 0.6.4
I follow the comment in the config file "propertymodifier - common.toml",
according to the comment:
enchantedbook: buyItem1;[buyItem2;buyItemCount2;]enchantment[;level] - enchantment to use (e. g. minecraft:sharpness, supports regex), level for the level (randomly selected if not stated). Outputs an enchanted book, at which the amount of buyItem1 is scaled - a lvl 5 book costs approx. 5 times more than a lvl 1 book. Adding more than one enchantment is impossible
I use
villager_1_trades = ["minecraft:librarian;12;2;0.05;enchantedbook;minecraft:emerald;minecraft:sharpness;20"]
Villagers will provide sharpness 20 ON the book not IN the book, which means item "minecraft:enchanted_book" have nbt Enchantments:[] instead of StoredEnchantments:[], it makes that enchanted book cannot apply on weapon but can use the book as a weapon.
And the amount of buyItem1 is not scaled and it's always 1.
The text was updated successfully, but these errors were encountered: