EvilOwl

Yes, joining our Discord, not reading the rules and then doing things that made moderators ban you is a really great plan for reviving Voltz. Good luck with that!

Admins barely check the forums, they only make sure everything is working fine and clean up the forums every time it's needed. Posting your email address in a public place like this was a bad idea. People can spam you. Remove it. I hope you are aware most of the mod authors do not support minecraft in the versions you mentioned so "cleaning out any bugs reported" is just not possible, nobody will go back to an old mod version to fix it if it's like crashing. Note that MinecraftForge supports only the latest MC version. There was a team that already tried to update Voltz but it all failed, idk the details, that was before my time. If you wanna help in this community just join our discord and let us know you a bit more, show that you are a good modpack maker, maybe even help some people fix their bugs here or on Discord, that's usually the way you can earn respect here.

I would totally not use a pack that's for mc 1.6.4 in 2017. Find Something more recent and half of your trouble will be gone. Note that the original Moonquest modpack is hosted on the ATLauncher, not Technic, this was probably just somebody porting it with some custom changes. Also idk what are you trying to do with META-INF, afaik in 1.6.4 you just had to drop a jar in the mods directory without modifying minecraft's jar. The crash you were getting was caused by low memory settings in the launcher and/or using 32 bit java instead of 64 bit java just like Jaari said in his first post in this topic.

Moved to the correct forum section.

Download and install 64 bit java 8 and then restart your machine. Do not install java 9.

We don't support modpacks that are an obvious copypasta from other launchers. When a modpack is being created a user is linked with the Modpack Terms. Please read those.

Did you read your own log? "cpw.mods.fml.common.MissingModsException" That bring us to the main question: how did you make the server? The needed server files are already linked on the modpack page. Guess you didn't use those. Attach the full fml log from the server.

Huh. Another ad. User restricted from posting.

Topic moved. Ad link deleted. One more link like this and @RyanCaleb will be banned.

Uninstall java 9 and install java 64 bit java 8. For details you can visit our #tech-help channel on discord, there's a tutorial specifically for mac in the pinned messages. Pro tip: read the #rules channel before you start typing

Locate the .technic directory, there'as a Logs folder in there, open it, find the latest launcher log, copy the contents to paste.ubuntu.com and post the link here or just use attachments to upload the log file here.

W don't support pixelmon modpacks, try a different pack.

Moved to the correct forum section.

You have 32 bit java. You need 64 bit java, use java 8.

Make a proper ad for it and post in the correct forum section.

Since the user that posted here is no longer interested in this community I'll just leave some info and close the topic so others can find it and benefit from it. Modpack makers have a modpack policy they agree on when adding a pack to the platform, it's their responsibility to get all the permissions and check mod licenses. If we get a report with a proof that a pack is breaking the modpack policy we simply remove it. Contact us on Discord if you want to talk to us about it. I did read the whole post, I remember reading "the issue indeed lay with the Technic launcher" and sighing. The issue here is using Windows 10 on old hardware with java version past java 8u60. There are also cases of not installed/updated gpu drivers that are very similar. Details here. Vanilla launcher is using the built-in java that it downloads, it's 8u20 or 8u25, I don't remember exactly which one of those 2. It's surely older than 8u60. Technic uses the system's java, in this case 8u144, The log above says that. No, I wasn't bored. This happened when one of the staff members fixed something on the forums so I tested if it works now (yes, Pyker fixed attachments) and looked around Platform Pagoda, my fav section from back when I wasn't staff here. You can probably find my old posts from that time.

Go ahead then, add the info, without it this topic's existence doesn't make sense.

If the launcher is closed by force or other problems occur while writing the "installedPacks" file then this happens. The file gets corrupted and the packs are gone. You can install the launcher in a different location and check the file contents, it's easy to rebuild it with a text editor.

1. We don't support pixelmon packs. 2. Did you ever check what java version is the regular minecraft launcher using vs. the java version technic is using?

We resolved this issue. We had a bit of downtime. Sorry for that

We don't support Pixelmon in any way, sorry. Try running tekkit legends and then post launcher logs from .technic/logs, use pastebin.com or paste.ubuntu.com.

Visit our discord server and upload the logs to #tech-help. Looks like some software limited your RAM with a JAVA_OPTIONS environment variable.

Visit our discord server and upload the file with the logs to #tech-help. Looks like old hardware + Windows 10 but I'm not sure.

Looks like a firewall issue, blocking java from accessing the internet.

Visit our discord server and upload the logs to #tech-help