1.7.2 / Can't connect to any 1.7.2 server.

  • The FTB Forum is now read-only, and is here as an archive. To participate in our community discussions, please join our Discord! https://ftb.team/discord
Status
Not open for further replies.

Lomsor

New Member
Jul 29, 2019
2
0
0
Dear FTB support team,

Operating System, bit type: Windows 7, 64
Java version/update, bit type: 1.7.0_45, 64
Launcher version: 1.3.4
Completed the troubleshooting guide (y/n): no, singleplayer works
Console log, pastebin.com link: http://pastebin.com/aruXMbGV
Description of the problem:

Now that Launcher 1.3.4 is officially released I can file my bug report.

Before 1.3.4 Minecraft 1.7 wasn't downloaded correctly by the launcher (it used the pre 1.5 system).
Now that works though, so good.

I have been in contact with Watchfull11 to get my new 1.7.2 modpack onto the FTB launcher. While trying to get that working we discovers some bugs. That lead to Watchfull11 actually fixing one of them in the source on github personally, the fix has been applied with the just released 1.3.4 Launcher. It was the bug mentioned in the paragraph above.

TLDR:
Now I hit another bug that seems to go deeper. When using a 1.7.2 modpack on FTB you aren't able to connect to any "online" non cracked server. This includes non modified 1.7.2 servers. The error that appears is following:
"Failed to connect to server
Failed to login: Invalid session (Try restarting your game)"
Restarting doesn't help. The logs don't show anything ether ... take a look here: http://pastebin.com/aruXMbGV
Any other non 1.7 (so all others) work though. Including 1.6.4. I have tested it on modified and non modified servers.

I'm aware that you state that you won't provide a lot support for custom modpacks. Though I believe this problem would applie to any 1.7 modpack on your launcher. I think I'm the first one to have a 1.7 modpack on the FTB launcher. So sadly I personally can't test if the problem is with the modpack. As the modpack works perfectly fine in multiMC I assume it's a problem on the launcher side.

I bring this up so the issue can be fixed before the big Modpacks switch to 1.7.

(and of course I want to see my modpack work too ...)

Tell me if you need any more information.
I hope we can help each other out.

Greetings,
Lomsor
 
Last edited:

lavarthan

New Member
Jul 29, 2019
2,437
0
0
[INFO] LaunchFrame.main:199: Launcher Install Dir: C:\Program Files (x86)\Minecraft\FTB
1.7.2? When did the mods update to 1.7.2 yet? When was the launcher ever setup to download minecraft 1.7.x?

I also see a problem with your installation. It is never recommended to run the launcher from within the Program Files folder. You would have to log in and be an admin all the time and that is not recommended. Even then you will probably run into many problems with that setup.
 

Tristam Izumi

New Member
Jul 29, 2019
1,460
0
0
I came in here thinking "there aren't any 1.7 packs out yet...", now I'm trying to figure out how short a list of mods you have put together.

Also, you definitely know more about this bug than most of us, and I'm sure that Watchfull and the launcher devs are happy to have you testing this stuff. Good luck!
 

Lomsor

New Member
Jul 29, 2019
2
0
0
I didn't know how much communication went from Watchfull to the actuall devs of the launcher.
Now that the launcher is officially 1.3.4 (I was allowed to try 1.3.4 before it was official) I wanted to file the bugreport trough official channels just to make sure the devs know of the bug.

Also yes. I'm always logged in as admin. And yes that's ok with me. No pw, no other users. Preference.
 

lavarthan

New Member
Jul 29, 2019
2,437
0
0
Also yes. I'm always logged in as admin. And yes that's ok with me. No pw, no other users. Preference.
I was more worried about the other programs and viruses and such that could possibly run as an admin since you are logged in as an admin. Though I'm glad you are testing it for them. Please forgive my assumption that you were someone who did not know what they were doing.
 

Ashzification

New Member
Jul 29, 2019
7,425
1
0
This is not a Tech Support issue. There are not any official 1.7.2 packs. 1.7.2 is still in beta functionality (see line 110: LiteLoader> Active Pack: Development version (NOT FOR RELEASE))

I won't class this as a launcher bug just yet, since there is not yet any reason for FTB to support 1.7.2. This support will come when there are either a. official 1.7.2 packs, or b. there is a "vanilla pack" added to the launcher.

Also, all private packs are to be reported to the pack creator, as they are responsible for any issues that occur with their packs. Since you're the creator, it's your issue.

As the current focus is on 1.6.x functionality, I'll leave this to @progwml6 to investigate any launcher-side problems.

Locking this, unless I'm told by someone higher it should be unlocked.
 
Status
Not open for further replies.