Search results

What is your IGN (Case sensitive): Fattigfaan Age (Must be 18+) : 26 How long have you been playing Minecraft : On and off since vanilla beta. Do you accept the rules : Yes Where are you from? : Sweden How big is your knowledge of mods? (e.g. Tinkers construct, Railcraft) : Been playing around...

Name/Nickname: Tig or Fattig IGN: fattigfaan Age: 24 Why you want to join: Looking for a nice and friendly server where i can just chill and build stuff. What you would bring to the server: Part from crappy jokes.. I've played around alot with the mods and know a thing or two about them. Used to...

Yeah might admit, i overreacted a bit.. But them bringing in more people now, will fix alot of the things, as they have more knowledge of the mods and will hopefully be able to make fixes for things faster.

Sounds nice Slowpoke. Don't get me wrong, I love the modpack so far, even though it has issues, but that's to be expected with an early release. The only real issue i had with it was that it seemed to have been pushed out there a bit too fast. I'm really looking forward to what's to come out of...

That's the thing though, is all the errors just not relevant? Or do they cause any kind of lag or other issues to the server?

But, you're the guys who put the modpack together, so ain't it your responsibility to make sure that everything works? Not the actual mods themselves, but getting them to work together.

That's the thing when you're making a modpack though. You make it, knowing that things gets updated frequently, so that's the job you agree'd to do. Sure, it's hard to fix alot of the things, and of course it will take time to get everything working, but then rather put it off for a while longer...

That glitch wasn't really directed directly at the FTB crew though, more to other users of FTB. To see if anyone solved it or had any idea on what the issue might be. The players do alot for modpacks, just look at what the players have done for Tekkit, as an example. It was also really glitchy...

Hence why i reported it to the mod creators as well..

Hence why I'm reporting the bugs that I can find. Like I said, I love the modpack, I just think they have some things they need to fix before actually putting it out there, unless they're trying to get the players to fix it for them.

Some items not working, i can understand as it's still in beta. It can be hard to test out every single thing with every possible use, so i can understand why some things aren't working. But the errors you get in your console when you host the server, that's not acceptable to me. And I've been...

What about the ic2 blockid collision? They should be able to change the ID's in the configs.

Yeah but bringing the mods together, include getting them working without errors.

Indeed it is. But you'd think they would work out the errors you get when starting up the server at least.

If you start a clean server, you find several errors.. Forestry not loading correctly, ic2 blockID's colliding with other blocksID's, paulscode giving errors, even complaining that it's missing RedPower, and alot more. Sure, the servers work, but really? This many errors on server start...

Hmm, removed that modular forcefield mod, and now I'm getting a slightly different error with advanced machines.. [SEVERE] Encountered an unexpected exception NullPointerException java.lang.NullPointerException at...

It might work with just the machine. If it does, try pumping the monazit into the machine with bc pipes, and pump out the finished product, see if that's the issue.

I don't think the 2 are related though, as I've been running them with and without batboxes, and the machines itself works fine with every ore, even monazit which is the ore that makes it crash. But the odd thing is, it seems fine on lower RPM's, but once the speed picks up it crashes the...

Noone got it to work still i take it? It seem to be when the macerator picks up in speed. I don't know if it has anything to do with me pumping the ores into the machine and extracting it with bc pipes.

Thing is though, i tried adding 4.4c both on server and manually adding it to the client as well. Still doesn't fix it though.