I know that they are sort of like that, but the posts should just be ignored to prevent a mod combined with another great mod's thread to be degraded into a flame war.
Then why did you report my posts instead of ignoring them? That wasn't a very courteous thing to do, and according to the rule section you quoted, two wrongs don't make a right, so I fail to see how your third wrong improved the situation.
The only flame-war being risked in recent memory on this thread seems to be the one you're currently bringing about.
Please be so kind as to take your trolling elsewhere.
It is my hope that through my patented application of wit and charm, the situation will rapidly return to normal.
I watched your recent interview last night (and the other 7 from almost a year ago), and just wanted to say...
"YOU ARE THE MAN FC!" Thank you and many, many studs to you.
Dont ever change, and dont let all these wankers with idiotic comments discourage you.
BTB & BTW are probably the most well thought out mods I have seen to date, and i am looking forward to the future with baited breath. Cant wait to find out what you have been hinting about.
My guess is a Thunderdome to go with the gimp suit and ropes "Two men enter, one man leaves"...
Nah probably not till SMP is supported? (just kidding)
But seriously keep doing what your doing, your "patented application of wit and charm" gives me frequent chuckles. And your work ethic give me hope that not everyone in the world is out to make a quick buck. People like you make the world a less ignorant place and force others to think for themselves. Which could only be a good thing!
By the way that npc kid soldier idea was pure gold, maybe thats who could fight in the Thunderdome?
I was wondering if using a builder with the path markers was bugged in BTB. It's not all the time, but seems if I start a builder then stop it early the old path marks are left behind invisibly. If I don't place and remove from the same location they were at, I'll get a crash and corrupt save on placing a new builder. Fortunately if I go into MCedit and place something over those blocks it allows me to continue.
Oh, and thanks for screwing up SMP for me :P. now I can't stand to play without BTW at the least (though BTB is becoming a must too).
I'm encountering an odd sort of glitch that I'm hoping somebody else can confirm. Under some conditions (which I don't fully understand), my hemp requires a block update to grow. At first I thought it occurred whenever a Lens beam occupied the space above the hemp, but I've long since removed the Lens and it's still happening.
Place a block, and BOOM: Instant growth.
Now, this isn't so much a bug report as it is a "have others been having this issue?".
This is because there is a number of external factors that may be causing this; I'm using BTB (and therefore not the latest version of BTW (3.52)), I have Optifine installed on top of BTW, the world where I encountered this bug is a Creative world, I have the time set to Day Only (in Optifine)...
I know how vehement FC is about the value of time, and so I'd hate to be the one to make him waste an afternoon trying to reproduce a bug that was actually caused by Optifine.
Note to anybody who tries to reproduce this: Make sure your entire farmland becomes moist before planting the hemp. Farmland becoming wet is a block update, which will allow the hemp to grow.
I've had hemp grow when I do a block update, but I think it's just to do with the way things grow (I'm not sure, but I think things only grow on chunk updates)
Huh. Turns out my little patch of farmland was exactly flush against the corner of a chunk and thus didn't cross any boundaries. I extended it out a bit, and sure enough, placing a block now only updates the part of the farm in the same chunk.
To be honest, I did try to grow Wheat in that same area to confirm that Hemp was the only thing having trouble growing, but the seeds decided to grow uncharacteristically slow that time, and I got bored and just assumed my previous test was enough.
That "previous test" was a wheat farm I put near some mechanical systems that, in hindsight, probably caused chunk updates.