Search results

Thank you, that's the kind of response I was looking for.

That would be your problem. Direwolf 1.4.7 is very different from Direwolf 1.5, so it requires a map reset unless you want to run it through mIDas, however there would be a lot of blocks that you would have to replace with 0 since they are removed from the pack. Redpower, for example. It...

Are there any errors in the log? I myself have never used Forge Essentials but it seems pretty straightforward.

It's not so much an ETA that most of us want rather than what is actually going on. They said that there are more problems than just the map fixing tool, but they never answer what those problems actually are when asked, even though it should be as simple as "There are a few bugs with Powersuits...

I grabbed that from the 1.5 config, however I do know that it was in the 1.4 config as well, probably named differently. Let me open up one of my old configs. EDIT: No, looks like it's the same option. Here is a pastebin of the config. It's on line 46.

I've used both Multicraft and McMyAdmin along the ways for my server, and they both work fine. In Multicraft, all you have to do is edit /multicraft/jars/[jarfile].jar.conf and choose what settings you want in there to fit your server. There is a place for java options as well. McMyAdmin is a...

Another way to do it would be to add your staff members to "S:ForceFieldMaster". That will allow them to not only bypass the kill fields but also modify any MFFS without an ID card. Example: S:ForceFieldMaster=joey19982;TheDJParadox;Dingham

I'm not asking you to answer every question. To quote my post from earlier: Besides, if everyone has the same question, it only takes one post to answer them all.

Oh I know that they're working hard on it, I just wish that they'd be more communicative about it. I haven't seen really any feedback since the "Final testing." I am being a bit impatient, but mainly because supposedly the pack is done and just in testing. I don't see why testing would take so...

So much for some sort of update today, I suppose. 1.1.3 = HL3.

Well, Perm gen space still does come from the RAM. I'm not too sure what else to do, though. Sorry :(

Any idea how much of the RAM is being used at the time? It may just be that 2GB isn't enough.

You should be able to fetch it from the server.log file instead of copying from the console, which is in the same folder as your server's .jar.

Direwolf20 made a video today that will show you the basics of them. As said, you need a saw to "cut" the blocks.

Again, try setting it to: java -Xms2G -Xmx2G -XX:PermSize=128M -XX:MaxPermSize=256M -jar server.jar nogui and post the results. Even 512MB is a bit much for what I assume is a smaller server (based off of ram). I have a pretty large server and only set it to 256MB.

0% usage isn't normal nor possible... Also, mind using Pastebin next time? The text is pretty hard to read. You probably want to post it on TickThreading's GitHub issues, as it says when you run a server with TickThreading. Nallar is away right now though. Can you pastebin your whole...

Try setting it to -XX;PermSize=128M -XX:MaxPermSize=256M. Having a whole gigabyte of Perm space is unnecessary, especially when you only have 2GB of RAM.

By default /ticks (From TickThreading, which you obviously run) is assigned to ops only. If you use a permissions plugin, that is a node you can put in there to give a group permission to use it. I recommend giving it to moderators.

You'd have to edit the mod similar to how servers have patched Mining Lasers. Once the Direwolf pack updates I may try my hand at fixing it and release it here.

Although I appreciate you guys seeking me out in other areas, keep this to PMs please. This topic is for the modpack, not my server.