Jump to content

Pyker

Forum Administrators
  • Posts

    53
  • Joined

  • Last visited

  • Days Won

    12

Everything posted by Pyker

  1. This is a known bug, but it does mean that you're trying to login with a Mojang account that doesn't have Minecraft Java edition. Did you migrate your Mojang account to a Microsoft account, or are you using the wrong account?
  2. That's good to know. However, with the most recent version of the launcher, it should use the Mojang Java (which is 16 for 1.17). It might require you to reinstall the modpack (modpack settings -> reinstall).
  3. Again, we can't help you. Platform is working correctly, I can't access your sky.rdnx.nl link either. Maybe it only works from inside the Netherlands?
  4. These updates have now been pushed to the stable channel. The workaround to set it up is no longer necessary (just download the launcher from the website). If you want, you can switch to the stable release channel in the launcher settings.
  5. A bug in build 628, that resulted in Minecraft crashing with a GSON exception every time you tried to launch a modpack with a Microsoft account logged in, has been fixed. If you restart the launcher (in the beta stream) you'll receive the update to build 629.
  6. The reverse engineering and finding bugs part is right. Also, we have a beta release now. It's a bit hacky to set up, since you can't really get into the launcher proper without logging in first. So: Download the launcher and run it Open %AppData% (you can just type this in the Start menu), go to .technic and open the settings.json file (Notepad works) Change the buildStream entry from "stable" to "beta" Restart the launcher You should now have the beta release, which allows you to login with Microsoft accounts Please post any feedback in this thread.
  7. Migrations haven't begun yet, so unless you bought your account on or after December 1st 2020, then you still have a Mojang account. Sometimes Mojang's auth server will also somehow fail to realize you do own Minecraft, which is... weird, and rare.
  8. If I had to guess, it's one of the Sky Factory 4 modpacks I recently deleted, since they got reported by the actual Sky Factory 4 team. That specific modpack has also only been there for 2 months.
  9. Can we please be civil? I understand that everyone is upset with the delay on support for Microsoft accounts (myself included), but it's really close to being a thing.
  10. The Microsoft login support is currently being developed and cleaned up.
  11. I will simply leave this here: https://help.minecraft.net/hc/en-us/articles/360035130511-Minecraft-on-Chromebooks
  12. You don't. A ChromeBook isn't capable of running modded Minecraft (and probably not vanilla Minecraft either).
  13. This is no longer an issue for Technic Platform. Currently we have no way to switch over the forums.
  14. I think legally it would be very very complicated for them. I'm just annoyed they started working on something and gave up halfway, but at least they're not saying third-party launchers aren't allowed, just that we're on our own.
  15. An update: Mojang/Microsoft just changed their stance on third-party launchers. Previously, they said they were working on a solution to allow third-party launchers to authenticate with their new login system (Microsoft accounts), but now they have decided to drop any support for that entirely, and are instead relying on us to roll out our own support. https://help.minecraft.net/hc/en-us/articles/360050865492 With all this said, we already had a backup plan in mind, and we'll start working on that so everyone can use Technic once again, regardless of having a Microsoft account or not.
  16. Here's how to add Fabric to a Technic modpack: https://fabricmc.net/wiki/tutorial:technic_modpacks
  17. The guru3d link has been fixed now.
  18. We're aware of how the Curseforge launcher works (with embedding the vanilla launcher), but that's a *really* fragile solution and it resulted in some very broken functionality.
  19. You are literally asking us to transform our legitimate launcher into an illegal, cracked launcher. You can probably see why we won't do that.
  20. As far as I know, Microsoft/Mojang are working on this. We're still waiting, but if nothing comes soon then we might have no option but to roll the reverse engineered stuff. We already have people who are unable to play Technic packs because new accounts are MS accounts, so I definitely understand and share your frustration with this.
  21. We're not going to turn our launcher into a cracked launcher.
  22. If you're trying to login on Technic Launcher, then you need to use your Mojang account credentials, just like you would use in the vanilla launcher or minecraft.net. Technic Platform is separate from the launcher (playing Minecraft vs publishing a modpack on Technic).
  23. We're also stuck waiting for Microsoft and Mojang's solution for third-party launchers. There are other launchers that have implemented a solution for MS accounts, but it's based on reverse-engineered information and we could get a Cease & Desist from Microsoft if we went down that route.
  24. The issue is exactly that you're trying to allocate more RAM than your computer has available (not total... available). Other stuff running in your computer also takes up RAM. > There is insufficient memory for the Java Runtime Environment to continue Lower the amount of allocated RAM to something like 6 GB (given this is quite a beefy modpack) and see if that works.
×
×
  • Create New...