I wrote a new server for our patchbot to connect to (since the old one was painfully slow especially when overloaded), so i figured a good way to test it before pushing it on everyone would be to make it be used by the beta client.

At the same time, ill make i much easier to stay updated on the beta client (and easier to install too). Keep in mind that for now there is no automated system that ensure beta is more recent than release. So on live patch, it may happen that beta client end up outdated and you need to run the normal client until beta get an update. Once i switch live client patch server to the new one, ill link them both so that beta will use the live client repository if its more recent.

tldr; for now even if you want to permanently use the beta client, keep a live client installed somewhere so that if i forget to update the beta client on a live patch, youll be able to play .



This is a micro install, as in, the installer only contain the patchbot and will download everything from the patch server on first start. If you want to avoid wasting some precious bandwith, then you can do so by canceling the patchbot after install. Copying your ss2 folder in the beta one, then reinstall the beta over it (or run the patchbot if you made sure to not overwrite either patchbot.exe or patchbot.ini).


in a soon to be future, the beta client will know if there is a new version available and run the patchbot automaticly just like live client does. But for now, i added a check for update button in your start menu, i encourage you to press it a from time to time to get the newest beta if available (and help test the patchbot server at the same time).


Just a lil bit of random info, the old patch server could answer about 8-10 client per seconds on cache. The new one clock in the 5000-8000 answer per second, so it should be able to handle itself just fine even under heavy load.


Edit: 3/20/2012 new beta installer attached. Its required to patch your patchbot due to a bug in the old version that broke the self patching. The crash on first install is also fixed.

Wow this is really impressive. Just started running patchbot and I didn't even see the communicating screen it was so fast, which is a first for me (as its taken so long I've made a gif of it before )

Oh, :/ It crashed when it made it to 12,13/13. I'll send the dmp now.

yea, the communicating part is the part where you wait after the server. so considering this one is about 800times faster on cached answers.

Offcourse, if the server need to generate new cluster file and whatnot, it wont be in the ms delay before answering, but its still pretty darn fast (and everyone after you wont need to wait unless they required their own cluster as well).

please do. im staring at my inbox !

Crashes, sending 2 dmps

thanks for the dmp, i found a way to reproduce the issue and am now working on fixing it, in the meantime, simply rerunning the patchbot work to finish downloading (it will resume close to where it was when it crashed).

new beta installer (youll need to install it to update patchbot, there was a bug in the self patching code). It wont redownload what you already had so no big deal .

Thanks Jey, it works perfectly now.

Jey, I just want to say.... you are freaking awesome! Finally got my computer to stop denying the download of the beta client, for the first time in 2 years, I can get on SS at college without using the tunnel, not to mention my fps in dging went from like 20s max to 60s. It's amazing!

Maybe I'm doing this wrong, but doesn't running this completely overwrite your current beta client files?

this is only a micro install, installing this will overwrite your patchbot.exe, patchbot.init and star sonata.exe. You only need to install it once, after that, the "check for update" option in the start menu for star sonata 2 beta is what you need to run to obtain the lastest version (well, nothing stop you from rerunning that installer everytimes).

Mine stopped responding after I had logged in.

Showed the characters, and clicked my character and it stopped responding.. :/

using the beta i went to warp into copper and i crashed upon entry and everytime i tried reopening beta and logging on that char and it just crashed right away, i had to get on the old way to be able to get that char outta copper