Loader

Ah, ok - how much RAM is being assigned to it in the launcher, and how much is showing in game (top right of the F3 debug screen).

Sorry Daniel, that came out a bit more sarcastically than I'd intended - I honestly thought you'd posted in the wrong place and was trying to let you know (so you could post again in the intended thread). You have nothing to apologize for.

You know how you connect to an ip address and it might be something like 192.168.1.10 for another computer on LAN? Well, you can connect to 127.0.0.1 instead and it'll connect directly to your own computer (a 'local loopback'). The other way is to use the word localhost instead of a hostname (like mc.xeongaming.co.uk to take an example from the first result in the server section right now). Both of these do the same thing, connect back to your own computer - if it's running the server then it'll just connect to it, no using hamachi/network/router/internet or anything because it's all running on the same computer and it doesn't need to. It's for situations like the above where a player wants to use a client on the same machine that's running the server.

For future people reading this thread, this can happen on any crash in a singleplayer world. Daniels solution should work - the world isn't gone or deleted, it's simply removed from the list. Creating a 'new' world with the same name and settings will detect the previous world files and use those. MCEdit is another alternative (simply open the world and save it, that should be enough to fix the corruption). To avoid this completely, run a local server and connect to that. It's also worth noting this isn't restricted to the B-Team modpack, it's something that can happen with crashes in Minecraft in any modpack, and this solution will work for those, too.

Just for clarity this is fairly rare, but B-Team is one of the few mod packs around at the moment in which all the mods are currently actively developed, so it's not impossible. Was there something specific from a later version that you wanted? There's probably an analogue in the B-Team already.

XP has a security feature that Hamachi works around without telling you - it needs to install a special passthrough driver to allow connections to flow freely into and out of your network (Vista and on don't do this that way, Win2000 and back wouldn't have needed it). It's not quite an exception because what's essentially happening there is Hamachi is acting as a proxy - all connections are going 'out' to the Hamachi adapter (outside what your computer sees as its internal network, but technically still on your computer) then coming back 'in', so it seems to be an acceptable request. I wondered about mentioning proxies being the only exception and I figured "Nah, it'll just complicate things needlessly", of course you'd have encountered that exact situation that's caused confusion, just my luck. EDIT: A proxy is just a machine that you pass your own requests to - so if you have a proxy at proxy.com (not a real thing), and you want to go to Google, you connect to the proxy and make the request. The proxy actually does the request to Google (so Google sees the request coming from Proxy.com, not from you). Once the proxy gets a response from Google, it sends it back to you. In your situation Hamachi was the 'proxy', your other network cards are 'you'. Because the proxy can access your computer from the outside (it's on the internet as far as your computer is concerned whether that's true or not), using the Hamachi local IP works fine. This is an XP workaround as adapters aren't allowed to communicate with one another except in a few specific ways by default.

Every time I think of something I'm pretty sure would be a good idea to add, you've already added it. This is exactly why I almost never ask for anything! (sorry I missed that) They should spawn in vanilla biomes as usual - this greatly reduces the number of spawns though (there has to be a village spawn and it has to line up with a vanilla chunk).

Direct connecting to 127.0.0.1 won't use the modem, internet or even network. Minecraft doesn't use any form of Peer to Peer networking, it's pure client-server architecture (even in singleplayer it's connecting to an internal server on 127.0.0.1). Because it's client-server you need some form of port forwarding for port 25565 across the internet - the DMZ is one way of doing that (it just passes all the port requests to a single IP), Hamachi is another way to do that (it's basically a series of DMZs pointed to the hamachi ip addresses if you want to look at it like that). You won't be able to connect or ping your own internet (WAN) IP address or hamachi IP from your own computer, use the local loopback (127.0.0.1) for that. You may be able to ping your own local IP (192.168.?.? probably) depending on how your network is configured. If the firewall is blocking connections on 25565 and changing that isn't an option, then playing multiplayer isn't an option. Turning the firewall off temporarily is a way to check to see if it's causing any problems - if it works fine with the firewall off then you need to make some changes to settings in it, if it doesn't make a difference then you can try turning it back on at the end when it's working and seeing if it makes a change then. You're right in that it's a nice thing to have and keeping it on is more secure than not, but it's not much of a risk to have it off for a short period of time (and in all honesty if someone has the skill to take advantage of the firewall being off then it likely won't make a difference if you're using the standard windows firewall and they want to attack you for some reason). The windows firewall is capable of blocking local loopback requests, so you can't rule it out just because it's running on the same machine.

