sscanf "u" and "s[126]" specifier bug
#6

Might be something in one of your filterscripts? Maybe? Im super new to scripting but I had a similar issue with my script yesterday. I would type almost any cmd and it would give me an error message from a different filterscript regardless of if the cmd worked or not.

I disabled the filterscript through the server.cfg and I stopped getting that error message. As for why its not showing your usage cmd I have no idea. But try this maybe?
PHP Code:
if(sscanf(params"us[356]"pnamestring)) return Usage(playerid,"w <matn> - Baray Chat Dargooshi"); 
Reply


Messages In This Thread
sscanf "u" and "s[126]" specifier bug - by xRadical3 - 24.12.2018, 13:46
Re: sscanf "u" and "s[126]" specifier bug - by Calisthenics - 24.12.2018, 15:00
Re: sscanf "u" and "s[126]" specifier bug - by xRadical3 - 24.12.2018, 15:50
Re: sscanf "u" and "s[126]" specifier bug - by SapMan - 24.12.2018, 16:22
Re: sscanf "u" and "s[126]" specifier bug - by xRadical3 - 25.12.2018, 07:56
Re: sscanf "u" and "s[126]" specifier bug - by aKnoxx - 25.12.2018, 09:17
Re: sscanf "u" and "s[126]" specifier bug - by xRadical3 - 25.12.2018, 12:53
Re: sscanf "u" and "s[126]" specifier bug - by aKnoxx - 26.12.2018, 07:39

Forum Jump:


Users browsing this thread: 2 Guest(s)