(Backport of the 1.21.1 changes to the Crop Tweak)
minecraft:melon_stem, minecraft:pumpkin_stem and minecraft:sweet_berry_bush to the default blacklisted_harvest_crops tagage blockstate will be detectedThanks for your patience with this recurring problem that has been fixed by outright removing it:
{
"type": "vtweaks:fluid_conversion",
"input": [{
"item": "minecraft:stick"
}, {
"tag": "minecraft:wool"
}],
"output": {
"item": "minecraft:white_wool"
},
"fluid": "minecraft:water"
}
Anvil Recipe:
cpFromLeft has been renamed to copyTagsFromLeftcpFromRight has been renamed to copyTagsFromRightstrict. When set to false, the inputs on both sides of the recipe will ignore NBT;
otherwise the inputs will need to match the NBT specified in the datapack entryWater Conversion Recipes:
vtweaks:valuable
vtweaks:valuable item can be enchanted, it'll only
save the item if it's enchanted.vtweaks-common.toml file to verify that your previous settings are
what they should beFluidConversionTweak not working for many reasonsItemFrameTweak: Allows any vtweaks:clear_glass, or glow ink sac, to be activated on an item frame while sneaking
to make the item frame transparent or glowing respectively. DemoSplashPotionTweak: Allows splash potions of water to behave the same as throwing an item in water, but using
V-Tweaks' Fluid Conversion Recipes. Works as an alternative if you'd like to set enableFluidConversionRecipes
to false, but only works with blocks instead of blocks and items. Demovtweaks-common.toml - if you previously changed enableCactusItemProtection,
you'll need to change it again but in vtweaks-common.toml 🙁useOriginalFoodTooltipColor (bool): if food has a custom color such as via rarity or NBT, use that color
instead of the other colors defined below for the hunger bar. If food has no given custom color, then the
default color (or the buff/debuff color) will be
used. DemofoodTooltipColor (string): the HEX code for a normal food that gives no Positive / Negative potion effects on
consumptionfoodTooltipPositiveColor (string): the HEX code for food that gives NO Negative Potion Effects and at
least one Positive potion effect on consumptionfoodTooltipNegativeColor (string): the HEX code for food that gives at least one Negative potion effect on
consumptionfoodTooltipMultiplier (float): similar to health, 1 hunger is equivalent to half a hunger haunch. This setting
controls a multiplier for this in terms of the hunger tooltip on foods.foodTooltipSaturationColor (string): the HEX code for the saturation a food givesjava.lang.IllegalStateException: Accessing LegacyRandomSource from multiple threads. I've looked into this
issue for most of my day today and I have no earthly idea what I'm doing wrong to cause this, but hopefully a small
change I made may have resolved this.This rewrite includes a couple of major changes:
[CODE] The Tweak system has been introduced. Create a new tweak by extending VTweak and using the @Tweak
annotation. The config system will automatically grab onto what configs you need based on this annotation, and the
Tweak Registry will automatically grab and fire all custom tweaks' events[CODE] Config System has been overhauled, allowing each tweak to house its own configs rather than making them
static members of some conglomerate config class. The category param in the @Tweak annotation tells the config
system what category to put the tweak's configs in - if it's not one of the ones listed in CommonConfig.java
or ClientConfig.java, then it will be skipped.it.unimi.dsi.fastutil.objects.Object2ObjectOpenHashMap.rehash
errorcpFromLeft and cpFromRight. Assumes to be false if not
included. cpFrom[Left|Right] will copy all NBT except for those defined in the output, to the output. You can
choose to set BOTH to true, but any overlap in NBT will be overwritten by the RIGHT input.Accessing LegacyRandomSource from multiple threads errors.vtweaks:anvil recipe type -- see below!vtweaks:anvil recipes to control inputs and costvtweaks:anvilInputs AND outputs can have NBT defined for them! This recipe type performs a soft NBT comparison.
Example: if your item is defined as {"item": "minecraft:stick", "nbt": { "Damage": 0 }}, then if you input a stick
with enchantments or other NBT it will succeed so long as the NBT matches at the bare minimum the NBT defined in the
recipe (in this case, {Damage:0}).
imperishable.json:
{
"type": "vtweaks:anvil",
"left": {
"item": "minecraft:enchanted_book",
"nbt": {
"StoredEnchantments": [
{
"id": "minecraft:unbreaking",
"lvl": 3
}
]
}
},
"right": {
"item": "minecraft:enchanted_book",
"nbt": {
"StoredEnchantments": [
{
"id": "minecraft:unbreaking",
"lvl": 3
}
]
}
},
"result": {
"item": "minecraft:enchanted_book",
"nbt": {
"StoredEnchantments": [
{
"id": "vtweaks:imperishable",
"lvl": 1
}
]
}
},
"cost": 24
}
lumbering.json:
{
"type": "vtweaks:anvil",
"left": {
"item": "minecraft:writable_book"
},
"right": {
"item": "minecraft:golden_axe",
"nbt": {
"Damage": 0
}
},
"result": {
"item": "minecraft:enchanted_book",
"nbt": {
"StoredEnchantments": [
{
"id": "vtweaks:lumbering",
"lvl": 1
}
]
}
},
"cost": 16
}
minecraft:melon_stem, minecraft:pumpkin_stem and minecraft:sweet_berry_bush to the default blacklisted_harvest_crops tagage blockstate will be detectedc:seeds
#c:chickens can have their feathers plucked
forge namespace to now use the c namespace instead
Durability: in the Durability Tooltip is now localizable!Initial port to 1.21 (and 1.21.1 by proxy) using NeoForge. Tested full suite of features locally in dev server, so hopefully there'll be minimal server-only issues, but we'll see!
Not too much has changed from a functional perspective really:
c:seeds
#c:chickens can have their feathers plucked
forge namespace to now use the c namespace instead
Durability: in the Durability Tooltip is now localizable!Initial port to 1.21 (and 1.21.1 by proxy) using NeoForge. Tested full suite of features locally in dev server, so hopefully there'll be minimal server-only issues, but we'll see!
Not too much has changed from a functional perspective really:
c:seeds
#c:chickens can have their feathers plucked
forge namespace to now use the c namespace instead
Durability: in the Durability Tooltip is now localizable!Initial port to 1.21 (and 1.21.1 by proxy) using NeoForge. Tested full suite of features locally in dev server, so hopefully there'll be minimal server-only issues, but we'll see!
Not too much has changed from a functional perspective really:
#c:chickens can have their feathers plucked
forge namespace to now use the c namespace instead
Durability: in the Durability Tooltip is now localizable!Initial port to 1.21 (and 1.21.1 by proxy) using NeoForge. Tested full suite of features locally in dev server, so hopefully there'll be minimal server-only issues, but we'll see!
Not too much has changed from a functional perspective really: