EvilOwl
-
Posts
1462 -
Joined
-
Last visited
-
Days Won
36
Everything posted by EvilOwl
-
Are the server config files synced (identical) to the client config files? Are you using the same version of the pack on the server and on the client? What pack is this? Api modpack link would be nice.
-
It's for mac users I presume. Why is there no information in the post about that?
-
Attachments don't work on the forums atm. Try pastebin. com or paste.ubuntu.com.
-
This is not a launcher problem, this is a modpack problem, especially when client/server configs are out of sync. Closing. Post in the appropriate bug section for official modpacks or in Platform Pagoda for custom modpacks.
-
Your system obviously can't show the progress bars from Forge, disable them in .technic/modpacks/modpackname/config/splash.properties It's the enabled=true line in the file, change it to enabled=false.
-
Wrong section. Moved. Post the api link.
-
Right, you need Minechem 5.0.5.395 or newer
-
I don't know that. I'm not using apps that add an overlay to my games. Check it. If it crashes disable it entirely. If it crashes again unistall it from your pc. Experiment.
-
Don't spill logs. Use pastebin or similar sites. That fix above with Reliquary doesn't apply to you, it applies to 3.0.0c, you are running 1.0.10 now, and I know 1.0.10 works like a charm without any changes (you don't need the legacy fixer and new reliquary for that version). That crash log is a jvm crash, it means that your system is at fault here, especially when you have Evolve installed: 0x00007ffcd5d20000 - 0x00007ffcd5dbe000 C:\Program Files\Echobit\Evolve\Drivers\EvolveGameTracker_64.dll 0x00007ffccc460000 - 0x00007ffccc629000 C:\Program Files\Echobit\Evolve\Drivers\EvolveOverlayHelper_64.dll 0x00007ffcd6830000 - 0x00007ffcd6850000 C:\Program Files\Echobit\Evolve\EvolveEasyHook_64.dll Uninstall Evolve (or disable it for a minute) and recheck.
-
Why don't you test it locally? There's a bunch of Forge-only packs around here like this one or this one. You set it to the correct MC version and Forge version you need, install it and drop your mods, config, flans, hats, journeymap directories to .technic/modpacks/modpackname/ and you can test it there without the need of uploading all this again and again. Once you're done you get those directories again to a zip file (add /bin/modpack.jar) and upload it all once. You can also use multimc.org for that. Your missing mod that depends on ttCore is RedstoneArmory, update it but wait.. there's more, like a lot more. All the changes made to the modpack to let it start without a crash are here. The left side is the original zip you linked and the right is the working modpack. I used Forge 10.13.4.1492-1.7.10 for those tests.
-
I still don't see the modpack api link from then platform. I wanted to help you but you don't even read what's on the screen. If you're downloading a mod you need to read the whole curse page or the minecraftforum post about the mod, you didn't do that. Answer me this: which versions of WailaPlugins need ttCore to work and which need EnderCore (in the ttCore's place) ?
-
Attachments don't work on the forums atm. Use pastebin, post only the link.
-
Yes you should but check what version of hexxit are you running now after all those shenanigans. Click the modpacks tab and select hexxit, the version should be on the top right of the hexxit page.
-
Loads for me fine, creating a world is also working.
-
Wow. You broke only two rules when posting here. Good job (not really). Edit your post, get that wall of text where it belongs, post only the link. Use the search form next time or just read the previous report. Yes, the answer to making 3.0.0c work is in the previous report, here.
-
Here's the same modpack on my end Your gpu is probably.. uh broken or a potato. Post some specs.
-
No idea what you did there. You can always redownload the launcher or reinstall the modpack if you broke everything.
-
No modpack api link, no screenshots of the error, no logs. Nothing
-
That's your choice. Like I said before the recommended version works fine, the latest also does (with a small fix)
-
Nah, it's Reliquary-1.2.200.jar, you probably reinstalled the recommended hexxit version (1.0.10). Check it in the launcher Edit: your own crash log shows that xreliquary{1.2} [Reliquary] (Reliquary-1.2.200.jar) Unloaded->Constructed->Errored
-
I'm sorry but copy.com links for zip modpack files are doing some strange stuff at the moment and you will get a platform error when you try that.
-
how to chain the liteloader with forge in technic Platform?
EvilOwl replied to Revenge01's topic in Platform Pagoda
Your answer is here and the search form is here -
You already have a thread like that started in Platform Pagoda. I'll answer you there. Closing
-
Recommended version is working fine, the latest 3.0.0c has a bug probably because a mod author changed a file hosted in his repository and the modpack downloads that newer file (actually a library) that's not synced with the mod version. In other words: update Reliquary to this version and the modpack should boot ok but that will make it a custom modpack. Remember also about the legacy java fixer if needed.
-
It's the real deal but like I said that can change since the pack is still indev.
