Well, that didn't work. Would Java have something to do with it not starting up? Had Task Manager going when I tried the Launcher and saw Minecraft pop up (then close up a few seconds later), but not Java (and it's always started up when I start MC)
I don't know if Java has anything to do with it but I do know there was an update to Java recently. Maybe try it?
Okay. gonna do a complete fresh start of MC, with Java updated. Don't know what else to do if that doesn't work.
That's what I get when I try to start. Even got that before the complete fresh start and updating Java to the latest release.
Based on the path of the first error message, it looks like you're using the new launcher. If that's the case, try downloading the old launcher (which is better ) by logging in on minecraft.net and see if it works. I hope it works so you can be in-game again. It's been too long.
That didn't work. Gonna try using the FTB Launcher as a work-around. If that don't work, I really only have two options left. One's to get a copy of the files in another person's MinecraftLauncher folder and the other option is the 'nuclear' option, a full PC reset and re-installation of the OS.
That's not enough for the nuclear option--you will probably have to burn your PC in a pit outside, legally change your name, move to another country and set up a new life there At that point I'm assuming MC will let you log in
OH GOD!!! I hope not. I got a good thing going here (besides not being able to get onto MC, of course).
well, FTB didn't really work out too well. However, I did manage to pop onto the server via the Vanilla MC option on the Technic Launcher. Still gonna try to get the MC Launcher to work, but at least I still have a way in for now.
I'm having trouble myself. After I launch, I get a Code 1 error without a log. I'm using Fabric Loader 1.19.2 with all mods in the Mod folder updated to 1.19.2 (I did make a copy of the old folder just in case). When I go back to 1.19, I get your outdated message.
Could you share what mods you have installed? Cross-reference that they are on the approved mods list: https://mods.emc.gs/ A "Code 1 error" isn't a server side error. You could try taking out all of the mods and add them back one at a time to identify which one is causing your issue.
Here's my list: architectury-5.12.42-fabric badpackets-fabric-0.1.2 balm-fabric-4.3.0+0 BetterF3-1.3.2-Fabric-1.19 c2me-fabric-mc1.19-0.2.0+alpha.8.2 charmonium-fabric-1.19-4.1.0 clickthrough-1.19-fabric0.53.3-0.4 cloth-config-8.0.75-fabric continuity-2.0.1+1.19 craftingtweaks-fabric-1.19-15.0.1 cullleaves-2.3.4 custom-crosshair-mod-v1.5.0-fabric-mc1.19 dynamic-fps-2.2.0 easiercrafting-1.19-fabric0.53.3-1.7 enhancedblockentities-0.7.1+1.19 entity_texture_features_fabric-4.0.1 entityculling-fabric-1.5.2-mc1.19 fabric-api-0.60.0+1.19.2 fabric-language-kotlin-1.8.3+kotlin.1.7.10 ferritecore-5.0.0-fabric indium-1.0.9+mc1.19.2 inspecio-1.4.2+1.19 InventoryProfilesNext-fabric-1.19-1.7.0 iris-mc1.19.2-1.2.8 krypton-0.2.0 lambdynamiclights-2.1.2+1.19 lithium-fabric-mc1.19.2-0.8.3 malilib-fabric-1.19-0.12.1 midnightlib-0.5.2 minihud-fabric-1.19-0.22.0 modmenu-4.0.6 notenoughcrashes-4.1.6+1.19-fabric PetOwner-1.8.3-1.19+ qfapi-4.0.0-beta.9_qsl-3.0.0-beta.14_fapi-0.60.0_mc-1.19.2 reeses_sodium_options-1.4.7+mc1.19.2-build.59 smoothboot-fabric-1.19-1.7.1 sodium-extra-0.4.10+mc1.19.2-build.64 sodium-fabric-mc1.19.2-0.4.4+build.18 starlight-1.1.1+fabric.ae22326 WorldEditCUI-1.19+01 worldedit-mod-7.2.11-beta-01 wthit-fabric-5.11.3 Xaeros_Minimap_22.13.2_Fabric_1.19.1 I'm also using the following resource packs: 2000Leagues_1.19 2000Leagues_mobs_1.19_1024x All of the 1.19 versions worked fine, just not the 1.19.2 versions.
An update went out overnight to release the Labor Day items. But we are also trying a change to fix shulkers randomly despawning.
Take your time with that one, my friend. I'm sure there's a lot to fix for getting THAT to work properly.
