Search results

New version of RFTools (2.62): Curse: http://www.curse.com/mc-mods/minecraft/224641-rftools#t1:other-downloads Mediafire: http://www.mediafire.com/download/y23yyxzcnhdn2nc/rftools-2.62.jar Have fun!

Yes, more filtering and sorting options in the dialer are planned.

This modpack is supposed to be played in peaceful.

We're doing our best to solve all bugs we find. But indeed. It is not always easy. There are so many things that can go wrong.

Don't use java 6. That's not likely to work anymore. Java 7 or Java 8 should be fine (I'm using 8 on linux with infinity just fine).

In the comment that you are replying too I was talking about the unnatural darkness that occurs when a dimension runs out of power. I'm not talking about the hardcore darkness of the pathfinder modpack. In normal RFTools (outside pathfinder) the world is as bright as it is in the overworld.

No, the bug in rftools shouldn't cause a crash. It just ignores the first dimlet.

XP doesn't exist in peaceful.

New version of RFTools (2.61): There are still bugs left on the github. I'll try to fix those soon too. Especially the VERY annoying bug with the items disappearing if you shift-click them in some of my inventories. So for now be careful with that. Curse...

This was indeed another bug and I'm fixing it now. Thanks for reporting.

Thanks I'll check it out.

Yes, a crash report for that would be interesting as that appears to be something else. And I'm preparing new release.

Well you need to go to that world to get food, wood, and other materials to proceed with the quests. How else are you going to solve the quests?

Yes, that's a known issue. The dimlet format has changed in 2.60 and the quests have to be adapted for that. Just complete the quest with /hqm edit (I think that was the command)

Warning. Found a bug in RFTools 2.60. The first dimlet in the enscriber is not parsed right. Put a 'digit' dimlet there for now!

Something for next version of RFTools. Dimension validation before you create it:

Known problem and reported in the post right before you as well.

This is a known problem and has been reported a number of times already in this thread. For now you'll have to go back to 1.0.1 or else wait until it gets fixed.

Actually maybe it wouldn't be that hard. I see a few ways where it would be possible to do. It wouldn't replace the current grammer but just be a shortcut to it.

Yes, this has been suggested before. However, that's a rather big change so not sure if I will get around to that soon.