Fix detection of weird trees, and update some Thaumcraft config#38
Fix detection of weird trees, and update some Thaumcraft config#38WayOfTheQway wants to merge 2 commits intobspkrs:masterfrom WayOfTheQway:master
Conversation
…ft config Using ModulusBlockID with a modulus of 4 can mess up non-standard log blocks (like Thaumcraft 5 logs - Greatwood is log:0 through log:2, and Silverwood is log:3 through log:5) And I updated the Thaumcraft default config so it works with Thaumcraft 5
…s fail. The auto detection uses only the first log that was broken as the list of BlockIDs, so if the TreeDef has other BlockIDs then the autodetect doesn't realize this, and it would force the TreeDef to be null and make everything else fail afterward.
|
Probably missed the comment in the other PR. I've been converting the metadata stuff to block states, so the config will look like this: |
|
Okay. This was mostly just so I could have it working in my modded survival. I thought I may as well put it out there in case anyone else was having the same problems |
|
First: Sorry I'm replying quite late, I kinda forgot that Github was a thing that I did sometimes. |
So... Detection of trees with multiple block types (like trees with some logs sideways) would sometimes fail depending on what type of log you broke and if it was connected to others etc. That was fixed in the second commit. In the first commit, some stuff having to do with non-standard trees (ones that the logs weren't modulus, but rather one after the other) not being able to be defined correctly.