at .lambda$checkModsOnCurseForge$67(InstanceInstaller.java:1920) at .WindowsFileSystemProvider.newByteChannel(WindowsFileSystemProvider.java:230) at .WindowsException.rethrowAsIOException(WindowsException.java:102) at .WindowsException.rethrowAsIOException(WindowsException.java:97) at .anslateToIOException(WindowsException.java:79) I don't really know what I'm looking for other than red text. It's a rather lengthy one so I'll try to record the relevant bits if I can, but I may miss something. Trying this resulted in a crash and a new report. If that doesn't work I'll try to replicate your situation, see if maybe it's a problem with how optifine 1.17 is formatted maybe? Maybe try this? It could be the issue, though if so it's a new one, as Optifine has always worked with AT for me There's kind of a third option - the add mod GUI has a button to add from a jar file - you can use this to target your optifine jar, which will make it show up in the UI. Method 2 is to use ATLauncher's interface to search, download, and install mods - the 'add mods' button (I think?) Will bring up a window that searches through curseforge for mods, and will handle MC versions and mod dependencies for you - then you just download and they get put in your mods folder just like if you did it manually - the only difference is that this way, ATlauncher "sees" the mods, and they get added to the list, where they can be enabled/disabled/etc There's basically two different ways to 'install' mods into a pack - you can manually download jar files and then drop them into your instance's 'mods' folder - when forge launches it scans the whole folder, so anything valid in here should work.īut if you install them this way (which I've been doing for years, it's completely viable, just a little less user-friendly perhaps), the mods aren't actually registered by AT as part of the pack - I assume it doesn't scan the folder, it just keeps track of what mods are added/removed through method 2. I'm similarly afc right now, so can't do testing of this myself, but I can explain why the mods aren't showing up in instance settings. If the manual install fails, you might have a corrupted or bad file try re-downloading, and make sure you get it from the legit site () This should sidestep the issue if I understand it correctly. You should also try running ATLauncher as admin, which can help with permissions issues - admin alone might do it, but you might need to launch as admin AND move the file.Īlternatively, just open your instance folder (should be a button in the instance interface, or just navigate there in windows) and drop optifine into the mods folder manually (it might need to be in jarmods, but it's always worked in mods for me). It could be a permissions issue where ATlauncher doesn't have access to files on the desktop (doesn't strike me as likely but it's easy to test/fix) - try putting optifine elsewhere, like downloads or preferably somewhere within atlaunchers install folder (just to see if this is the problem, if so we just change permissions for the desktop). Failed to get contents of file in C:\Users\Alex Chaney\Desktop\OptiFine_1.17.1_HD_U_G9.jar. Showing splash screen and loading everything Operating System: Windows (10 (Home) build 19042) CPU: AMD Ry6-Core Processor 6 cores/12 threads GPU: NVIDIA GeForce RTX 2060 (NVIDIA (0x10de)) DriverVersion=27. I'm also pasting a copy of the log below: java.io.Title describes the issue reasonably well I think. Error trying to download scala-actors-migration_2.11-1.1.0. Error trying to download scala-reflect-2.11.1. java.io.IOException: request wasn't successful: Response at .execute(())Īt .downloadFile(())Īt ($n)(())Īt .runWorker(Unknown Source)Īt ($n)(Unknown Source)Īt ()(Unknown Source) Error trying to download scala-continuations-plugin_2.11.1-1.0.2.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |