I know they are all connected to the same tables on the embed database, but I think it would be nice to create a better approach in the code towards "blockBuddy" and "addBuddy". Reason for that: It doesn't make much sense to add the player to your buddy list before adding it to y...

Just confirming here how the bug happens and how off I was. how to replicate it: Variables set as string length 0 are being read incorrectly by __sfscore__ storage database. The variable names printed in the field goes as a string incomparable with its values (5 variables, 4 values since the last is...

There we go! Ok first of all, I would like to apologize for my behavior on this matter. I went COMPLETELY over my head when I thought I had it figured out and blamed on SFS team regardless of what was actually going on. So to patch things up, I've managed to find apparently, the real trigger to forc...

Watch it for data tamper buddy. I've been a victim of these people not long enough for using external ASP pages as a connection bridge to my SFS. The best way to protect yourself is definally using SFS Database functionalities. This way is highly unlikely anyone can tamper your database connections

Ooooh there we go :) Yea jix did not see that as well lol. Also didn't know the relation between the Embedded database engine docs and the advanced buddy list (althou it is clearly expressed there and I was too dumb to put it together). Yea about the bug, it does have some relation afterwards. They ...

Thanks lapo and sorry for the frustration. You know just as any of us how frustrated and out of control a person can get after spending 2 months (since my last post about this problem) trying figuring out a bug out of trials and errors without much instructions then "Reason: 4". I apologiz...

YES! FOUND THE BUG! As simple as it is, YES it is a SmartFoxServer bug , and you will all laugh on how to replicate: You all know that 2 equal usernames can be logged at the same time in 2 different zones right? well yea, obviously it was made to work this way. But I think what you didn't know is th...

If this is of any help:
smartfox.loadBuddyList() is being loaded in response of the user joining the lobby, and right after a request for joining the trade room (multiple room feature being used here).

This might also be of some help. This is the output retrieved from the wrapper the moment the warning occurs. I've retrieve it from the moment the error occurs until the offline buddy variables is setup. Notice that the buddy variable $clan is blank. Don't know if that could be a problem yet, but I'...

2008/04/08 21:38:59.779 - [ WARNING ] [id: 29] (AdvancedBuddyListPersister.loadList): Error loading buddy list for user: Lizzy. Reason: 4 2008/04/08 21:39:11.889 - [ WARNING ] [id: 29] (AdvancedBuddyListPersister.loadList): Error loading buddy list for user: The Unspeakable. Reason:...

I'll try being as straight forward as possible :) How does it happen: Login, add a player to the list. Close the engine, re-open it and this "warning" (that should be "severe") will pop in the logs. The buddy list "vanish" and If you try to add that player again, "...

I see. UserVariables are attached to the user so if he's in multiple rooms it's necessary to update all the people in those rooms. Maybe we could add an extra parameter to the setUserVariables that forces the update only in the specified room . Would this help? O yes yes that would help quite a lot...

martinselva : one simple workaround is to catch the login error on the client side and call a PHP/ASP page on your server that sends you a notification. You could also store the timestamp of the last time in which the event occurred so that you don't send too many emails at once. Lol why didn't I t...

Nice question and nice explanation Lapo :D I'll be posting very soon a great example of joining multiple rooms using SFS Pro. Exactly like Lapo explained, a user that joins a lobby while also joins a game room. In my case I made it in a very interesting way: The user joins what I called "the ma...

sfs.login(zone, myName, myPass, true); variable usage: true to kick any one logged with that username. Reason: Even with custom login and a nice implementation of ghost-killers, we still eventually end up with ghost connections due to client's errors. A lot of games and messengers out there have th...