does anyone know this error on my char_map

[joven15]

Im using 2014-04-16aRagexe client. and i also using a udpate emulator from rathena github.

any idea how to fix this ? 

Edited November 3, 2020 by joven15

[Thanna20]

27 minutes ago, joven15 said:

Im using 2014-04-16aRagexe client. and i also using a udpate emulator from rathena github.

any idea how to fix this ? 

you have to import the sql upgrades from the folder sql-files->upgrades

[joven15]

1 hour ago, Thanna20 said:

you have to import the sql upgrades from the folder sql-files->upgrades

what kind of upgrade im using a latest rathena emulator from github then, i use an old ragexe client.

 

Edited November 3, 2020 by joven15

[Thanna20]

11 minutes ago, joven15 said:

what kind of upgrade im using a latest rathena emulator from github then, i use an old ragexe client.

 

import those sql upgrades to your database.

[joven15]

15 minutes ago, Thanna20 said:

import those sql upgrades to your database.

all of them ?

[Thanna20]

5 minutes ago, joven15 said:

all of them ?

yes, since those are essential on the latest rathena.

[joven15]

7 minutes ago, Thanna20 said:

yes, since those are essential on the latest rathena.

Still got the error. anyone know how to fix this ? so annoying i use clean rathena on github it supposed to be no error since its clean emulator.

Edited November 3, 2020 by joven15

[Thanna20]

Just now, joven15 said:

Still got the error. anyone know how to fix this ? so annoying i use clean rathena on github it supposed to be no error since its clean emulator.

have you set your packet date to the client date that you are using? for 2015 and above the gender is per character not pet account anymore.

[joven15]

Just now, Thanna20 said:

have you set your packet date to the client date that you are using? for 2015 and above the gender is per character not pet account anymore.

are you talking about the packet from src ?

 

 

[Thanna20]

did you use the main.sql that comes with the latest rathena or is that an old database? because on the latest database there is no gender anymore on the character table.

[joven15]

3 minutes ago, Thanna20 said:

did you use the main.sql that comes with the latest rathena or is that an old database? because on the latest database there is no gender anymore on the character table.

all latest from latest rathena i used main.sql also with the log. but i having this kind of error.

[Thanna20]

3 minutes ago, joven15 said:

all latest from latest rathena i used main.sql also with the log. but i having this kind of error.

check this link out.

 

https://github.com/rathena/rathena/pull/5006/files

[joven15]

Just now, Thanna20 said:

check this link out.

 

https://github.com/rathena/rathena/pull/5006/files

still has a gender on the character. as i can see the script but it modify the src. as you u can see it pull up on july 4, i just downloaded the rathena from github a week a go so im sure i using a latest. rathena emulator with the latest main.sql on it also with the log. its just the i using a old client. but i dont think thats  the reason.

[Thanna20]

1 minute ago, joven15 said:

still has a gender on the character. as i can see the script but it modify the src. as you u can see it pull up on july 4, i just downloaded the rathena from github a week a go so im sure i using a latest. rathena emulator with the latest main.sql on it also with the log. its just the i using a old client. but i dont think thats  the reason.

If you can try something from 2015 client maybe it would work as 2014 is quite old and I think its not supported anymore.

[joven15]

Just now, Thanna20 said:

If you can try something from 2015 client maybe it would work as 2014 is quite old and I think its not supported anymore.

ok i will try now. 2015 client.

[joven15]

9 minutes ago, Thanna20 said:

If you can try something from 2015 client maybe it would work as 2014 is quite old and I think its not supported anymore.

i really have to use 2014 since ill make a classic server. 99/50 if i will use the latest theres a lot difference.

[Thanna20]

16 minutes ago, joven15 said:

i really have to use 2014 since ill make a classic server. 99/50 if i will use the latest theres a lot difference.

did you recompile your server when you added your packet date?

[joven15]

29 minutes ago, Thanna20 said:

did you recompile your server when you added your packet date?

yes i already i always compile.

[Thanna20]

3 minutes ago, joven15 said:

yes i already i always compile.

You can report it on the git hub of rathena. https://github.com/rathena/rathena/issues

[Patotron]

In src/char/char.cpp, function char_mmo_gender.

 

int char_mmo_gender( const struct char_session_data *sd, const struct mmo_charstatus *p, char sex ){
	switch( sex ){
#if PACKETVER >= 20141016
		case 'M':
			return SEX_MALE;
		case 'F':
			return SEX_FEMALE;
#else
		// No matter what the database says, always return the account gender
		// Per character gender is not supported before 2014-10-16
#endif
		default:
			// There are calls to this function that do not contain the session
			if( sd == nullptr ){
				int i;

				// Find player session
				ARR_FIND( 0, fd_max, i, session[i] && ( sd = (struct char_session_data*)session[i]->session_data ) && sd->account_id == p->account_id );

				if( i >= fd_max ){
					ShowWarning( "Session was not found for character '%s' (CID: %d, AID: %d), defaulting gender to male...\n", p->name, p->char_id, p->account_id );
					return SEX_MALE;
				}
			}

			ShowWarning( "Found unknown gender '%c' for character '%s' (CID: %d, AID: %d), returning account gender...\n", sex, p->name, p->char_id, p->account_id );
			return sd->sex;
	}
}

As we can see here if PACKETVER is less than 20141016 always execute the default case.

The message "Found unknown gender 'M' for character 'Joven15'" is the correct behaviour.

In your use case is safe to just comment this line (886 in the in the mentioned file), since the only thing it's telling you is that since you use a lower version than the 20141016 it doesn't support sex by character.

Just keep in mind is a warning, not an error.

 

EDIT: However, this error will be corrected when the PR is accepted

Edited November 3, 2020 by Patotron