[FinStar]

Guys do not know where the problem may be? I can not figure out :/

Код HTML:

[19:47:44] [debug] Server crashed while executing Roleplay.amx
[19:47:44] [debug] AMX backtrace:
[19:47:44] [debug] #0 00000034 in INI_AddToBuffer (INI:file=57, name[]=@00000000 "", data[]=@01ed410c "0000001484523489") at <unknown file>:0
[19:47:44] [debug] #1 000115f0 in ?? (str[]=@00000039 !"=", ... <13 arguments>) at D:\Dropbox\SA-MP\Los Angeles Roleplay\pawno\include\YSI\y_ini.inc:1076
[19:47:44] [debug] #2 00000034 in public OnPlayerDisconnect () at <unknown file>:0

[Konstantinos]

Update to YSI 4: http://forum.sa-mp.com/showpost.php?...99&postcount=2

Looking at the logs though the 2nd parameter is empty. Like the "entry" you specified in a function such as INI_WriteInt is "". Do you by any chance try to format an entry name but something went wrong (passing a wrong string which is empty instead of the one formatted for example)?

[FinStar]

I think that's a mistake, I looked after the forum on other issues like this


Look this..

http://forum.sa-mp.com/showthread.ph...NI_AddToBuffer

https://sampwiki.blast.hk/wiki/Valstr

https://sampforum.blast.hk/showthread.php?tid=570922

https://github.com/ziggi/sa-mp-fixes


EDIT:

This problem occurred when running the server, I think that the problem will be writing files, yesterday, the first time it happened, when a player joins "exceptionally" as server crashes, the log displays this error..

Код HTML:

[19:47:44] [debug] Server crashed while executing Roleplay.amx
[19:47:44] [debug] AMX backtrace:
[19:47:44] [debug] #0 00000034 in INI_AddToBuffer (INI:file=57, name[]=@00000000 "", data[]=@01ed410c "0000001484523489") at <unknown file>:0
[19:47:44] [debug] #1 000115f0 in ?? (str[]=@00000039 !"=", ... <13 arguments>) at D:\Dropbox\SA-MP\Los Angeles Roleplay\pawno\include\YSI\y_ini.inc:1076
[19:47:44] [debug] #2 00000034 in public OnPlayerDisconnect () at <unknown file>:0

[Konstantinos]

INI_AddToBuffer function does not use any valstr but writing functions do. Still, the best option for you is to update to YSI 4 which fixes both valstr and checks if "key" (called "name" in YSI 3.1) is not empty before continuing.