Minecraft Launcher For Mods
Natalí Stibb
ATLauncher is a simple and easy to use Minecraft Launcher which contains 155 modpacks for you to choose from, as well as the ability to browse and install packs from other platforms including CurseForge, Modrinth and Technic.
So why not take a look at the different packs that are available or just download ATLauncher and give a try yourself. If you're still unsure about us, then visit our about page to get a list of features.
Currently there are known issues with logging into Microsoft accounts. Check Downdetector for user reports of the issue.
This issue is intermittent over the last week, and affects all launchers and websites that use Minecraft services, including the vanilla launcher and minecraft.net.
This issue is at Microsoft/Mojang's end and is not something that ATLauncher or individuals themselves encountering issues can fix.
Some people have had luck using a VPN set to another country in order to login, but other than that all that you can do if you face login issues is to keep trying, logins start and stop working constantly, so just keep trying.
Again, please note that ATLauncher staff cannot do anything about this, please have some patience and just keep trying the above. Our support cannot do anything to fix this and will just direct you to the above.
Thanks
Unfortunately there is another exploit going around the modded Minecraft community at the moment.
This is an RCE which allows bad actors to run code remotely on your computer when connected on the same server as them.
The scope at the moment seems to mostly affect mods on 1.7 and 1.12 but may also occur on other Minecraft versions, there is still work going on to find a full list of mods and affected versions. If you play singleplayer only you don't have anything to worry about, only if you play online on public servers.
Due to the nature of this being a remote code execution exploit, any attacker on the same server as you could've run any code on your computer, so as such there's no way to tell if you've been affected or what code was run.
The best course of action currently if you play older modpacks on 1.7/1.12 is to simply not join any public servers unprotected and to add this mod to your instances to protect yourself from the exploit.
More information about the exploit and affected mods and solutions can be found at
There is a thread in our Discord if you have any questions.
NOTE: We posted this on our Discord when it happened, but forgot to post to our News feed, so if you already got the ping from our Discord about this issue, this is the same issue, not a new one.
The situation seems to have relaxed a bit, the details on the malware and what it does is known (again if you're interested take a look at this GitHub repo) and we have tools available to detect if you're infected:
- CurseForge Infected mods detection tool
- NekoDetector
Both these tools will detect for any traces of the malware on your PC or within your modded Minecraft installations (be sure to scan your entire drives, or at least your user folder and any folders where you run Minecraft from).
Several platforms have come out and confirmed that they've scanned and removed all traces (if there were any) of the malware from their sites:
- ATLauncher: All clear to install and use ATLauncher modpacks
- CurseForge: All clear to install and use CurseForge modpacks and install and use CurseForge mods
- Modrinth: All clear to install and use Modrinth modpacks and install and use Modrinth mods
- Technic: All clear to install and use Technic official modpacks. Non official modpacks were not verified as they use external download sources, so if you plan on installing a third party pack from Technic, you should be cautious and scan after downloading.
Make sure that you have scanned your system using the tools mentioned above before installing or playing Minecraft.
ATLauncher will be investigating how we can detect for and warn against this type of attack going forward, including checking not only for this specific type of malware, but also checking for changes to your mods since downloading. Keep an eye out for more updates on that in the coming week or two.
As always, if you have any concerns or questions, please reach out in #malware-incident channel in our Discord.
There is currently an ongoing incident within the Minecraft modding community where malware has been found to be included in some Minecraft mods (and bukkit plugins) on CurseForge. This included being included in some modpacks.
There are some smart people going through and finding out what the malware does, but at a high level it looks like it steals authentication credentials for Minecraft/Microsoft accounts that are logged into various launchers (not including ATLauncher), as well as stealing browser cookies and discord tokens as well as other things.
It self replicates itself, injecting a payload into any Minecraft mods in your system so that it can spread, and that's believed to be how it got onto CurseForge, unknowingly uploaded after the devs machines were infected.
Due to the fact that it can replicate itself into mods, it's highly likely that anyone who has been infected with the malware now has it injected into the mods on their system.
You can check if you're infected by using the detector tools released by CurseForge here.
The situation is still very much ongoing, and we'll be looking to place mitigations in place within the launcher to check for the presence of these infected mods as well as at the system level if you're infected. Will be looking to roll that out soon, again some smart people are looking into mitigations and what can be done to detect and remove the malware.
While more information is still being found out, for now the recommendation is to still not download any mods from anywhere which includes CurseForge, Modrinth and from any other sources, including friends.
If you have any questions or more information, please visit us in Discord in the #malware-incident channel.
Mojang have announced that on September 19th they will turn off login for unmigrated accounts. This will mean you'll no longer be able to login and play Minecraft.
We will remove legacy unmigrated account login from the launcher once Mojang have confirmed to have turned the login servers off.
If you still haven't migrated your account, please make sure you do so now so you don't lose access. If you're having troubles migrating or need help, take a look at Mojang's migration FAQ page.
I've recently changed to the new Minecraft launcher, and I have noticed a change in the .minecraft folder layout. I can no longer install mods just by copying it over into the versions/1.6.1 jar file, as this file refreshes every time it is launched.
I am specifically trying to install Optifine, which does work with 1.6.1. Where do I drag in the mod files now? I can't seem to find a jar file that is suited to it, except in the version folder, but as I stated above, this refreshes every time.
There doesn't seem to be any official way. Then again, modding the game by splaying open and modifying the internals of the .jar file was never really officially supported, either. The new launcher is, ultimately, part of a rather large series of changes to Minecraft, including making mods actually something the game supports via the new Resource Pack stuff, but until that time, modding is a bit more awkward.
However, there's still a way to do it. Go into the versions folder inside .minecraft, and copy the version you want to mod. Rename the copied folder, and both the files inside, to some new name, say "modded 1.blah". Lastly, open the .json file in a text editor, and change the line that will read something like "id": "1.6.1", so that the ID matches the new name. The new launcher should now show a version "modded 1.blah" in the list, but since that version doesn't exist on the Minecraft servers, it won't get overwritten. Splay open and tinker with the .jar file in there the same way you always would with the old launcher.
Note:
If you are using the new launcher with an older version of Minecraft, then the mods you are using may attempt to access files in the bin folder directly. If this is the case, you can simply create a folder named 'bin' in the .minecraft folder where they are looking for it, and add the files the mod needs in there. The mod should find the files, and carry on as it used to, not knowing the difference.
Seeing as none of the answers so far have covered this, it is now possible to do it. For a long while now, APIs such as Forge have transitioned to the new layout for quite some time now, and Forge especially has its own installer that you can use to automatically drop a modified .jar archive already prepared to be used.
There is a way. Go to your .minecraft folder, go into versions and click 1.6.1 then add a .zip file extension to 1.6.1.jar to make it 1.6.1.jar.zip. Double click it, then drag the mod files into the folder called 1.6.1.jar.
Ive been having a really hard time trying to solve what is causing my minecraft forge to crash when attempting to play, immediately after i press play it crashes. I deleted all my mods and currently have none in my mods folder so i know it has nothing to do with outdated mods or mods in general, its forge. I can still play vanilla minecraft.
It is still not working for me too unfortunately, and i have tried reaching out directly to get support from forge off of the curse forge website but they did not help and instead redirected me here again where my problem remains unsolved, id appreciate it if someone could reach out to me and help, as many others i have encountered online are having the same problem .
c80f0f1006