• 5

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from zkol»

    OK, I read the in developer blog and had a couple for dry runs to figure out how the things are intended to work ...
    Thus, I'm sharing my findings for those who encountered the same issues by migrating EBXL worlds from 1.6.4 to 1.7.10:

    • It seems that EBXL fix 3.15.8B is only for worlds that are created with EBXL 3.15.8
    • To open world that are created with earlier versions of EBXL, you need to
    • keep and modify extrabiomes.cfg to prevent a crash:
    I:quarterlog0.id=0
    I:quarterlog1.id=0
    I:quarterlog2.id=0
    I:quarterlog3.id=0


    I think, I've found my migration path. As soon as I'm successfully finished, I will report the detailed procedure.

    Yep that is indeed the issue, upgrading from older versions kept on the old quarterlogs by default to allow for backwards compatibility but the new names in 1.7.10 ended up resulting in them and they probably should have been fully removed, as people were given pleanty of time to make sure they that old forests had been replaced by that time.

    Anyways on a completely different note I am going to have to step down as a member of the team, I have come to the conclusion that I have been putting myself under to much stress between trying to work on ExtrabiomesXL, and my own maintain my own free time. Getting home from a long/annonying day at work and wanting to relax, only to feel guilty because I know there is work to be done on ExtrabiomesXL and then getting neither relaxations or stuff done on ExtrabiomesXL and just felling at that much worse, is never good for oneself.

    As such I am going to have to retire as a member of the ExtrabiomesXL development team. I might come back to mine craft modding one day but for now I am going to have to step away and wish Annysia and Scott the best of luck. (Maybe they will actually get v4 on out the door as I partially feel that I have been holding it back.)

    Until next time I'll be out exploring the the wonderful world in which we are blessed to exist. (And who knows I may eventually get around to writing that factorio mod that I wanted to make, but always put off because I felt guilty every time I thought about spending time trying to do it instead of working on ExtabiomesXL.)
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from Keybounce»

    Can you clarify this a bit, please?

    Lets say I've got a world with some mystcraft ages, one of which we want to keep, that has some EBXL stuff. No strawberries. Is the following a workable "upgrade" path:

    1. Load up in 1.4.7/mystcraft 0.9.5/whichever EBXL that is, verify that everything's OK (check).
    2. Load up in 1.4.7/mystcraft 0.10.0/same EBXL to update mystcraft age format data and migrate biomes properly.
    3. Load up in 1.6.4/mystcraft 0.10.5/_THIS_ EBXL to provide world with 1.7.10 upgrade information
    4. Load up in 1.7.10/mystcraft 0.11.0/new EBXL and play

    About the only thing that may cause issues is the fact that by default some of the old 2x2 trees may have issues, and this "patch" and 1.7.10 stuff may possibly have a small issue with the old "quarter" logs. During 1.6 time period I was working on phasing out the old versions as they had issues and they are technically not enabled in 1.7 as they were meant to be fully removed by then, and when I did the update prep I noticed that there was a potential for a crash there, but I did not test it at this time.

    So the simple answer is that you may end up loosing any fir or redwood trees that you have from the 1.4.7 world, but other than than it should work with the upgrade path that you have described, but I can't guarantee it as I have never tried.
    Posted in: Minecraft Mods
  • 1

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from Chocohead»
    It seems that the latest version of ProjectE breaks with EBXL:

    [Server thread/ERROR] [FML/]: Caught exception from ProjectE
    java.lang.ArrayIndexOutOfBoundsException: 7
    at extrabiomes.items.ItemNewSapling.func_77667_c(ItemNewSapling.java:33) ~[ItemNewSapling.class:?]
    at net.minecraft.item.ItemStack.func_77977_a(ItemStack.java:359) ~[add.class:?]
    at moze_intel.projecte.utils.Utils.getODItems(Utils.java:704) ~[Utils.class:?]
    at moze_intel.projecte.emc.EMCMapper.addMapping(EMCMapper.java:241) ~[EMCMapper.class:?]
    at moze_intel.projecte.emc.EMCMapper.loadEmcFromOD(EMCMapper.java:409) ~[EMCMapper.class:?]
    at moze_intel.projecte.emc.EMCMapper.map(EMCMapper.java:32) ~[EMCMapper.class:?]
    at moze_intel.projecte.MozeCore.serverStarting(MozeCore.java:120) ~[MozeCore.class:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_51]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:513) ~[forge-1.7.10-10.13.0.1207.jar:?]
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) ~[?:?]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.post(EventBus.java:275) ~[guava-16.0.jar:?]
    at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:208) ~[forge-1.7.10-10.13.0.1207.jar:?]
    at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:187) ~[forge-1.7.10-10.13.0.1207.jar:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_51]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.post(EventBus.java:275) ~[guava-16.0.jar:?]
    at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:118) [LoadController.class:?]
    at cpw.mods.fml.common.Loader.serverStarting(Loader.java:739) [Loader.class:?]
    at cpw.mods.fml.common.FMLCommonHandler.handleServerStarting(FMLCommonHandler.java:278) [FMLCommonHandler.class:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_51]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at Reflector.callBoolean(Reflector.java:332) [Reflector.class:?]
    at net.minecraft.server.integrated.IntegratedServer.func_71197_b(IntegratedServer.java:161) [bsx.class:?]
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:387) [MinecraftServer.class:?]
    at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685) [?:?]
    [23:42:44] [Server thread/ERROR] [FML/]: A fatal exception occurred during the server about to start event
    java.lang.ArrayIndexOutOfBoundsException: 7
    at extrabiomes.items.ItemNewSapling.func_77667_c(ItemNewSapling.java:33) ~[ItemNewSapling.class:?]
    at net.minecraft.item.ItemStack.func_77977_a(ItemStack.java:359) ~[add.class:?]
    at moze_intel.projecte.utils.Utils.getODItems(Utils.java:704) ~[Utils.class:?]
    at moze_intel.projecte.emc.EMCMapper.addMapping(EMCMapper.java:241) ~[EMCMapper.class:?]
    at moze_intel.projecte.emc.EMCMapper.loadEmcFromOD(EMCMapper.java:409) ~[EMCMapper.class:?]
    at moze_intel.projecte.emc.EMCMapper.map(EMCMapper.java:32) ~[EMCMapper.class:?]
    at moze_intel.projecte.MozeCore.serverStarting(MozeCore.java:120) ~[MozeCore.class:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_51]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at cpw.mods.fml.common.FMLModContainer.handleModStateEvent(FMLModContainer.java:513) ~[forge-1.7.10-10.13.0.1207.jar:?]
    at sun.reflect.GeneratedMethodAccessor3.invoke(Unknown Source) ~[?:?]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.post(EventBus.java:275) ~[guava-16.0.jar:?]
    at cpw.mods.fml.common.LoadController.sendEventToModContainer(LoadController.java:208) ~[LoadController.class:?]
    at cpw.mods.fml.common.LoadController.propogateStateMessage(LoadController.java:187) ~[LoadController.class:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_51]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at com.google.common.eventbus.EventSubscriber.handleEvent(EventSubscriber.java:74) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.SynchronizedEventSubscriber.handleEvent(SynchronizedEventSubscriber.java:47) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatch(EventBus.java:322) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.dispatchQueuedEvents(EventBus.java:304) ~[guava-16.0.jar:?]
    at com.google.common.eventbus.EventBus.post(EventBus.java:275) ~[guava-16.0.jar:?]
    at cpw.mods.fml.common.LoadController.distributeStateMessage(LoadController.java:118) ~[LoadController.class:?]
    at cpw.mods.fml.common.Loader.serverStarting(Loader.java:739) [Loader.class:?]
    at cpw.mods.fml.common.FMLCommonHandler.handleServerStarting(FMLCommonHandler.java:278) [FMLCommonHandler.class:?]
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[?:1.7.0_51]
    at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[?:1.7.0_51]
    at java.lang.reflect.Method.invoke(Unknown Source) ~[?:1.7.0_51]
    at Reflector.callBoolean(Reflector.java:332) [Reflector.class:?]
    at net.minecraft.server.integrated.IntegratedServer.func_71197_b(IntegratedServer.java:161) [bsx.class:?]
    at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:387) [MinecraftServer.class:?]
    at net.minecraft.server.MinecraftServer$2.run(MinecraftServer.java:685) [?:?]

    Do you think the problem is on your or ProjectE's side?

    So I dug into the code and it is a little on their end and a little on our end...

    We have a bit of code that makes the assumption that noting will reach that bit of code with invalid metadata, as we provide a list of valid metadata to minecraft's creative mode. They on the other hand are brute force searching and not making use of the info that we provide to mc itself, and then assuming that passing any random metadata will be excepted.

    I won't be able to get this out as part of 3.16.1 as it is already built and I was just writing up the post for it prior to stopping to go and track down this issue. I guess I'll have to pull 3.16.1 and jump straight to 3.16.2 instead, so that may not make it out till tomorrow.
    Posted in: Minecraft Mods
  • 2

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    If on the off event that there is anyone who wants to port an old 1.6.4 world to 1.7.10, here is a quick hotfix for the old 3.15.6 to allow for the corrected names in 1.7.10. Just a word of warning though, though due to a glitch on my end I don't have the old strawberry code from 1.6.4 so all strawberry stuff will probably be deleted from your world.

    Also note that this build is not intended to for general use should only be used to "prep" a world for opening in 1.7.10.

    Download Update Build

    [Edit]
    Ok, so strawberries are in the build that I am working off of, but it is definitely out of date so using this for anything other than prepping a world for use in 1.7.10 is not recommended.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from Retro_King»
    Quote: "Recommended - ExtrabiomesXL Universal 3.16.0 for MC 1.7.10 - Please note that this will not work with any version of Forge higher than 1223 because of a bug in Forge. Until Forge fixes the bug you will need to use a version from 1208 to 1223."

    Very strange is... that 1230 Forge is recommended at the moment and BIOMES O' PLENTY, HIGHLANDS, NATURA, TWILIGHT FOREST, CANDYCRAFT works with it no problem. SP & SMP

    You must be doing something magical programming :o)

    Ok so the OP was a little out of date, at the time it was written forge recommended was still 1180. Forge 1224 changed how biomes are registered but still has the old way that is used in 1180 (which was recommended at the time of our releasing EbXL 3.16). The problem is that forge added in the new way of registering biomes in 1224, the old way was broken and it did not get fixed till after forge updated to 1231 and the fix that Adubbz had written 10 days ago.

    Although we could have done what mods like BoP, Thaumcraft and some others have done and update to the new way of doing things in 1224, we opted to target a version of forge that was working as intended and did not unintentionally break backwards compatibility because a single test case was missed.

    Also being that Twlight Forest's Biomes do not generate in the vanilla overworld there is no reason that it would have issues with 1224, because it never tell the vanilla world generator that it needs to spawn its biomes in the overworld only in it's own dimension.

    So all in all we aren't doing anything special, it was just a bug on forge's end and since we have historically strived for compatibility with forge recommended we built against it rather than 1224+.
    Posted in: Minecraft Mods
  • 1

    posted a message on BiblioCraft [v2.4.5]-Bookcases, armor stands, shelves, printing presses, seats, clocks, the Atlas and more! Updated 06/21/2018
    Hello!

    OK, so i'm having a bit of trouble with configuring blank books for my bookcase. Normally, the text file looks all nice, neat, and legible. Today the text file is all screwed up and looks like this... (careful with this its big.) What do I do? I can't get my mind together when i look at it.

    let me know if you need more Info

    It looks to me like the encoding on the file got messed up, or that notepad is reading the file's header/metadata incorrectly and as such displaying things improperly.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from zkol»
    What is the recommended/supported procedure to migrate an exisiting "EBXL for 1.6.4" world to 1.7.10?

    Now that 3.16 for 1.7.10 is stable I'll have to go back to 1.6.4 and do a patch to the 1.6.x build to fix the forced name changes that came in forge 1.7.

    I'll try and get it out in the next day or two unless you want to take the time and manually go through and update the NBTags for the world to make it work using a NBT editor. I can't guarantee that it will be all that easy to do though so you may want to wait till I can get that patch out to make it much simpler. With the patch you would run the world in 1.6 one last time and forge would complain about ID's changing, but would let you update the ID's, then you would save and exit and then load up the world in 1.7.10 and everything should work nice and smooth.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from crunkazcanbe»

    Well tbh I use ATG with ExtrabiomesXL . Thats the only way I can use Extrabiomes is with the pretty world gen of ATG . BTW I dont get chunk borders this way . I have not seen any yet , and I flew over 3800 blocks so far . :/

    Yeah ATG does not rely on the vanilla biome selector so it is not an issue there.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from crunkazcanbe»
    The new forge version 1231 fixed the issue with this mod for me . :)

    Yeah forge 1231 fixes the crash issue. But there is the issue with the fact that forge 1229 changed how biomes are selected so you will see chunk borders in 1231 and there is nothing that we can do about it as the change affect all worlds that have mod biomes in them.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from DarkSkript»
    What do you mean by warning? If needed I can upload elsewhere.

    It is probably nothing, but what is happening is the download is triggering Google Chrome's anti phishing/malware detection. Without taking time to verify everything myself, I can't really tell people to go and just roll with it, even if it is just a minor warning that is being given by chrome. It is nothing personal against you, but I personally don't have any prior experience with anything from you in the past, so if I am getting a warning from the download I can't in good faith recommend that users of ExtrabiomesXL take that leap of faith.
    You attempted to download something from an unfamiliar and potentially dangerous website. You should only download programs from sites you trust.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from Aeraesoria»
    forge 1229 came out... anyone tested it yet to see if extrabiomes works again with it?

    No I haven't tested 1229, and it came out after the last time that I checked the change logs. That said I looked over at the change logs and although there is a tweak to some of the code that was broken it does not touch the part that breaks desert biomes. So in a word no it does not fix the issue. Please that the bug that was fixed in 1229 was pushed by azanor1 the maker of thaumcraft because 1224, the update that broke mods like ExtabiomesXL, was not even doing what it was intended to do in the first place. That particular part is now working but it is still not initializing the "desert biome" list object so that is not working.

    If you look at the change forge log, then if it is fixed it will say something like:

    ixed desert list initialization. Fixes #1447

    OR

    nitialize desert biomes.


    Both are proposed, although looking at the proposed code changes the second one may be more correct, the both solve the NPE problem but the first one may not be registering vanilla biomes for generation, meaning that you may end up with ugly chunk borders.
    Posted in: Minecraft Mods
  • 1

    posted a message on BiblioCraft [v2.4.5]-Bookcases, armor stands, shelves, printing presses, seats, clocks, the Atlas and more! Updated 06/21/2018
    For bibliowoods extrabiomes xl addon it does not see the extrabiomes wood types. All it shows is fire. I am running Minecraft 1.7.10 and have tried various versions of forge from the recommended for this mod and up to see if this would fix it and it doesn't. I hope that this issue can be fixed in the near future.

    The issue here is that ExtrabiomesXL 3.16.a17 introduced a bug when it was being ported to 1.7.10 where the modid accidentally had it's capitalization changed. I believe that Nuchaz updated the Bibliowoods EbXL addon to support this unintended bug, and when I as one of the Extrabiomes developers changed things back on our end it allowed for this to happen as the dependencies listing of the addon is now configured to make sure it load after the the non capitalized version of ExtrabiomeXL.

    After looking into this tonight, I have confirmed that this is the cause of the issue, and atleast for myself a temp fix is to manually trick forge into ensuring that ExtrabbiomesXL loads first, by renaming it such that when the contents of the mods folder is sorted by name ExtrabiomesXL is listed first. This isn't guaranteed to work on all systems, but it should do till Nuchaz can put out a patched version.

    Quote from candy49997»
    Help! When I open my world, I get this crash report: http://pastebin.com/NbF80E2k. I tried to update forge, Bibliowoods, and I am using the latest version of Bibliocraft.

    Not this does not appear to be tied to using a broken version of forge, rather slightly more strangely the game is trying to treat an armor stand as if it is a bookcase. I don't really know how that is possible as I haven't really done all that much work with tile entities as of yet, but it sounds like you might have had something corrupted in your world.
    Quote from delax000»
    Think that was fixed in the next build...

    Several big mods seem to have updated to 1224 (Thaumcraft and Biomes O'Plenty off top of my head), so I take that as a recommendation.

    It was actually MinecraftForge 1224 that broke things for biome mods. 1224 was intended to "improve" how vanilla handled the chance that biomes could spawn in a super biomes, but it has a small bug in that means that mods are not able to register biomes classified as "desert". (IE if they are both warm and dry.) I don't believe that Thaumcraft adds any of such biomes, so it is not affected by the bug, and it is able to take advantage of the finer grain of control that MinecraftForge 1224 offers when setting the chance that a biome will spawn.

    Biomes O' Pleanty's "bug fix", if you want to call it that, was to test to see if the bug existed, and if the bug existed then it would skip registering biomes with the biome manager. I don't know if BoP uses the vanilla biome manager for it's own world type, but at a minimum it means that in default world types and possibly even their own world type their "desert" like biomes will not spawn at all, leading to those ugly chunk borders that you get when you go exploring and have changed the biomes that are generated in your world. Doubly worse is that it also has effect that if do explore new terrain that generates such chunk borders, once the bug in MinecraftForge is fixed, you will again have the possibility to generate the ugly chunk borders all without any mods truly adding or removing any biomes.
    Posted in: Minecraft Mods
  • 1

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    In the event that anyone is wondering, no forge 1226 is not compatiable with extrabiomes as it does not fix the issue with desert (warm/dry) biomes not being able to be registered with MC for generation and fixes another graphics bug with some intel graphics cards.
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    As mentioned in the release, forge 1224 is broken and should not be used. It has a bug in it that is causing this, and although BoP has a "work-a-round" in it's latest release, it is not something that that we as a dev team for EbXL consider a viable solution. Basically BoP's solution it to not register their biomes that qualify as warm dry, which means that if you as the end user updates to it then if you have any partially generated warm and dry biomes and you generate more then you will get chunk borders. Not only that but when the bug in forge get's fixed and you generate more of the warm and dry biomes then you will once more have chunk border errors.

    Scott and I couldn't justify creating our own solution as another mod could possibly run before we tried to apply our own fix in our code, so we just opted to not support forge 1224 as it breaks backwards compatibility, and our aim it to be able to run on forge recommended if at all possible, as it is there is a reason that it is recommended. EbXL is able to run on all versions of forge from forge recommended (1180) up to 1223, as they don't break backwards compatibility for anything that we use.

    [EDIT]
    And sniped by HanFox
    Posted in: Minecraft Mods
  • 0

    posted a message on ExtrabiomesXL Universal 3.16.3 for MC 1.7.10
    Quote from Chocohead»
    Noticed something while updating the EBXL textures for the FTB wiki, Bald Cypress fences, fence gates and doors are called Baldcypress fence/gate/door, while the wood, plank, stair and slab are all called Bald Cypress wood/plank/slab/stairs.

    Bugger, I missed that. Both spellings are correct, it is just depends on where you look things up.

    Much like color and colour. It all depends on the source that you look it up in, and this was a case of it being written one way in one place. From a file/unlocalized naming convention it makes sense to write it without the space or hyphen, but it initially made it in with the space...
    Posted in: Minecraft Mods
  • To post a comment, please or register a new account.