Worldguard has a logging option, you'd have to log when people placed down soul-sand or wither skulls, though (the server is what actually spawns the wither, not the player). You'd set the itemid for wither skulls to be logged, then look for where they are placed 3 next to one another.

Can you put up a screenshot of your setup? Could be a lot of things.

Great advice, Daniel - I'm just not sure it was intended for this issue? If you're still reading this OP, remove the version that asks you for donations and go here for the proper one; http://www.technicpack.net/download (you can also just navigate there by clicking the Technic Platform button on the top left of this page then the Download tab on the right side of that next page rather than trust another link from a stranger).

My favorite minecart powersource was being pushed by a little slime - failing that though you can hold up a carrot and pigs will push you along (pigs, of course, being the one true form of transport in minecraft).

It's not the same issue as the original posters, most people there had a configuration error (too much RAM set, RAM limited in environment variables), it's not the same problem as the last guy (he wasn't even running B-Team), running on laptops vs. desktops are largely irrelevant (beyond the usual considerations of "6GB/12GB" machines with mismatched RAM and integrated graphics being more common on laptops), the modpack may destroy it, it's not to do with the amount of mods in the mod pack (unless you're running on a computer with 3-4GB RAM and running out). It could be overheating but there's not a lot to indicate that, and I should note that you have to be careful when cleaning the inside of a computer, many parts (especially the RAM) are highly susceptible to static damage.

It's not the mods that are the problem - Java is not compatible with Java 8 yet. Once it's up on the main page as the default download you can assume it's properly backward compatible, but until oracle says it should be the default version then I wouldn't expect it to work (it may be fine, but honestly it's just pointless trouble to put yourself through if you're not a dev right now).

Je ne parle pas bien le Français. Je vais parler en Anglais. Je suis desole. Try looking through here: http://forums.technicpack.net/forum/75-attack-of-the-b-team-servers/ and you might find something (I'd recommend asking there too), but if it's just technic launcher with flans mod you're after you might be best doing a search here for a custom modpack http://www.technicpack.net/modpack/list

No problem, member. That usually fixes it (for future people reading this the Tracker is here and it often takes a few goes to get off the ship, so keep trying 5-10 times, it usually only takes 2-3 but you might get unlucky). Creator, make sure it's not touching any other object - that includes long grass, microblocks next to one another and torches (those all count as full blocks). Carpenters blocks will cause a crash and microblocks may. I'd suggest making a 'ship' on top of a dirt platform that's just made out of the ship helm and then just add things one or two blocks at a time - anything that's not vanilla isn't guaranteed to behave properly.

Also make sure you're not running out of disk space - the map files can take quite a lot.

Please post the crash report on the tracker - if it closes minecraft there'll be one even if it didn't pop up for you or anything. You can find a guide on where to find the report in my sig.

By default all the singleplayer worlds are stored in a directory called saves, go to %AppData%.technicmodpacksattack-of-the-bteam and you should see that folder there. Copy the saves folder from one machine to another (into the same place), and that should be it.

The modpack version, not the minecraft version (though those should be identical too).

Please post your crashlog up to the tracker so we can check what's actually causing the crash and work on fixing it from there (it's probably a client-side crashlog).

Error 403 is an authentication failure - firewalls are the only thing that are likely to trigger it on a public download like that (it can also happen with incorrect credentials on a passworded site). Edit: If you need more assistance, posting your launcher log up on the tracker along with this info is your best bet.

There's usually some system configuration issue with problems like this - I'd suggest posting this up along with a launcher log on the tracker, you should get better help for this kind of thing there.

Radios work, there's just a requirement now for the notenoughcodecs clientside mod to be added (which allows the clients to hear the aac or mp3 streams the radio puts out). You can get it here; http://openmods.info/ Actually CanVox, adding that to the clientside in this version might be a good idea (along with a default stream to be superawesome!).

The ship didn't vanish, it's probably still attached to your player. Keep mashing shift to get off the ship the second you log in, it might take a few goes but eventually it should work. Failing that you'll need to remove the ship in MCEdit (remember it's an entity now, not blocks!)