MySql Skin saving (its been a week)
#1

FIXED!
Reply
#2

cache_get_value_int(0, "Skin", PlayerInfo[playerid][Skin]); - Just an example how it should look...
Reply
#3

Why do you create these absolutely humongous arrays?
  • msg[500] - not even used
  • query[1000] (1) - max length for that query is 78 characters
  • query[1000] (2) - max length for that query is 284 characters
  • playerserial[128] - a gpci string is 41 (40 + null terminator) characters
  • query[2316] - max length for that query is 84 characters
Do you get the "code size" warning on compilation? Because that is a severe red flag. Using more memory than is assigned will eventually lead to memory corruption which in turn will lead to all sorts of glitches.
Reply
#4

@Andrei
Thanks.

@vince
I actually created this script before a year and i m scripting it again so. Have to fix it and no it doesn't show any warning or error. Thanks to you for letting me.

But both of your post really didn't help me.
Reply
#5

Quote:

It doesn't load players skin but it does save player skin into database.

Generally, skins don't set unless the player is spawned, try setting them OnPlayerSpawn.

Also I don't see where you are doing TogglePlayerSpectating(playerid, 1);

pawn Код:
public OnPlayerConnect(playerid)
{
    TogglePlayerSpectating(playerid, 1);
Reply
#6

Quote:
Originally Posted by Dokins
Посмотреть сообщение
Generally, skins don't set unless the player is spawned, try setting them OnPlayerSpawn.

Also I don't see where you are doing TogglePlayerSpectating(playerid, 1);

pawn Код:
public OnPlayerConnect(playerid)
{
    TogglePlayerSpectating(playerid, 1);
I do save player data including skin under PlayerDisconnect. Isn't same thing if i do save player skin after spawned or under PlayerDisconnect? Does it matter?
Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)