Loader

MostaRica, please use the tracker for this kind of thing in future - here's another guy with the same problem as you on the tracker, follow the same advice as I gave there and post a new issue on it if that doesn't fix it. http://forums.technicpack.net/tracker/issue-1149-tinkersconstruct-crash/

Can you reword that? Perhaps say what you're trying to achieve so people can offer suggestions on how they'd do it? I'm not really sure what you're asking here.

Ok, go to the .technic/modpack folder and remove the attack of the b-team folder manually (back up your saves first!). In future, please post this kind of thing up on the tracker.

Ok, please post up a crash-log on the tracker (links for where to get that are in my sig), I'll need at least the server log but if you can get his client log too that'd be great.

Your best bet is MCEdit, backup the world, open it in MCEdit and see if you can see what's going on. If a section looks bad, cut out that small bit, if nothing looks bad, save in MCEdit and reopen in minecraft, if the chunk still looks broken (usually chunk corruption looks like a kind of spiral staircase of random blocks) then there's not a lot you can do except restore an earlier backup (the underlying data is damaged in that case). Any idea what triggered it? I've seen this happen if you use the infinite power bug (interaction between GC and TE power) but not from anything else on B-Team yet. If you're not sure what triggered it, can you run me through a list of things you had in the chunk?

Please post up your launcher log on the tracker (links for both are in my sig), that should give the info we need to help.

That's strange, thanks for coming back and letting us know - this is the first time I've seen problems like this with openJDK 1.7 (1.6 obviously doesn't work). I'll bear it in mind for future issues.

It's a problem connecting to minecraft.net - that connection actually happens when you run the launcher (and may have timed out), so quit the launcher all the way out, reopen it and run b-team as usual.

It seems to be a bug with the sledge, it drops the iron like usual for blockbreaking but because it's broken the top bit of a door the door still drops - diamond version means it'll do this 80% of the time (the rest of the time it'll drop just the door). The sledge also only sorta takes durability loss (one of them seems to have done, but the other two in this picture haven't taken any - I'm not sure why one did and they all seem to have stopped taking damage now). You can build a machine like this (this is me testing it just now) but I've gotta be honest - I never really had a problem with iron. (Machines on top using the sledge, machines on bottom receiving and replacing doors, hoppers to catch the junk and seal it so it doesn't go everywhere)

Please get a crash report and post it up on the issue tracker (links to help with both are in my sig).

You can add (and have to add) specific info to make protection work with a lot of items. A few have to be banned to be stopped completely because they don't respect world-protect because they interact with the world differently to standard, but anything that's not ranged can be dealt with guaranteed (you can control if an item can be used in protected areas at all, so only ranged stuff where there could be a block-type interaction can bypass that kind of thing - even then only if the explosion/interaction is unusual).

There's an issue tracker specifically for launcher problems here; http://forums.technicpack.net/tracker/project-1-technic-launcher/ Please look at the guidelines for posting there linked in my sig then put some info up there so people can help you.

In worldofdinos.cfg, get this bit; general { # A comma-separated list of integer Biome IDs where dinos should spawn. S:dinoBiomeIdList=201,202,203,204,205,206,207,208,209 } And remove all of those biome ID numbers so it looks like; general { # A comma-separated list of integer Biome IDs where dinos should spawn. S:dinoBiomeIdList= } That'll not tear it out of the fossils or anything like that - it'll just stop them spawning automatically in tropicraft (people can still clone them).

(I think that's DS's humorous way of saying you in fact need Java 7 or 8, in case you missed the joke)

Always be prepared as you hand them the last stuff - sometimes you may be in for a surprise...

Ok, maybe I was wrong - put up your logs (as many as you have, crashlogs if it makes them when it drops out of the mojang screen but at least launcher logs - there should be both client and launcher) on the tracker for your pack. Links for how to get the logs and guidelines for posting on the tracker are in my sig.

This way does work, they do check here, but for this pack in particular it'll be what the B-Team asks them for. You're probably better off asking genericB on facebook in all honesty.

I was thinking of the Rancher, but those work too if you keep your pen a straight line and I guess it has the advantage of not needing power.

You need to take her something... something that helps you see the future.

Ok, it's probably removed your symlinks for the old (Java 6) system default version, if you can run using terminal though then you've sucessfully installed java 7 in an OS that specifically doesn't support it, congrats To look at all the default stuff for java now just type in Java Preferences in spotlight, you should be able to click (checkbox) to turn different versions on and off and drag things up and down to change the order of preference. Did making sure the smeltery was all within the chunk make any difference?

This was for when you've already got the berries and want to convert them to mob essence without involving you - there's a video tutorial around here somewhere of how to make an infinite metal farm (using a different kind of berry) which can talk you through that using autonomous activators, or you can just use the MFR harvester (it needs power but can cover a much larger area and I'm lazy ).

Solar panels or bug exploiting, at the moment, if you want a system similar to before. You can do any number of tree-farm>charcoal>steam dynamo setups or mob essence>reactant dynamo setups, but if you want a solution without spawning trees or mobs then the solar panels. Edit: Beat me to it

There's a couple things, but like freakachu said there's not a lot you can really do, almost nothing is actually designed to work on that kind of system anymore. Firstly, Mapwriter uses a lot of processing power and disk activity on a client - this can cause freezes like you're describing so if your mod has that I'd remove it to see if that helps. Secondly, you can run the server software rather than singleplayer - that'll let the server use 1GB RAM and the client connecting to use another 1GB RAM (connect to 127.0.0.1 to log into a local server). This is almost as good in some ways as being able to allocate 2GB, but in others it isn't (you'll still get crashes from out of memory on the client from time to time). It's certainly an improvement on trying to do it all in the one instance of java, though.

If you didn't find anything in the common solutions thread that helped then please post a launcher log up on the tracker (link to help with both are in my sig).

It is, isn't it? At least I think so. Here's the board rules; '?do=embed' frameborder='0' data-embedContent>> Here's where you should've posted; http://forums.technicpack.net/tracker/project-4-attack-of-the-b-team/ Here's the rules for posting there; '?do=embed' frameborder='0' data-embedContent>> Here's what you should've posted; http://forums.technicpack.net/tracker/issue-925-bug-report-template/ Many of the people who help here are doing it voluntarily, and if someone doesn't appear to have taken the time to read some stuff and they think they might be wasting their time, they often won't bother - it's not personal, there's just other people to help. I get that you're frustrated, but when you didn't get a response you could've tried to find if there was a reason why - being snarky and making no attempt to find out if you did this right is not a good way to make volunteers think that you're worth their time. That said, if you post on the tracker with the proper info I'm sure someone will still help you - you're just making it difficult for people right now.