Jump to content

Recommended Posts

Posted (edited)

Hello,

 

I've recently been working on a 1.7.10 version of my modpack Technolution.

 

All is going well, but I've been having problems with the new Twitch integration.

TQRXvdl.png

 

It does not detect that my account has been linked to Twitch, while it definitely is linked and working in vanilla 1.7.10. (With vanilla launcher).

 

chJt0i7.png

 

I am not sure if this has something to do with the way Technic handles accounts, It's disabled in Forge or some mod is interfering.

 

Forced crash for system info & mod list on Pastebin.

 

My question is what is causing Twitch streaming to break and how can I resolve it?

 

 

EDIT:

Twitch integration works for me with:

  • Vanilla launcher 1.7.10
  • FTB Launcher Unstable modpack 1.7.10

 

And doesn't work with:

  • Any Technic launcher pack for 1.7.10 (Also the launcher's vanilla pack)
Edited by jwa1
Posted

I don't have my client handy, but have you tried the vanilla pack in the launcher and see what it does?

If you can get it working with the vanilla pack, try just vanilla + forge.

  • 2 weeks later...
Posted

jwa1 - the only suggestion I can offer atm is to pull mods one by one until the issue is resolved, with whatever mod that was pulled last being the culprit.

Posted (edited)

jwa1 - the only suggestion I can offer atm is to pull mods one by one until the issue is resolved, with whatever mod that was pulled last being the culprit.

 

This also happens when I play vanilla Minecraft through the Technic launcher. (As stated in the OP)

So this has nothing to do with mods.

Edited by jwa1
Posted

It doesn't work in vanilla minecraft? I seem to misunderstand this bit then:

 

 

It does not detect that my account has been linked to Twitch, while it definitely is linked and working in vanilla 1.7.10. (With vanilla launcher).

 

Posted (edited)

I mean that it works fine with vanilla Minecraft with the standard vanilla launcher. (WORKING)

 

6TCBGCu.png

 

 

 

It also works fine with the FTB 1.7.10 modpack. (WORKING)

 

P0yjX5H.png

 

 

 

But does not work with the vanilla pack through the Technic launcher. (NOT WORKING)

 

ijtSZud.png

 

 

 

Also does not work with any 1.7.10 modpack through the Technic launcher. (NOT WORKING)

 

TNVfuey.png?1

Edited by jwa1
Posted

Ah, okay, I understand now. My only suggestion then is to take a look at any security software you may have. The technic launcher and in general doesnt change anything that is supposed to be there with vanilla minecraft (and even downloads the vanilla minecraft jar for a modpack if it needs to for the version, if it isnt already downloaded) so all internal integration shouldnt be modified at all. It's possible that because its being ran through a launcher that security software may be picking it up as untrusted or otherwise seeing it as "bad" and stops the outgoing connections.

Posted

I am using AVG Free edition, I have added the .technic folder as an exception to the security shield. Also I tried unlinking my Twitch account and then linking it again to the Mojang account.

 

Still no success.

 

 

Is it working for you?

Posted

Let me grab the modpack you mentioned here and I'll give it a go to see if it is working for me. If it is, then its definitely something local. Also, there's more to add to the exceptions list than the folder. There's the urls as well (technicpack.net, minecraft.net and twitch.tv) - not to mention theres also the windows firewall (or macs firewall), router/modems that can also be getting in the way. I'll edit this post with a success/failure and let you know my result.

Posted

Oh, alrighty then. Btw, whatever happened to version 1.04 to 4.02 of that modpack? Lol, noticed the jump and lack of #'s...and also, that saturn packs launcher bg image.....am not a fan, not a fan at all..

Posted

Migrated to a mojang account, linked twitch, not working. Adding explusions for all relevant files, folders, and URLs don't change it.

 

Guessing there is something wrong with how the launcher deals with a mojang login, or mojang has a block setup for the launcher for that particular feature for some stupid reason.

Posted

Yeah, I'm running into the same result Neowulf. Talking to jwa1 via skype right now. I even attempted to change JVM args to see if i could get it ran. But for some reason it just isnt. Even tried the newest forge version in the event that was doing something, it showed no difference. And changed the --username arg that is sent to be my email address since I have it setup and that failed to work too. Compared the vanilla and launchers JVM args too and i see no difference in jar associations that it needs, theres a few minor JVM arg differences but those are performance/java related and have no end effect on communication.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...