Search results

Like I said, I'm using Multicraft. The .conf file contains all such stuff, including startup arguments.

It hasn't happened again so far. I did have the PermSize set correctly in the .conf file but somehow it wasn't being applied I guess. Maybe it used the wrong one, I dunno. Now it's working though.

I decided to install the server from scratch and now it suddenly works. Not a clue what somehow fixed it though.

For some reason my server throws a memory error at me when I try to start it with MCPC+ installed. Without it it runs fine. Running on Linux using Multicraft. Log of the crash: 2014-05-30 16:37:35 [SEVERE] Exception in thread "Command Reader" 2014-05-30 16:37:37 [SEVERE]...

Ah alright, that would explain why it didn't work as I expected :P. Luckily the explosive force of Nukes and Reactors can be changed in the mod config. So I'll just lower it or turn it off completely.

Alright, that's what I needed to know. Guess I'll postpone those plans for now then. Thanks!

So from what I understand a 1.6.4 version of FTB Unleashed will be released in a few weeks? I assume current 1.5.2 (1.1.3) worlds will not be compatible so an upgrade is not possible, right? Would that mean that starting a brand new FTB Unleashed server right now would be a bad idea and a waste...

Assuming I entered everything correctly, this list is not preventing Nuclear Generators or Nukes from wiping out a claim. I did several tests with this setup loaded, made sure the ID's were proper. Made a regular claim for myself and an admin claim next to it. Then set up a reactor to blow up...

So I have extensive experience in running vanilla Minecraft servers and also Tekkit servers. Both of these run on a (slightly altered) version of Bukkit as the framework. I blindly expected that Feed the Beast would also run on some version of Bukkit but apparently I was wrong. Am I correct in...

After some more research and messing around I found the problems. The first error had to do with a mod being disabled while other mods are looking for it. Always check which mods are dependant on a mod before disabling them. The second error probably had something to do with the location of...

I've disabled both, very certain. The error it gives now seems to be related Open Peripherals. It gives this AFTER all the mods have successfully been initialized. 2013-12-04 17:42:44 [SEVERE] [ForgeModLoader] The following problems were captured during this phase 2013-12-04 17:42:44 [SEVERE]...

I've disabled EnchantingPlus Hats Hatstand Mystcraft ReliQuary Thaumcraft Thaumatic Tinker Twilight Forest I figured it had to do something with a disabled mod after reading through the error logs a bit just now, but I couldn't figure out exactly what the problem was. Edit: Oh, hang on. After...

Hey guys, My name is TigerXtrm. Been playing Minecraft and various modpacks for a while now and also own a couple of servers. Used to support Tekkit but recently made my way over to FTB. So here I am :).

I'm trying to install FTB Unleashed 1.1.3 on my dedicated Linux server (CentOS 6.4). I'm setting up the server through Multicraft. I've disabled some of the mods by adding .disabled behind the file name and then uploaded the server files to the server. When starting the server the process...