![]() If you try this with a stripped log which is showing damage, break and replace it with a fresh log, the fresh log will now show damage (and extraction will still only be 1mb/cycle). Interestingly, if you allow the extractor to extract from a fresh log until the log shows damage, say 80% damage, then break and replace the log, the new log will show the same damage. You can let the stripped log break entirely and then replace it with a fresh log and it will still only extract at 1mb/cycle. You can break the stripped log and replace it with a fresh one and it will continue to extract from the new log at 1mb/cycle. ![]() The problem arises once the extractor shifts from the normal extraction rate (4mb/cycle in my case) to the stripped rate (1mb/cycle). At this point, extraction continues at a much lower 1mb/cycle rate until the stripped log eventually breaks. It will continue extracting at this rate until the log is used up and is replaced with a stripped version of the log. For Acacia wood in the pack I'm using, that's 4mb/cycle. I was recently reminded that I had failed to file a bug on this while watching Direwolf20's Let's Play S10E39 where he too encounters this.Ī newly placed fluid extractor will extract latex from a log at the documented rate. ![]() ![]() Thus I've experienced this in two worlds total. I'm playing in the direwolf20 1.16.4 modpack (1.5.1) but have experienced this issue in another 1.16 modpack recently. Crashlog If Applicable (Upload to pastebin/gist): ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |