Jump to content

radfast

Members
  • Posts

    5
  • Joined

  • Last visited

Posts posted by radfast

  1. If that is your agenda, consider my comment void.

    Looking at the (probably vastly outdated) GC build used in Tekkit, I noticed quite a few quirks and issues that mostly prohibited automation (see for reference the extreme measures >some users took to get it automated at all). This gave the overall impression that GC authors don't care overly much if their stuff works together with anybody else's mods or not. This was probably a false impression, given your statement. With the growing number of intricate tech mods accumulating in modpacks, it's essential that these mods work together to a certain degree and integrate into the greater whole. If you are committed to that, I have nothing to criticise.

     

    :)

     

    We are absolutely committed to that in GC3, certainly since I joined the team which was March 2014.  Personally I love to automate when I play Minecraft, and although these days I mostly code instead of playing, I think it's very important that everything works in the way that players would expect.

  2. If you love Galacticraft to be in modpacks, you should look into making your machines cooperate better with other mods. They cannot be automated properly, and I think your ore processing chain doesn't fit into the usual modpack gameplay at all. Take a look at CoFH Core and other essential factory mods, and try to be more of a teamplayer.

     

    Of course these are not issues that can be addressed quickly, but you might take note of them going forward.

     

    I applaud the fixes in build 1096, though, and I'm sure it will be included once anybody finds time to actually work on Tekkit again.

     

    Thanks for pointers on those issues of concern.  We have made some machine automation improvements in GC3, but I will review this again before the next GC3 update.

     

    Please explain what is meant by "ore processing chain doesn't fit into the usual modpack gameplay at all", I don't understand that one?  These days Galacticraft ores are all Oredict compatible (unfortunately it was not the case before around version 2.0.10) and the three standard metals (copper, tin, aluminum) should interact fully with other mods.  In GC3 we have also added intelligent metal block recipes, so 9 IC2 copper ingots will make an IC2 copper block, but 9 Galacticraft copper ingots will make a Galacticraft copper block.  In GC3 there is also a config option to set ores from any other mods to be added to the worldgen on Moon + Mars.

     

    If there is a further thing which will help integration in 1.7.10 modpacks, we will happily include it but I need specifics please.

     

    Our intention is that GC3 should integrate smoothly with IC2, Mekanism, Thermal Expansion, Buildcraft, or EnderIO.  (There are current issues with EnderIO2.2 because we built Galacticraft for compatibility with EnderIO2.0 not EnderIO2.2, but that will be fixed soon.)

  3. Hi guys, as you may know I'm the co-developer of Galacticraft working jointly with micdoodle8.

     

    For the final 1.6.4 pack, we recommend version 2.0.14.1096 of Galacticraft.  Not version 2.0.14.1084.

     

    Build #1096 has:

     

    * fixed three bugs causing rare crashes in #1084

    * corrected the Buildcraft and Thermal Expansion energy conversion ratios, in a default Galacticraft config file

    * performance increase

    * other small fixes

     

    It would be good if the modpack makers would take note of this!  Also it would be good to add the block IDs of glass blocks from other mods - for example Hardened Glass - to the Galacticraft config for Sealable Block IDs.

     

    Feel free to get in touch if you have any additional questions or requests.  We love the Tekkit modpack and are happy to help resolve any issues if the modpack makers want to get in touch.  (Best way is to PM me here or on http://forum.micdoodle8.com/)

  4. This power multiplication bug between aluminium wire and TE is fixed in Galacticraft builds 1024 and later.

    We maintain a beautiful changelog at http://ci.micdoodle8.com/job/Galacticraft/changes

    so that players like you can see what is being fixed.

    If you want to have all the most recent updates in Attack of the B Team then ask the modpack makers to update to the latest Galacticraft version which is 2.0.13.

    NOTE: generally speaking, whatever build is in the modpack, server owners can safely update server-side only to the latest build as long as it has the same Galacticraft minor version number. Example: if the modpack has 2.0.12.1026, the server can actually run 2.0.12.1059 to get the latest bugfixes. Any Galacticraft 2.0.12 client should have no problem connecting to a server running 2.0.12.1059 and the players will not even know the build number is different. Hope you server owner guys understood this.

    And @Loader? Lol at trying to fix it in the source code yourself instead of looking at the changelog, coming to the Galacticraft forum to ask, or maybe opening an issue about this on Github.

    cheers all

    radfast

    (Galacticraft co-dev)

×
×
  • Create New...