Quote from MirrormanMart
+1 - divide and conquer always gets me the job done
Please always consider the customer support perspective: For every single bug report there are a thousand users having the same problem though not reporting.
secretname2009 is right, there is a bug. I stripped it down and found out whenever you change the ID of "flower.id", "flower2.id" or "flower3.id" externally using Idfix the error occurs when creating a world.
I already had a nice discussion with Vswe from Steve's Carts on whether that has to be considered a bug in Idfix/IDResolver or the mod concerned (he didn't quite see the responsibility on his side ^^).
So, Annysia & co., could you please be so kind and make the flower blocks work with Idfix, which means not crash when assigned a different block ID from outside?
I know, you can just change that in the EBXL configuration - a nice "workaround" in my eyes. But in the big picture, when you have a hundred mods you don't wanna change IDs in each and every single configuration file, but rather use Idfix to do so.
And Annysia, the problem with not just having to change a couple of IDs afterwards comes in at the latest when you have to migrate your whole server containing 100 mods from, say, Minecraft 1.4.7 to 1.6.4. - at that point Sodom and Gomorrah breaks out ;-)
While I have never used Idfix if I read their forum thread correctly, and I was reading the correct forum thread then there are two different versions. One that does some funkey stuff internally to forge, which am assuming you are using, and then you have Idfix Minus, which makes use of forge's existing code that we use for block id assignment and "improves" from what I am told.
From the what I understand Idfix Minus, should take care of any block interference that may be caused by ExtrabiomesXL, as EbXL relies upon the forge block Id assignment code that Idfix Minus overrides and we don't force block Id's, and as such any such collisions are that occur can hardly be our fault from what I can tell.
Block Id's as they are now cease being an issue in 1.7 as worlds themselves keep track of what is assigned to what id, and since 1.7 is the new build target it is not 1.6, and as I don't know what Idfix does that is causing the issues (Reports of it doesn't work do not help in the least bit.) and the fact that Idfix is already no longer being developed as it is no longer needed, unless you or someone else wants to push a commit that fixes the issues to our github then I am going to have to say this is classified as a non issue.
1
Although I learned from accidentally messing up the tracks, in numerous places, on the first map Doffen released.
1
Well this is the saddest post I could write for my 300 post. It's a sad day because of the locking of the original LBPR thread,even tho I new this was coming thanks to IMblueN4 (aka Sedawan) I'am still sad as this along with TM where the first too things I used when I first joined Minecraft on August 18,2011. Even tho I'am sad I can't wait to see what 1LotS will do with goodbey Scuttles you will be missed😥.
1
1
3
Where on earth did you come up with this conclusion Roncow? RoW has had lots of progress in the past few months, and if look at page 156 you will see Naiten has posted saying the next update is about 40% complet. Then you will see on page 157 DAYdiecast has post a pic of a new train.
1
1
1
1
1
Best wishes MrFiber-Nicholas C. Walter