Search results

Well, there is one more thing you can do that's a guaranteed fix: run %appdata% and you'll see a folder called 'ftblauncher' - delete it and reinstall FTB. Before you reinstall, I'd probably want to go to where FTB is installed - and delete 152ngt and 152wgt manually just to make sure it's dead.

Oh, I think I see what you're saying. Try hitting options; and click 'force update'; but make sure the pulldown says 0.8 before you do it. EDIT: And to delete the pack; click on private packs - and type in 152ngt (or 152wgt) and then remove.

Not sure where you came up with that impression - the list just shows the recommended version; not what you have installed. If you have 0.8 listed instead of recommended - then you have 0.8 installed; it doesn't matter what the list says.

You have to change it from recommended to 0.8

Not trying to be rude: but it's been said a billion times: Xycraft is not - will not be - available for 1.5.2. The developer is waiting for 1.6

It is however, a discussion on this mod pack. And, since MPS has already come up...

@Wyld: The MPS (I assume peripherals - they aren't in 0.7) mod has a bug. There's little glasses on the helmet (it's new, looks like shades) - causes minecraft to crash everytime you hover over it. EDIT: Also, if anyone happens to know what they are - I'm going to disable them if I can figure...

type 'o' from your inventory. it was probably accidently disabled.

They're there. See if you have it in utility or recipe mode.

0.8 just crashed on me using the tinkerer for the Powered Armor. :( Crash is in the support directory. Happen to know if the flint & steel uses iron or steel? That really pissed me off with GT.

You can't convert a 1.4.7 world to a 1.5.2 world without a ton of problems from the mods. (I mean you can try; but guaranteed half of it is going to be broken....) Your best bet is to just redo the world if you're upgrading versions. EDIT: To clarify... :)

Coincidence is coincidence.

Who's default is also M.

Any chance you'll add EBXL into the loop (even if it's disabled). We keep getting game exits (the game suddenly just shuts down; no server crash) and the only thing different is we added EBXL (which I prefer over BOP hands down...) :) And I hope you feel better quick!

Sounds good - but sounds like I should also call it a night and get it in the morning. :) Awesome job tonight :)

Even tho I'm sure there's no way to know, do you have an idea of how long that part will take? (ie. we're not going to see something for a few more hours? it'll be just a few minutes? etc, etc...) And thanks Wyld (I missed the black dynamite ... sounds like fun. I think...) :)

Oh, my bad! I would assume it's default (ie. no biomes disabled) - it's just got different id's and such than normal. :)

Wyld's said BOP will be disabled from the start. But enabling it easy: You simply click 'edit pack' (after it's downloaded; so you'll update - then exit to enable the mod) - moving it from disabled to enabled list; and then again launching the pack. It'll have the config files all ready there...

Well then you're pretty much set :) Except for a few additional mods. :) True, that's why I really like that Soartex pack. Being able to chose what mods you want from a list (with version numbers) and such is pretty damn awesome. :)

I would start piecing it together now. :) The only bad thing with Sphax (and it's why I switched to Soartex) is he doesn't cover all the mods FTB uses...