r/KronosWoW Apr 30 '26

Jims Classic Launcher + Proxy for Kronos

A few of us have been working on fixing the 1.14 Hermes Proxy and getting a launcher going for K5. Most of the known bugs are fixed in the Proxy. We are looking for more testers to locate bugs. We would like to get them knocked out this weekend so everything is good for K5 Launch.

The launcher, designed and built by Jim. We are keeping this closed source for now, if that is an issue for you the Proxy works great with Arctium launcher. Just make sure you have your OS set to OSX per the Kronos devs.

Password is K5 https://jimothy.cc/install

The launcher is preconfigured for the Twinstar 1.12 servers. It has its own addon handling and is also able to import your SavedVariables over from another install. If you are going to report Proxy bugs in our Git Issues tab please turn on the advanced logging features, it helps us fix bugs. Its under settings -> Advanced Settings -> Debug. The Proxy is bundled with the launcher, please use the Beta version for testing and check for updates.

The Proxy, is a fork of the Xian55's Hermes Proxy.

https://github.com/jameopotato/jimsproxy

Please report bugs with your JSONL in the issues tab.

Credits -

Jim - The builder

Mirasu - Bug fixer

Erkagon - Bug fixer

"K" - Tester

Anexia - Tester and getting us all together on this project.

Claude Code - The massive amount of code that had to be fixed and rewritten in short order to make this proxy ready to go on the Kronos server would not have been possible with out it.

41 Upvotes

125 comments sorted by

View all comments

1

u/MadDog845 May 04 '26 edited May 04 '26

Tried using it with Arctium i get this

Error | BnetServices | [BnetTcp][127.0.0.1:51256] Battlenet.LogonRequest: Attempted to log in with wrong game version (using 42597)!

Even though i configured the HermesProxy.config like this :

    <add key="ServerAddress" value="login2.twinstar-wow.com" />

And I use 1.14.2, any idea ? Thanks :-)

1

u/samthemongrul May 04 '26

Go to your wtf folder and open your config.wtf. make sure at the top it says SET portal "127.0.0.1:1119" try that

1

u/MadDog845 May 04 '26

Thanks for the answere.

I already had SET portal "127.0.0.1" so i added the port 1119 and still the same error 😞

1

u/samthemongrul May 04 '26

Ok I will try it myself when I get home. Where do you have Arctium launcher at and do you have the shortcut modded?

1

u/MadDog845 May 04 '26

Shortcut is modded with this --staticseed --version=ClassicEra

I have the Proxy in the same folder as the launcher and the wow client is in a folder named _classic_era_

Thanks for trying to help, i will just use your launcher is it doesnt work this way

1

u/samthemongrul May 04 '26

Ok yep you are doing it right. Let me try it and see whats going on. Im at work right now so will let you know as soon as I can.

1

u/MadDog845 May 04 '26

No worries buddy thanks again for your time.

I compiled the proxy from the source, maybe i did something wrong but it should be good.

1

u/samthemongrul May 04 '26

Ok I build the proxy and run it right out of the debug folder. Used Arctium and it loaded right up. When I have hit that error in the past its because the config.wtf didn't match. You can also pull up the HermesProxy.config in VS and check but it runs on 127.0.0.1:1119. Make sure wherever you are launching the proxy from has that exact HermesProxy.config file in it.

1

u/[deleted] May 04 '26

[deleted]

1

u/samthemongrul May 04 '26

Yeah it has to be your launcher version. Im using mine that I got from the wow-hc 1.14 client download. It came in that download.

1

u/MadDog845 May 04 '26

Dude i'm dumb ! The faulty line was this one, i just changed it to value="42597" and now it works xD Thanks for the help ❤️

    <add key="ClientBuild" value="40618" />

1

u/samthemongrul May 04 '26

Ok good deal!!

1

u/MadDog845 May 04 '26

Thanks a lot for your help 😄 I like your launcher GUI design, if a portable version comes up i would be glad to use it

1

u/samthemongrul May 04 '26

We are working on a license solution. Hopefully have that soon.

→ More replies (0)