Search results

I'm also pushing the vendor mod to disabled by default .. due to creative crash issues and, it's more or less something you may want in multiplayer only. No need for it to be enabled by default, it's there if you need it though. Good way to avoid that crash, is not to spawn it in via creative...

A few quick things .. Firstly, it is *possible* that a shift from a beta to release in 1.5.2 will break worlds, and in a spectacular nature. Yes, there are important reasons for this, but discussions behind the scenes will continue and we will make the best decision we can. The main reason for...

Working for me (no optifine).

Just a quick heads up .. am suffering a little with lack of sleep and a headcold .. but have been documenting and testing most the day. Already up to around 23 things to address, from config tweaks to specific mod version things. I'm going to keep pushing on through for a day or two, gather as...

Tinkers Construct requires some tool parts (metal ones) to be smelted. This can be changed in configs, but it's how the mod is intended to be.

It is true. I am Max Headroom.

You can take a 0.7 release, enable BoP, and reduce the number of biomes. Solved.

Just putting this out there. Not in a Minecraft sense, but in a Real World sense. If you implement something in Beta, and expect it to work in Production, you're a bloody idiot. I say this as a guy who has been working in IT for 30 years.

There is one hurdle that has yet to be finally assessed on this. Please, please note .. we call these betas FOR A REASON. They are not here for continuation into a production release. We will always *try* but there are more than a few factors why this won't be the case. As *actual*...

Okay, normally, a week must pass. This makes more than enough sense .. there's so many issues, mods and people who use these mods and packs .. the shift from 'beta pack' to 'production pack' needs to take the time needed. It's as simple as that.

It shouldn't take too long. I'm confident everything is done right, it's up to someone else to confirm it and then push it out if it's good. That's it. I've left messages with those who can, so now we allow them to wake up and take it from there.

Okay, so a quick update. I've revised all mods for the packs, tested, shuffled, test again, found some breaking issues, Myrathi in swung like FREAKING BATMAN and fixed code, tested more, and it's stable enough for a beta release. Server and client packs have been uploaded, and now we wait for...

Soon.

Fixed. Shut up. :P

Initial build is .. working .. but plenty of issues in console to address. As has been said before, here's my spreadsheet on the pack, version numbers, links, etc .. https://docs.google.com/spreadsheet/ccc?key=0AoWBpEX_gP1AdEZNb0VlRkc5M1FHaUhWRkhWaHRyU0E&usp=sharing I'll be chatting on and...

Just to be clear, when I say 'previous worlds' .. I mean from previous 1.5.2 beta packs. edit: Beaten to the punch by Tyrellan :)

So I herd u liek mudkipz!!! As I tweeted above, "things happened" but today I will be elbow deep in a 0.7 release. Am now *aiming* for previous worlds to be brought across. Wish me luck and strong coffee .. going to be a busy day.

Define "changed it up". From my view, the old vision was 1.4.7 packs were it and this was to remain until the undiscovered lands that it 1.6. This changed by *adding* in 1.5.2 packs, mainly due to the want of the public. Key word here is, added. 1.4.7 packs will remain in 1.6 land, and...

+9001. The 1.5.2 pack will shift from private to public (and supported) once everything settles. There is no movement to remove the 1.4.7 packs, as far as I know.

Yeah, the idea that a 1.4.7 pack will not exist because of 1.5.2 is .. well .. let's just say, unrealistic. It's there. It's done. Stick a fork in it. 1.5.2 will be as awesome as we and the mod authors can, and have, provided us. And honestly, 1.6 is going to be yet another step up and...