Search results

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
  1. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    Hopefully within the next month. It is being worked on but it takes time. Have you finished the pack?
  2. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    That would be my advice. 1.2.0 will require a full reset of both map and quests
  3. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    Thanks for your feedback, we have worked hard to make the pack enjoyable. That seems to be a shame that it is happening. I will add it to our tracker so we can reproduce it, then pass onto Pam if needed Thanks for letting me know, I will pass that on
  4. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    Probably not as that is a feature of the deep dark. Not something we control
  5. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    We do not know exactly how far. Your best bet is at least as far as the furthest hidden cubes (about 1000 blocks). For 1.2 it will be a complete reset with a new map (ores all fixed) and a pretty major change to the quest book
  6. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    There is currently none in the map. For now you must explore new chunks to get it. This is fixed in 1.2.0
  7. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    The issue with the progressive automation machines is a bug with the mod. It is fixed in newer versions and will be fixed in the next update. If you wanted you could manually upgrade to any version after 1.6.19. Sorry for not pointing this out sooner
  8. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    This is odd. Could I please ask what version you are on? And could I please have a couple of screenshots of this happening. Thanks
  9. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    Thanks for reporting this, I will talk to the devs about what we can do
  10. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    What version are you playing on?
  11. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    From what you have said I think you need to update to 1.1.14 Then place your pickaxe in the crafting inventory and it should be fixed
  12. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    You should be able to level up the pickaxe through use and then add new parts till you can mine everything: Wood < Flint < Copper < Iron < Bronze < Obsidian < Ardite < Cobalt < Manyullyn
  13. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    That's part of our intentional lighting systemn
  14. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    This command should help you: /cofh tpx <hisusername> @a I will get this issue fixed for the next update
  15. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    1.1.13 had the incorrect lighting system (Accidentally removed from 1.1.12). Hence 1.1.14 fixed the lighting to how we wanted it. That's why your torches have changed. Sorry
  16. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    What version of the pack did you originally light your base up in? There have been some changes to lighting over a few versions, and that may explain it
  17. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    Uhh whoops. #BlameJohnny :P We will get this fixed for the next update
  18. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    There should be a solution in NEI. Otherwise the next map update fixes it
  19. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    Go to video settings and change your GUI settings. Does that work?
  20. AKTheKnight

    [1.7.10 | Unlisted] Obscurity - Jampacked 2 Winner

    A couple of people have reported this. I think it is fixed in version 1.1.14 that is being uploaded now