|
|
IC2Crash.PNG (152,136 bytes) |
|
|
You should delete the IC2 config completely and let it be regenerated. The problem arises from if you try to run a version of IC2 for 1.8+ on 1.7, so deleting it will certainly fix the problem so long as you're actually deleting the one it is using. |
|
|
Chocohead, could you please make the config file automatically changes between IC2:scaffold and IC2:blockScaffold depending on the game version? It is sometimes necessary to keep the rest of the config file. For example, when I was testing the explosion damage of the mining laser, I encountered the exact same problem. I deleted my config file and solved this problem, but later on when I was testing a dangerous fluid reactor, it exploded because I changed the reactor explosion power to 0 in the original config file and it got deleted. As a result, it blew up my setup and it takes quite some time to re-build it. This is also unaffordable for those people that has changed the config a lot. |
|
|
2.8.67 started converting pre-1.8 configs over, the actual change is not too hard but getting a 1.7 workspace to do it is much more effort. So long as you've not got a scaffolding to recycler machine, just removing the item completely out of the blacklist makes the issue go away without other side effects so you can (theoretically) freely use the config on whatever IC2 version you want. If you're switching between versions that frequently though I'd recommend launching them out of different file roots as worlds are still not cross-compatible even if the configs are. |
- Anonymous
