PARSING ERROR - Unknown Arguments

[Poeta 5]

Version of Files : XXX

Hello everyone im having this error and when i log on my P Server and i teleport my client crash and close instantly  

Im kind of new on the area but after a few changes.. i tried to use old backups from 5days and even 1 week ago but i always get the same error.. After teleport to any map my client just close and i get this message on sysser:

 

0704 13:39:25410 :: no argument name
0704 13:39:25410 ::  !! PARSING ERROR - Unknown Arguments : 9, |6;Cancel

0704 13:40:01438 :: no argument name
0704 13:40:01438 ::  !! PARSING ERROR - Unknown Arguments : 9, |6;Cancel

 

Can someone help me with that problem? 

 

 

Thanks, Sincerly,
Poeta

 

[WeedHex 636]

It seems related to new system you installed.

Find the syserr string and show us the function.

[Poeta 5]

@WeedHex Thats everything i have on my syserr:

 

Jul  4 17:16:11 :: LOG: INSERT DELAYED INTO log (type, time, who, x, y, what, how, hint, ip) VALUES('CHARACTER', NOW(), 1, 964686, 274135, 0, 'WARP', '123123 MapIdx 41 DestMapIdx0 DestX344000 DestY502500 1', '77.54.109.92')
Jul  4 17:16:11 :: LOG: INSERT DELAYED INTO command_log (userid, server, ip, port, username, command, date ) VALUES(1, 999, '77.54.109.92', 1, '123123', 'go d', NOW()) 
Jul  4 17:16:11 :: GLOBAL_TIME: Jul  4 17:16:11 time_gap 0
Jul  4 17:16:11 :: SAVE: 123123 344000x502500
Jul  4 17:16:12 :: DISCONNECT: 123123 (DESC::~DESC)
Jul  4 17:16:12 :: LOG: INSERT DELAYED INTO log (type, time, who, x, y, what, how, hint, ip) VALUES('CHARACTER', NOW(), 1, 964686, 274135, 0, 'LOGOUT', '77.54.109.92 1999978999 0 0 1 41 10', '77.54.109.92')
Jul  4 17:16:12 :: Click Quest : MatchingQuest
Jul  4 17:16:12 :: SAVE: 123123 344000x502500
Jul  4 17:16:12 :: QUEST clear timer 0
Jul  4 17:16:12 :: LOG: INSERT DELAYED INTO log (type, time, who, x, y, what, how, hint, ip, vnum) VALUES('ITEM', NOW(), 3, 31, 0, 10000009, 'SET_SOCKET', '', '', 71224)

 

Sorry about this questions..  and thanks everyone whos trying  to help..

Edited July 4, 2020 by Poeta

[TMP4 11070]

He meant to open all of your files and search for this: 9, |6;Cancel

If you don't know what is the system where it came from search every .py .cpp .quest files.

You can use notepad++ search in all document function so it's gonna be 1 click to search.

[Poeta 5]

@TMP4 Thank you m8.. will try to find that file 

[arves100 1549]

On 7/4/2020 at 2:56 PM, Poeta said:

Version of Files : XXX

Hello everyone im having this error and when i log on my P Server and i teleport my client crash and close instantly  

Im kind of new on the area but after a few changes.. i tried to use old backups from 5days and even 1 week ago but i always get the same error.. After teleport to any map my client just close and i get this message on sysser:

 

0704 13:39:25410 :: no argument name
0704 13:39:25410 ::  !! PARSING ERROR - Unknown Arguments : 9, |6;Cancel

0704 13:40:01438 :: no argument name
0704 13:40:01438 ::  !! PARSING ERROR - Unknown Arguments : 9, |6;Cancel

 

Can someone help me with that problem? 

 

 

Thanks, Sincerly,
Poeta

 

I have to admit, I never encountred this error,

this good guy comes from EterLib\parser, this a TXT parser for events that can happen in the Metin2 Client.

An example of such event can be the empire description, where there was actually a command to wait a couple of sec untill continuing the text rendering.

Under normal sources (no additional system or anything else), this error is only related to TXT parsed by your locale, either "RegisterEventSet" or "RegisterEventSetFromString" (as far as I was able to quickly read).

The ones that gets registred are Empiredesc and Jobdesc, so I am pretty sure you have those files wrong. (Keep in mind that bad codepage can also cause an issue in parsing special character) or you are using an unknown command not handled by the parser.

 

Edited July 9, 2020 by arves100

[Poeta 5]

@arves100 Sorry i forgot to mention that me and my friend who are working on that we found a solution. Im still waiting for his answer about where he changed or did to paste here for those who may have the same problem in the future! But yes you right was on those files.

Thank you everyone who tried to help. I will keep posting stupid questions like that to see if i learn more about it. Tbh this forum is friendly as fuck so i hope you all understand

[xP3NG3Rx 19745]

Can we see the quest-file which cause the problem?