Help request: "invalid idx 0" after adding Sash system by Lennt

[im4x8061 1]

Hey together,

after adding the Shoulder Sash System with Scale by Lennt in version 0.3, there is the syserr on client side simply stating "invalid idx 0". Server, db, dump_proto and client compile just fine. The error occurs in the transition from login screen to character select. When then selecting a character, one gets thrown back to the login screen instead of entering the loading screen. Here are the logs/errors:

- client/syserr.txt

Spoiler

invalid idx 0

- auth/syserr : no error here

- auth/syslog

Spoiler

Jan  7 00:44:14 :: SYSTEM: new connection from [XXX.XXX.XXX.XXX] fd: 16 handshake 4137518451 output input_len 0, ptr 0x210d7700
Jan  7 00:44:14 :: Handshake: client_time 0 server_time 676530
Jan  7 00:44:14 :: AUTH_PHASE 0x210d7700
Jan  7 00:44:14 :: InputAuth::Login : admin(5) desc 0x210d7700
Jan  7 00:44:14 :: SetLoginKey 141872404
Jan  7 00:44:14 :: InputAuth::Login : key 141872404:0x1d978829 login admin
Jan  7 00:44:14 :: QID_AUTH_LOGIN: START 141872404 0x210d7700
Jan  7 00:44:14 :: Create_Time 0 19700101
Jan  7 00:44:14 :: Block Time -2
Jan  7 00:44:14 :: SetRemainSecs admin 0 type 2
Jan  7 00:44:14 :: SendAuthLogin admin key 1
Jan  7 00:44:14 :: AuthLogin result 1 key 141872404
Jan  7 00:44:15 :: SYSTEM: closing socket. DESC #16

- db/syserr : no error here

- db/syslog

Spoiler

Jan  7 00:45:56 :: [     7800] return 0/0/0 async 0/0/0
Jan  7 00:46:01 :: [     7850] return 0/0/0 async 0/0/0
Jan  7 00:46:05 :: AUTH_LOGIN id(1) login(admin) social_id(1234567) login_key(1336545545), client_key(67046166 1563480934 814153046 1851929085)
Jan  7 00:46:06 :: LOGIN_BY_KEY success admin 1336545545 XXX.XXX.XXX.XXX
Jan  7 00:46:06 :: RESULT_LOGIN: login success admin rows: 1
Jan  7 00:46:06 :: test 51894 166465 hair 0
Jan  7 00:46:06 :: [     7900] return 0/0/2 async 0/0/0
Jan  7 00:46:11 :: [     7950] return 0/0/0 async 0/0/0
Jan  7 00:46:16 :: [     8000] return 0/0/0 async 0/0/0
Jan  7 00:46:21 :: [     8050] return 0/0/0 async 0/0/0
Jan  7 00:46:26 :: [     8100] return 0/0/0 async 0/0/0
Jan  7 00:46:31 :: [     8150] return 0/0/0 async 0/0/0
Jan  7 00:46:36 :: [     8200] return 0/0/0 async 0/0/0
Jan  7 00:46:41 :: [     8250] return 0/0/0 async 0/0/0
Jan  7 00:46:46 :: [     8300] return 0/0/0 async 0/0/0
Jan  7 00:46:51 :: [     8350] return 0/0/0 async 0/0/0

game99/syserr: no error

game99/syslog: no log

 

The serverfiles and client are TMP4 source. The implementation was compared with ULTHAR V2 source. The names were changed from "acce" to "sash", but the paths were kept the same as in TMP4 original client. The paths were updated in locale/xxx/item_list.txt to match "sash" theme.

The error must be inside the Svn/Client, right? Only alternative is db, but as the char loads correctly, this is also unlikely?

Any hint is appreciated.

Thanks in advance!

[im4x8061 1]

The error was a mistake in item_proto.txt: The item type "COSTUME_SASH" did not exist. -> Change to "COSTUME_ACCE" did the trick

As the system was applied to TMP4 reference client, Here are some more bug fixes:

- Missing GUI slots for sash and moun: 

- Questfiles call a function pc.open_sash, which should be pc.open_acce

- There is a "WOLFMAN" flags in uitooltip

And a few more things, like wrong function names. Quite a bit to debug.