Incompatible with Better Trees
Closed this issue ยท 10 comments
Describe the bug
Incompatible with this mod https://modrinth.com/datapack/better-trees v1.8.3
Minecraft version
1.21.1
Fabric API version
16.14
Mod version
1.21.1.7
Configuration
{
"trees": {
"allowedLogs": [],
"deniedLogs": [],
"allowedLeaves": [],
"allowedNonDecayLeaves": [],
"deniedLeaves": [],
"breakMode": "FALL_ALL_BLOCK",
"detectionMode": "ABOVE_CUT",
"maxScanSize": 500,
"maxSize": 100,
"maxLeafDistanceFromLog": 15,
"maxSizeAction": "ABORT",
"breakOrder": "FURTHEST_FIRST",
"minimumLeavesAroundRequired": 1,
"includePersistentLeavesInRequiredCount": true,
"treeBreaking": true,
"leavesBreaking": true,
"leavesBreakingForceRadius": 0,
"allowMixedLogs": false,
"breakNetherTreeWarts": true,
"breakMangroveRoots": true,
"searchAreaRadius": -1,
"allowedAdjacentBlocks": [],
"adjacentStopMode": "STOP_ALL",
"spawnItemsAtBreakPoint": false
},
"tools": {
"allowed": [],
"denied": [],
"durabilityMode": "NORMAL",
"ignoreTools": false,
"damageMultiplicand": 1.0,
"damageRounding": "ROUND_DOWN",
"speedMultiplicand": 0.5,
"forceToolUsage": false
},
"player": {
"allowedTags": []
},
"enchantment": {
"requireEnchantment": false
},
"sneakMode": "SNEAK_DISABLE",
"breakInCreative": false,
"lootInCreative": true,
"notificationMode": "ACTION_BAR"
}Relevant log output
Probably the same as #861 which is fixed in recent versions
@Rakambda But many mods I used isn't catch up yet, that's why 1.21.1
The other issue is 1.21.1 too.
#861 (comment) I don't know if I'll back port the changes. It's quite some maintenance to do all the changes on 5 different versions. Especially that 1.21.1 will soon be a year old.
Use some previous version of the mod for 1.21.1, some didn't have this bug at first.
@Rakambda How about 1.21.4? Is the issue fixed for the screenshoted problem
@Rakambda Broo, it's too far for 1.21.5 :(
Right now I'm bulk update all my mods to 1.21.4 and this version alone kicks out many of mods I used in 1.21.1
As I said earlier, use some previous version of the mod for 1.21.1, some didn't have this bug at first.
If you need that version that much, you can always open a PR with the backports of all the fixes/features that were made on 1.21.5 compared to 1.21.1/2/3/4. I Just personally don't have the time for the comming months to maintain several versions at once.
@Rakambda I'm practically blind for something like PR the backports and assembly it back to functioning with ver 1.21.4
