Konduit

Konduit has been retired as of 2019.
Thank you to everyone who made it what it was.

[Konduit @KonduitLauncher]

Konduit is now on Discord! Come say hello! https://t.co/Hpsg1YsKYJ

[Konduit @KonduitLauncher]

@tonkkis That fix is now live.

[Konduit @KonduitLauncher]

@tonkkis There's an issue with that that I am currently deploying a fix for. It should be live in a minute and I will send a tweet about it.

[Konduit @KonduitLauncher]

@SEAN878_ What don't you like about it? Do you want antialiasing? It should be pretty standard, and the way I've done it should be as beneficial for performance as possible.

[Konduit @KonduitLauncher]

@MAJonaiker I had to disable zoom earlier due to an issue that appeared in today's game update— I'll be fixing that ASAP (today) and re-enabling it.

[Konduit @KonduitLauncher]

@DiamondFluxify Indeed, the update yesterday changed an interface ID we had used for the bank. This is fixed in 2.19.1, which I will be releasing ASAP (I'm currently working on other features that will be included in that release).

[Konduit @KonduitLauncher]

@On3TwOrs I'm aiming to get 2.19.1 (which will include discord) out today, but there are still a few things I've left to do. It will either be tonight, or early tomorrow.

[Konduit @KonduitLauncher]

@Deadloxx That is strange, did it end up doing anything at all? If you close out of the client and attempt to launch it again, does it still hang at 99%?

[Konduit @KonduitLauncher]

@sirotacsip An update to our internal configuration system will be coming in 2.20. I don't have an exact timeframe for when that will be released, but it will address the issues you're talking about.

[Konduit @KonduitLauncher]

@JONBOY847 Do you have "Fallback mode" enabled in your Launcher settings? You would want to disable that if so, as it would cause it to launch a default, unmodified client (as you are experiencing).

[Konduit @KonduitLauncher]

@Glvco I was unable to reproduce this issue, and as you have mentioned that it is not exclusive to Konduit, I have to imagine it's something on your end.

[Konduit @KonduitLauncher]

@jonnymcbee It's possible that instead something went wrong with your session token; you can try closing all clients, and then closing and re-opening the launcher (you should see the sign-in screen again). If that was the problem, it should load the client properly when you launch one again.

[Konduit @KonduitLauncher]

@jonnymcbee Weird, you don't happen to have fallback mode enabled in the Launcher's settings, do you? The client would seem to not be downloading any of its additional files, so it just starts up a default, unmodified client (which is what fallback mode is intended to do).

[Konduit @KonduitLauncher]

@HershAttal In their case it was Java 8 update 101 that solved their problems, but it is likely that all versions before some point were OK. Some time soon I will try to use a macbook (or a mac VM) and diagnose these errors myself; it seems that something in newer Java versions is causing it

[Konduit @KonduitLauncher]

@HershAttal Unfortunately I do not have a macbook myself, so I have not been able to examine this issue firsthand yet; I only have secondhand observations from other users who were describing similar problems. In one of their cases, reverting to an older Java 8 version solved their problems.

[Konduit @KonduitLauncher]

@On3TwOrs Indeed there will be, very soon.

[Konduit @KonduitLauncher]

@Haukirs I had never seen the need for it, but considering that a majority of other clients have it now, I would not be against adding it.

[Konduit @KonduitLauncher]

@SirRock24 There should be a setting labelled "Use custom points overlay" under the raids settings, have you disabled that? This was added earlier today; the old points overlay should show up when doing so.

[Konduit @KonduitLauncher]

@trinity_rose You could also open a command prompt in the folder where the KonduitLauncher.jar is (hold shift and right click with no file selected, click open command window here) and run "java -jar KonduitLauncher.jar". This may give you a more detailed error message (and it won't disappear)

[Konduit @KonduitLauncher]

A new build has been released to address an issue in today's earlier release that could occur when clients start up in fixed mode. (This issue would have caused most game overlays to not be visible.)

[Konduit @KonduitLauncher]

@trinity_rose Strange, that error would indeed imply that it's not an executable jar file. It could be the file, but I don't think that's as likely. Could you open a command prompt and run "java -version"? I have a feeling that it might not be finding the correct version of Java by default.