character slot 1/0 2013 on client and newest trunk

[joelolopez]

i have a latest trunk and a 2013 client im not having errors with luas and lub the problem here is the character available slot displays 1/0 and "not available" how can i make this work???

 

 

like

 

1/9 character slots help guys

Edited August 1, 2013 by joelolopez

[AngelRO]

Check:

 

src\common\mmo.h:

 

#define MAX_CHARS 9

 

char_athena.conf:

 

// How many Characters are allowed per Account ? (0 = disabled)
// You can not exceed the limit of MAX_CHARS slots, defined in mmo.h
// Doing that, chars_per_account will be default to MAX_CHARS.
chars_per_account: 0
 

Mine is set to 0 and all the slots are shown, try changing it to 9.

Edited August 1, 2013 by AngelRO

[joelolopez]

nope it didnt work help anyone

Edited August 1, 2013 by joelolopez

[Kyle873]

Having the exact same issue.

[Kyle873]

Still nothing on this? Even after 100+ revisions the issue is still there.

[Skotlex]

Hmm.... I had this bug just now, and it turns out (in my case) that the problem was some outdated code. rAthena trunk should work correctly, so perhaps this is caused by some custom code bug.

 

The specific issue was that I was using an older char-server codebase, and my char-server was sending back after authentication (0x2727 in parse_fromlogin) mmo_char_send006b() instead of mmo_char_send(). What this means is, if you just send 006b, you are only sending packet 0x6b (character list), whereas the server should send (for 2013 clients) packets 0x82d, 0x9a0, and 0x20d. In particular, I think the problem lies in packet 0x82d, because this is the one that sends in how many characters you are allowed to have (sd->char_slot, which defaults to MAX_CHARS if character_slots is zero in the account database).

 

In any case, rA-trunk should be correct, so I suggest you look closer at what packets are being sent/received so you can figure out where the actual bug is.