Search results

Profile options then click unlock. Now you can edit the pack.

Not unless you are the server owner.

Yes and use feed the beast paste to post it.

Probably for being too op.

Your instance folder is where I would check.

Try removing the mod you added first.

I read that extra utils 2 is causing the crash. So if you much use optifine then you need to downgrade that mod. But like the above user suggests just don't use it.

The pack maintainer, Darkosto, posted the crash on the mod author's github but he never replied to it. He did fix it by reducing the amount of blocks that veinminer would break from 9999 to 2500. So if you really want to use it then you will need to make that change yourself manually. It still...

It sounds like something on your end and not an issue with the pack. I have never had this issue before. Can you check the logs folder and post the latest fml one please. @lokirocks25 Please create your own thread.

Sorry I made a mistake. Can you check the logs folder for the latest fml log. I believe it creates a new log everytime the pack is ran.

You will need to allocate more memory. There is currently a memory leak within forge that is causing the 1.10.2 packs to use more memory than usual. You will need to allocate at least 4gb of ram and if you don't have 8gb in total then you will struggle.

Remove optifine.

I read that the mod that causes it is extra utils 2 and if you downgrade it it will work again.

I assume all your drivers are up to date? Is that the latest one?

Edit the options file in the instance folder and change the mipmap setting to 0. This will turn it off. There currently is a memory leak within forge and is causing it to use a lot more ram than it should.

The crash reports folder and post the latest fml log.

You really should have working backups at all times as you never know when things like this can happen.

We would need to see a crash report because veinminer is no longer in the pack as of 2.5.5.

It sounds like something with your system and not specfic to a modpack. Have you tried it with other modpacks?

That could be related to your antivirus program blocking access to that file. If so then set it to ignore it from scanning your curse/ftb folder.