Loader

Please post your logs up on the tracker after reading the tracker rules and guidelines and I'm fairly sure someone will try to help you. It looks like some issue with an overzealous antivirus program.

Guys, please post your logs up on the tracker after reading the tracker rules and guidelines and I'm fairly sure someone will try to help you. Kylogan, update java here.

Please post your logs up on the tracker after reading the tracker rules and guidelines and I'm fairly sure someone will try to help you.

Yes, I suppose you do have the same problem (that this isn't where you post this kind of thing if you want people to help you ) Please follow the same advice.

If you want to make sure the generation is working (usually it is and you're just having bad luck), create a superflat world, fly around a bit, if you find a village then they're spawning properly. If they're spawning properly, the next step is to look for them - as Turgle said they won't spawn everywhere and in some areas that they can spawn they won't (they can't spawn if they're on something like water or too steep a hill, but they will tolerate a very steep hill by default for example).

He meant javaw.exe, if your program crashes sometimes it remains open which stops you from opening more windows. He's suggesting killing all the javaw.exe instances in memory so that there's no chance of a half-dead one conflicting. This may or may not be your problem, it's much more advisable to listen to Kalbintion here if you want help;

Eye_Mine, if you'd like to test the launcher to be sure for yourself, you can build a modpack that's just vanilla minecraft and see whether it's slow or not for you. If it's fast, then it's probably some of the mods that are loading in on other packs, not the launcher in any way. I'd say that behaviour (vanilla minecraft loads faster than that same minecraft but with a million extra lines of plugin code) is to be expected, but you don't have to take anyone's word for it if you're really unsure.

I thought you were chiming in with your own question that wasn't really related to the current conversation going on there Eye_Mine, I apologize if that wasn't the case but what you'd put sounded to me like it'd be fine as the topic of an entirely new thread. Once I understood what you were asking I did my best to clear it up, I certainly didn't mean any offense by it. Can you explain to me how your question was clarifying the point of the earlier conversation, please? I'm struggling to see the link so I've obviously missed something. If I've misunderstood some wording there (admittedly to begin with I really wasn't sure what you were asking) then I don't want to make that mistake again if I can avoid it.

Please post your client logs up on the tracker and we'll take a look - you can find links on how to get the logs, the tracker itself and the guidelines for posting on the tracker in my sig.

Please post up on the tracker here Nicojah with a little more info on where it crashes, please follow >these guidelines. For future reference for people I will help if you post in the right place to make it easy (or at least not too difficult) for me - it's almost never going to be in this thread (unless you've got a suggestion for a change or something to add to the first post).

If you don't have the issue with Java_options being set to override your java max memory allocation, then you don't have the issue with Java_options being set to override your java max memory allocation. If that's not clear enough yet, then simply understand that you do not have the same issue. Please post your logs up on the tracker following the guidelines - links that will help with that can be found in my sig.

I'd post here as well if I were you, not sure where's the right place for this but best of luck finding someone to help http://forums.technicpack.net/forum/39-scribble-parlour/

The tracker is where we monitor and handle issues, the logs are made by the launcher when it runs and by the modpack itself if it crashes, you can find links to help you with all of those in my signature. If you've got any further questions or those links confuse you somehow, please feel free to ask, and before I forget: Welcome to the forums, MoonlightPawz!

Not really, I can tell from that that there's a problem early in a tick, but that doesn't narrow it down much (there's 20 of those every second on a healthy server). The whole log would be more useful, and posting on the tracker would be more useful still. If you want to do it bit by bit then we can, but it might take a while.

Please post the whole log (server crashlog preferably) up on the tracker, there's links in my sig to help with that. In the case of the server log it should just be in a crash-reports folder wherever the server itself is.

FORUMS DON'T USUALLY HAVE NO SOUND!?! I'VE BEEN ONLY IMAGINING US ALL YELLING ALL THESE YEARS!!!

localhost or 127.0.0.1, they're both the same place and both working (it's just a location to connect to and it's doing that - the problem isn't with that). Like Kalbintion asked though, how are you actually running the server? Which file are you using?

No, he means don't worry - it'll come in the next version. Please post your logs up on the tracker and I'll take a look, you can find links to help in my sig

Ok, that's quite abnormal for that system - try making sure you've got enough RAM allocated in the launcher like this (1.5GB to 3GB seems to work best for most people);

Toadster, I see you're pulling up a lot of these old server posts (there's nothing wrong with that, it's just likely not that productive). Are you aware of this part of the forum? It might be more helpful to look there if you aren't. http://forums.technicpack.net/forum/75-attack-of-the-b-team-servers/

That's actually a really cool idea in a way, it forces you to think of a clever way to hide and protect your stuff like vanilla minecraft (though if there's worldprotect or something then it escapes the point). Maybe they had a lot of complaints about strongboxes not working with machines? (they only work if it's public, private and the machines can't access it). Now you've got me wondering Did they say why they'd disabled private strongboxes?

This is an old thread, soon you'll need steam, and in some situations you'll indeed need 4 - most of the time 2 is fine but on occasion especially if you travel away a lot you'll find it runs out with only 2 per turbine, it's probably a rounding error. 2 per machine and an additional 2 to offset that seems to work fine going through pipes, but I found just 2 each wasn't quite enough to avoid whatever that running out of water thing was. It's possible that this was just a bug that's been fixed in the last month+ though.

If you don't know which one you opened first, close both and try again to open just one to be safe. The launcher comes up pretty quickly compared with loading the game, so it's usually worth it.

Typing in your WAN (internet) IP will have that effect - what's happening there is you're trying to contact yourself through the internet, without going out to the internet (routers can be dicks, but in this case it's entirely intentional and useful behaviour that keeps LAN traffic safely in the LAN). 127.0.0.1 or localhost are loopbacks which connect to your own computer without even reaching a network adapter (in theory), the 192.168.*.* networks and 10.0.0.* networks are commonly used for internal communication on LANs, and that's what you need to use if you have to use one, not your internet IP. Think of it like trying to ring yourself on the phone you're using to call yourself (it's not a perfect analogy, but if the previous explanation doesn't make sense to you then that's close enough). Both 127.0.0.1 and localhost are exhibiting normal behaviour for that kind of connection (so those addresses are fine) but the server isn't set up or running correctly, try what Kalbintion suggests.

Oh yeah, to maximize your chances talk to them all on facebook, comment on their videos with what you'd like to see - I just meant to give an example (I picked chimneyswift because he does witchery already).