Search results

nice, what about those of us that have 1.5.2 private packs already updated and running as 1.6.4? Any ETA on when we will be able to resubmit them as 1.6.4 packs?

That would fall under "Well that is if the pack maker knows what they are doing and does not introduce ID conflicts and etc." Most of the packs on FTB are not put out by FTB, only approved by them, so the same applies to them as well.

lol, almost every 1.6.4 pack has to change constantly as the mods are updating constantly. However, this has little effect on players except for updating frequently. Well that is if the pack maker knows what they are doing and does not introduce ID conflicts and etc.

Strangely enough not all of us use twitter, and FTB does not list a twitter link on the forums. However, thankfully Google is more user friendly: "Turns out with some help from some very good friends. We have 1.6.4 packs running now on the original launcher." Wow, really, how many of us have...

Just a few of the packs on FTB are put out by FTB, the rest are public packs that are popular enough to meet the requirements to be listed there makers, and the rest are private packs put out by small server for their sole use. Really there is no real difference except that AtLauncher has...

So the community suffers because FTB can't staff its forums adequately? Sounds more like poor forum management more than anything else. There may be 230 private packs, but there is only 36 threads listed for them. As promotion threads for ultimate, unleashed, etc are outside of the whole...

why not just verify if the pack is on the FTB launcher as 1.5.2 as was the whole point of the cut off date...

but everything that came out afterward 1 July must be a 1.6 pack then, by that logic? And random in this case, means based on an arbitrarily selected date, having to do nothing with whether the pack was hosted through the FTB launcher as a 1.5.2 pack. I have read the whole thread, I was one of...

So again the answer is a randomly selected date...just one that would effect more packs.

yet it was random, as for example my pack was hosted through FTB for quite some time, and had quite a few updates as 1.5.2 as well. and "1.6.4 came out on 1 July Mods were not updating in large amounts until August Grace period of one month added. Result: Posts after 1 September advertising...

Um, no... You obviously do not know the conversation. Slowpoke stated that a system will be in place to update the current 1.5.2 private pack to 1.6.4. However, all packs that were made after the randomly selected cutoff date have had their threads deleted and their packs removed. Hence my...

It is not complaining, this is a discussion. It is not a matter of liking an option or not, bad advice that goes against what a Moderated has stated, in this thread no less, is still bad advice.

Have you read this thread? Because you telling me to recreate a post that has been delete would go against the "wack-a-mole" and "random cutoff date" ruling. Are you trying to get people banned from the forums by giving out bad advice?

Nope not really except that all the private packs that did not meet the random cutoff date, have no way to update to the new system... well thanks for that.

I find the whole thing funny by this point in time.

oh, sorry I missed three months by a few weeks, .That was the thread creation time, not the period of time the pack has been around as it was tested for weeks before the thread was created. Second that has nothing to do with "New servers posted in the past three months that have basically been...

"Existing servers previously using FTB packs that have updated to their own packs temporarily while holding for the launcher update have been given some grace." Obviously this is not true, as my pack and thread was created more than three months ago and is now gone. It is obvious that FTB has...

smae here, I would like to know what has happened to my thread as well.

nvm, I am an idiot it seems. I forgot to update it on the live server, though I did update it on the test server. Updating it to the correct version fixed the error message surprisingly enough. :).

Nope, I do 2-3 mod pack updates for the server a week, so all of the mods are current, as MFR only updates once every week or two, all of the mods that use its API are up to date. I have not had any crashes, I was just curious as it is stating that Dartpatch is using old API and may cause crashes.