Quote:
Originally Posted by damianpesta
Korvac i did everything what u wrote up there ................ Nothing works still Connection to the server is interupted please relog in... well like i said i think thats the database and start.cs cause the client connects to the database and sends password md5 but i didnt change the code in start.cs to send the md5 to database so ... i really dunno whats going on and sorry for double post :/
|
did you do all of this?
Also for all people receiving the 317/318 error:
Change your database type from 0 to 1, a noob error on mine and futures part,
Quote:
|
Originally Posted by Walos
Ok if you get try to log in and get an error similar to this
Code:
System.NullReferenceException: Object reference not set to an instance of an object.
at COServer.Start.Game_FirstDataArrived(Object sender, DataArgs e) in CoFuture_ReleaseServerStart.cs:line 317
which should be one of these 2 lines
Code:
COClient Cli = ((COServer.AuthServerPackets.AuthRequest.AuthBinder)GameClients[e.Conn]).Client;
string User = Cli.Account + ": " + Cli.Char.Name;
and get the Error: Connection with Server is interupted. Please re-login. on your client
make sure in your account table auth is set to 1
eg
Code:
AccountID Password Type Auth Address
NewChar 0 1 NULL
Also make sure tha the password field is blank
Changing the Auth to 1 and having a blank password try to log in again and now you should have the create char screen on the client
If you get
Code:
System.NullReferenceException: Object reference not set to an instance of an object.
at COServer.Start.Game_FirstDataArrived(Object sender, DataArgs e) in CoFuture_ReleaseServerStart.cs:line 317
and get to the create char screen of the client then what i think is happening is that it is connecting you to the game server without first making sure that there is a row in the character table (CharID) with the same accountid as in the account table. CharID == AccountID.... This will raise the exception but allow you to create the char.
After you successfully created the char you should be able to login and these error will not appear for that account/char
I hope this helps the thing to make sure is that Auth is 1 and password is blank
Cheers
Walos
I Have had a bit of a look through this again and if you change this in start.cs
Code:
string User = Cli.Account + ": " + Cli.Char.Name;
ClientList.Items.Add(User);
to
Code:
if (Cli.Status != Mode.CreateCharacter)
{
string User = Cli.Account + ": " + Cli.Char.Name;
ClientList.Items.Add(User);
}
Assumming that Auth is set right in the account table you shouldnt see this error again.
Its caused when you are creating a new Character as Cli.Char does not exist yet
Cheers
Walos
|
also, its not an md5 hash, conquer uses its own encryption and decryption of passwords which is why the hash is stored in the database, not plain txt.
and im not going to post a working start.cs because its obvious you have no idea how to fix it and like alot of people expect me to do the work for you, i think ive done more than enough by allowing this to be released, if you can follow instructions its not my problem, no amount of complaining will sway me on this matter
also anyone planning on msning me regarding this source, they will be deleted and blocked