The state of 1.6 Modpacks

Status
Not open for further replies.

mk16

New Member
Jul 29, 2019
347
0
0
anyone else unable to update to 1.1.2 on monster? like it will do all the downloading pop up but never launch.

deleted anything related to ftb and reinstalled, seems to have worked.
 
Last edited:

Hambeau

Over-Achiever
Jul 24, 2013
2,598
1,531
213
anyone else unable to update to 1.1.2 on monster? like it will do all the downloading pop up but never launch.

deleted anything related to ftb and reinstalled, seems to have worked.

See what happens when you poke the bear with a stick? :D
 

Azagal73

New Member
Jul 29, 2019
34
0
0
Tech2 will be out today

Tech 2 won't update since the modpacks.xml file is wrong for it. there is a comma (,) instead of semi-colon (;) separating the 1.1.7 and 1.1.6 versions in the file.. the launcher thinks the version is 1.1.7,1.1.6

You can get around it by editing the modpacks.xml locally, setting it to read only and then starting the launcher.
 

cricketnath

New Member
Jul 29, 2019
2
0
0
Now that RL is calming down for me and I will be getting much much more time to sit down and do what I love (game dev,) it is also time for me to announce the end of 1.6 FTB Official packs. In the next week, I will be releasing an update for all 1.6 FTB Official packs and then having a time of 1 week after for any additional bug fixes mod authors want to put up for us. After that, all 1.6 FTB Official Packs will be frozen.

As of now, I am already looking into 1.7 development as well as talking to a few people about additional tools for modpack creators. I am hoping what we are planning for you meets to your expectations and raises the bar for modpacks overall. iF you are anxious for what is to come, well, so are we.




Notice
1.7 packs are not planned to be released for a few months,
please do not spam the forums asking for ETAs or you will receive a timeout.
~Eya
I have some offers to make i am going to make my own minecraft server with all new mods and some of my mods i am making is the ultimatecraft and in the ultimatecraft it is mechines like ultimate blast compressor and more and i will like you to help me please thenk you a lot if you can help me
 

Jadedcat

New Member
Jul 29, 2019
2,615
3
0
  • Like
Reactions: aTeLe

aTeLe

New Member
Jul 29, 2019
68
0
0
The CC update broke a lot of cross mod compatibility. And the mods will not be updating to fix it in 1.6 when they can just fix it in 1.7.
Thank you for all of your answers. I will now make a new Techworld2 Server.
I hope these conflicts aren't bad:
Code:
2014-06-02 00:06:09 [Information] [simplyjetpacks] Registering armor: jetpackTier1
2014-06-02 00:06:09 [Information] [STDOUT] CONFLICT @ 17751 item slot already occupied by erogenousbeef.bigreactors.common.item.ItemBRBucket@650816a2 while adding tonius.simplyjetpacks.item.ItemSJJetpackArmored@7606197f
2014-06-02 00:06:09 [Information] [fml.ItemTracker] The mod simplyjetpacks is overwriting existing item at 18007 (erogenousbeef.bigreactors.common.item.ItemBRBucket from BigReactors) with tonius.simplyjetpacks.item.ItemSJJetpackArmored
2014-06-02 00:06:09 [Fein] [fml.ItemTracker] Adding item tonius.simplyjetpacks.item.ItemSJJetpackArmored(18007) owned by simplyjetpacks
2014-06-02 00:06:09 [Information] [simplyjetpacks] Registering armor: jetpackArmoredTier1
2014-06-02 00:06:09 [Fein] [fml.ItemTracker] Adding item tonius.simplyjetpacks.item.ItemSJJetpack(18002) owned by simplyjetpacks
2014-06-02 00:06:09 [Information] [simplyjetpacks] Registering armor: jetpackTier2
2014-06-02 00:06:09 [Information] [STDOUT] CONFLICT @ 17752 item slot already occupied by erogenousbeef.bigreactors.common.item.ItemBRBucket@4d35124a while adding tonius.simplyjetpacks.item.ItemSJJetpackArmored@5743dfdf
2014-06-02 00:06:09 [Information] [fml.ItemTracker] The mod simplyjetpacks is overwriting existing item at 18008 (erogenousbeef.bigreactors.common.item.ItemBRBucket from BigReactors) with tonius.simplyjetpacks.item.ItemSJJetpackArmored
2014-06-02 00:06:09 [Fein] [fml.ItemTracker] Adding item tonius.simplyjetpacks.item.ItemSJJetpackArmored(18008) owned by simplyjetpacks
 

Frontrider

New Member
Jul 29, 2019
319
0
0
Thank you for all of your answers. I will now make a new Techworld2 Server.
I hope these conflicts aren't bad:
Code:
2014-06-02 00:06:09 [Information] [simplyjetpacks] Registering armor: jetpackTier1
2014-06-02 00:06:09 [Information] [STDOUT] CONFLICT @ 17751 item slot already occupied by erogenousbeef.bigreactors.common.item.ItemBRBucket@650816a2 while adding tonius.simplyjetpacks.item.ItemSJJetpackArmored@7606197f
2014-06-02 00:06:09 [Information] [fml.ItemTracker] The mod simplyjetpacks is overwriting existing item at 18007 (erogenousbeef.bigreactors.common.item.ItemBRBucket from BigReactors) with tonius.simplyjetpacks.item.ItemSJJetpackArmored
2014-06-02 00:06:09 [Fein] [fml.ItemTracker] Adding item tonius.simplyjetpacks.item.ItemSJJetpackArmored(18007) owned by simplyjetpacks
2014-06-02 00:06:09 [Information] [simplyjetpacks] Registering armor: jetpackArmoredTier1
2014-06-02 00:06:09 [Fein] [fml.ItemTracker] Adding item tonius.simplyjetpacks.item.ItemSJJetpack(18002) owned by simplyjetpacks
2014-06-02 00:06:09 [Information] [simplyjetpacks] Registering armor: jetpackTier2
2014-06-02 00:06:09 [Information] [STDOUT] CONFLICT @ 17752 item slot already occupied by erogenousbeef.bigreactors.common.item.ItemBRBucket@4d35124a while adding tonius.simplyjetpacks.item.ItemSJJetpackArmored@5743dfdf
2014-06-02 00:06:09 [Information] [fml.ItemTracker] The mod simplyjetpacks is overwriting existing item at 18008 (erogenousbeef.bigreactors.common.item.ItemBRBucket from BigReactors) with tonius.simplyjetpacks.item.ItemSJJetpackArmored
2014-06-02 00:06:09 [Fein] [fml.ItemTracker] Adding item tonius.simplyjetpacks.item.ItemSJJetpackArmored(18008) owned by simplyjetpacks

If the big reactors buckets not missing, then theres no problem.
 

Arkie

New Member
Jul 29, 2019
2
0
0
Hi, i'm unable to update to the 1.1.2 monster pack. I'm only seeing version 1.1.1 in the launcher. Already tried deleted all the FTB stuff but it didn't work.
anyone got a fix?
 
Status
Not open for further replies.