PlanetTeamSpeakk/DevLogin

1.16.5 No pop up

Closed this issue · 2 comments

I don't get any errors part from mixer complains you never set a min version but I don't get the pop up and it just locks up.
I believe the problem is I am using a tool that is capturing the console window and for some reason it's not poping open, unless the pop up is meant to happen in the client then I can't see what would be blocking the login pop up.

This is happening with 3.1.1 and I testing it on 1.16.5 minicplayer worked though.

I think it's waiting for the pop up or something though as it locks up here

image

I was able to grab a error

[main/DEBUG] [mixin/]: Mixing MixinMain from forge-devlogin.mixins.json into net.minecraft.client.main.Main 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052 java.lang.NoSuchFieldError: f_91002_ 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at forge.com.ptsmods.devlogin.MSA.showDialog([MSA.java:451](file://forge.com.ptsmods.devlogin.msa:451/)) 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at forge.com.ptsmods.devlogin.MSA.lambda$reqTokens$2([MSA.java:133](file://forge.com.ptsmods.devlogin.msa:133/)) 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at forge.com.ptsmods.devlogin.MSA.lambda$doRequest$15([MSA.java:428](file://forge.com.ptsmods.devlogin.msa:428/)) 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at java.util.concurrent.ThreadPoolExecutor.runWorker([ThreadPoolExecutor.java:1149](file://java.util.concurrent.threadpoolexecutor:1149/)) 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at java.util.concurrent.ThreadPoolExecutor$Worker.run([ThreadPoolExecutor.java:624](file://java.util.concurrent.threadpoolexecutor:624/)) 
05:27.49 [pool-3-thread-1/INFO] [STDERR/]: [java.lang.ThreadGroup:uncaughtException:1052    at java.lang.Thread.run([Thread.java:750](file://java.lang.thread:750/))```

I cannot replicate this issue, however, you can now disable the dialog using the --msa-no-dialog program argument.