Posts: 117
Threads: 52
Joined: Jun 2012
Reputation:
0
Thing is there are bunch of sscanf parameters. Anyway to find it quickly?
Example: I got these
if(sscanf(params, "iI(-1)I(-1)", iVehicle, iColors[0], iColors[1]))
sscanf(szFileStr, "p<|>iis[8]s[24]ffffffiiiiiffd",
BusinessInfo[iIndex][bOwned],
BusinessInfo[iIndex][bLevel],
BusinessInfo[iIndex][bDescription],
BusinessInfo[iIndex][bOwner],
BusinessInfo[iIndex][bExteriorX],
BusinessInfo[iIndex][bExteriorY],
BusinessInfo[iIndex][bExteriorZ],
BusinessInfo[iIndex][bInteriorX],
BusinessInfo[iIndex][bInteriorY],
BusinessInfo[iIndex][bInteriorZ],
BusinessInfo[iIndex][bLock],
BusinessInfo[iIndex][bPrice],
BusinessInfo[iIndex][bPickupID],
BusinessInfo[iIndex][bCustomInterior],
BusinessInfo[iIndex][bCustomExterior],
BusinessInfo[iIndex][bExteriorA],
BusinessInfo[iIndex][bInteriorA],
BusinessInfo[iIndex][bInt]
is that wrong?
Posts: 117
Threads: 52
Joined: Jun 2012
Reputation:
0
What about the error that is shown in the picture? Could not connect to YSI update server thing? And what happens If I run my server like this? with those errors?
Posts: 117
Threads: 52
Joined: Jun 2012
Reputation:
0
Lol thanks, finally, about the parameter warnings, does it effects how my server works or anything?
Posts: 758
Threads: 7
Joined: Mar 2011
Reputation:
0
It might affect the scripts where the problem-causing sscanf is located. Other sscanf-functions will still work fine, but the error-reporting one might not get the information properly saved into the variables. My suggestion is to debug every sscanf with 'print' and/or 'printf' to find the one which is causing these errors.