JaariAtmc

Totes mate. So, why don't you go looking in which MC version that recipe was added and which version of MC Tekkit Legends is?

This is your own fault for downloading pretty much all the mods from crappy rehost sites. Only use Curseforge, minecraftforum.net (which links back to Curseforge anyways), or the own modmakers website (bibliocraft, iChun and Galacticraft for example).

Yes. Forge doesn't even run Java 9 or Java 10 anyways.

Delete the dimdoors folder in your world save.

This was handled on Discord.

No, you have 15,9 GB total.

1) Yes. To be more exact, it will just generate again. It might get corrupted again though, in case of another sudden power loss situation. 2) The references to DimDoors yes. (StevenDimDoors.mod_pocketDim.core.PocketManager.createAndRegisterBlacklist(PocketManager.java:697) and (StevenDimDoors.mod_pocketDim.saving.DDSaveHandler.loadAll(DDSaveHandler.java:59). Also, it being Tekkit and more people having this issue.

You can't allocate 8 GB RAM if you do not have it available.

Your power or pc/server probably shut off suddenly. Power loss maybe? Remove the DimDoors folder from the world save. As that got corrupted.

C:\Program Files\Java\jre-10.0.2\bin\javaw.exe

You stated that making a modpack was easy. Making a server is kinda the same really. You just need a minecraft server jar and the forge server jar (as opposed to just forge universal renamed to modpack). The minecraft server jar needs to match the MC version of the modpack, while the forge server jar needs to match the forge version number of your modpack. You need to do this manually, but you can keep reusing these files. As for clientside only mods, think of things like CustomMainMenu or ResourceLoader. These are things that the server doesn't understand. The server has no main menu. Some minimaps are clientside only too.

Why do you have MicDoodleCore included when you are not using it?

https://technicpack.zendesk.com/hc/en-us/articles/203799459-How-to-create-a-server-for-your-Platform-modpack You should be able to follow directions just fine.

You do not have the 2 GB RAM available which you tried to allocate. This is also likely due to you using 32-bits Java. Download 64-bits instead.

If it is a 1.7.10+ modpack, just add it to the mods folder. If its a lower mc version, well, that's going to be pretty painful to explain.

Y'know, except that one reply where I told not to use Java 10, but java 8. Oh wait, multiple posts over the past few months.

Please try a release version of Constructs Armory, instead of a beta version: https://minecraft.curseforge.com/projects/constructs-armory/files

...Don't use Java 10, use Java 8.

It is located under Launcher Options -> Java Settings. You are still limited by the amount of RAM in your pc. 1.12 modpacks usually require atleast 4 GB, while the max for a 1.7.10 modpack tends to be 4 GB (as an example for increased RAM costs).

If you want a quicker answer to these things, use the Technic Discord server instead. #tech-help channel, and don't forget to read the #rules channel. As for your issue here, Model Baker issues usually point to running out of RAM during the startup process. It is MC 1.12 after all, and RAM requirement went up considerably for such modpacks. #thanksMojang...

You've got a mix of illegitly obtained mods, 1.7.10 mods and 1.12.2 mods. That's going to be a problem. Your bin folder is empty, which should contain the forge.jar renamed to "modpack". You currently have that file named wrongly in the top folder (sickcoolradpack). Also, remove all the excess folders: asm, blueprints, crash-reports, logs, resourcepacks, saves. And remove the botaniavars and usernamecache files.

You might want to update From the Deep by one version.

Please try using this mod instead of your version of the Statues Mod: http://fileserver.mage-tech.org/1.7.10/mods/statues-1.7.10-2.1.4.jar

Other than this file missing in the mods folder (add to 1.7.10 folder), I do not see anything wrong with the modpack.

https://steamcommunity.com/app/219150/discussions/0/522730701434599527/ ^Relevant, it simply that the Intel HD Graphics drivers are too outdated.