Invalid GUID

[liliff]

Delete all lines containing 'proto' in the autogen.cfg. That fixed my problems.

edit: I deleted the seta protocol 85 from the autogen.cfg file and I was able to get to the NA server. However, I get message stating that the name belongs to an admin, Electric Monk, which is me.

Deleting it isn't really the correct solution, updating it to 86 is - though unv does that for you anyway.

KoR's server is still on 85. If you get a new list it'll show you the servers you can legitimately connect to.

[JOURNEYMAN]

Yeah, /seta protocol 86 is probably more elegant way of fixing the problem. :)

[ViruS]

Known issue.

Maybe get the installer [optional] to fix the protocol to the new value?

Btw, master.unvanquished.de needs to update as well...

[danmal]

The protocol isn't loaded from the config file anymore. This bug shouldn't happen again.

[Forty-Two]

I get 'Invalid pubkey' on every server I try to join with protocol 86 :P

[Ishq]

Your pubkey is probably corrupt. Delete the pubkey file in ~/.Unvanquished/main/profiles/<your profile>/pubkey

[ViruS]

I deleted the guid, and now it says 'Your guid is insecure'... hmmm.....
[quote][/QUOTE]
Edit: Works now.

[Forty-Two]

I've deleted C:\%appdata%\Daemon\main\pubkey, C:\%appdata%\Daemon\main\guid, C:\%appdata%\Daemon\main\profiles\Forty-Two\pubkey and C:\%appdata%\Daemon\main\profiles\Forty-Two\guid, but unfortunately I still get the same message :/

Console output normally:

Code: Select all

Hunk_Clear: reset the hunk ok
Loaded 2 language(s)
----- Client Initialization -----
Daemon GUID public-key found.
Daemon RSA public-key found.
----- Client Initialization Complete -----

Console output after deleting all that (the pubkey and guid don't come back in main by the way, I'm guessing it's because it loads a profile by default?):

Code: Select all

----- Client Initialization -----
Daemon GUID public-key generated
Daemon RSA public-key file not found, regenerating
Daemon RSA public-key generated
----- Client Initialization Complete -----

[Forty-Two]

For anyone who has the same problem: I got it with the 0.6 .zip. I went to the download page today and saw there was now an installer: I installed through that, and now it works fine. I had to manually add pakX.pk3 files, but worked like a charm for the rest.

Now that I've played a bit, I'd like to congratulate you on this, it seems really cool :D