Post: #10

Are you sure it wouldn't be a problem with tags not matching?

TAG.Sync.Paperdoll="layer1=NULL, layercor1=NULL, layer2=NULL, layercor2=NULL, layer6=NULL, layercor6=NULL, layer6=5447, layercor6=713, layer1=5184, layercor1=NULL, layer2=7030, layercor2=2057, layer6=NULL, layercor6=NULL, layer6=5138, layercor6=2057, layer1=NULL, layercor1=NULL, layer2=NULL, layercor2=NULL, layer6=NULL, layercor6=NULL, layer6=5447, layercor6=713, layer22=NULL, layercor22=NULL, layer22=9860, layercor22=1940, layer2=5122, layercor2...

LOCAL.SQL=<DB.AEXECUTE SQLAsyncResponse, UPDATE paperdoll SET <TAG.SQLSync.PaperdollItem> WHERE uid='<UID>' LIMIT 1>

Using your code and a simple debug message, it showed me that it was trying to "UPDATE paperdoll SET 0 WHERE uid='...' LIMIT 1"
I did not actually do the AEXECUTE here, I was simply trying to see if the query was properly formed.
Now I'm not an SQL expert here, but I don't think doing SET 0 is proper syntax... and doing so inside an async query is probably not very good... So I'm gonna take a wild guess here and say the issue might be with async database handling not being able to handle USER mistakes properly.

When it comes to Sphere string handling, I think we are ok.
Any strings can hold up to 2147483647 characters (the 4096 Feeh mentioned is only for SCRIPT lines but it's still higher then what you need)