Bug on oak fence to cherry fence
Psychodeus opened this issue ยท 11 comments
I'm in the middle of project right now, but I've run test like this:
Notice my hand what block I'm placing vs what actually placed / interpreted.
When I include horseman mod, Flashback mod interpret my oak fence as cherry fence

Then when I exclude your horseman mod, it turns it to spruce fence

Before I decide to include your horseman, there were no issues about sudden changing blocks like this, only after
Try with only Horseman and flashback, on a clean instance.
This is user error. The user included the mod after taking the recording which caused the block IDs to shift. They're also using an outdated version of Flashback, otherwise they would've got a warning.
Try with only Horseman and flashback, on a clean instance.
This is user error. The user included the mod after taking the recording which caused the block IDs to shift. They're also using an outdated version of Flashback, otherwise they would've got a warning.
Is there a workaround this other than reshoot again?
This is user error. The user included the mod after taking the recording which caused the block IDs to shift. They're also using an outdated version of Flashback, otherwise they would've got a warning.
I've just updated to used the LATEST flashback v0.36.0 and Horseman 1.5.1, and yet it turns my oak fence into Mangrove fence.
I've include the Horsemen mod BEFORE I take recording, and the result is still Flashback mod misinterpret the fence.
otherwise they would've got a warning.
No there was no warning.
Form now I don't want to use Horseman before this crucial bug is gone. Because every time I've done for the recording this bug ruined everything and I have to reshoot everything from 0.
Oak fence turns to Mangrove fence
@Moulberry This is not the first time Flashback gone wrong to interpret blocks, for example with mod leavesly-1.4.0+1.21.7
Recording with the leavesly mod:
After took off the leavesly mod:
But when I put the leavesly mod back, it went normal and playable.
Now for current case, I've exclude connectiblechains-2.5.4+1.21.8 and turns out it was the problem maker! After that the warning pop up...
The fence changer is connectible chains mod


