Page 1 of 1

SFS Developer to Troubleshoot

Posted: 19 Oct 2020, 16:07
by mlobel
We are having problems with our SFS implementation and our original developer that set it up is off the project now. Our current developer is more focused on Unity. There are a few issues we are facing and need help ASAP to clear them so we can finalize the project's current phase.

Here are some samples of the issues we are facing:

Scenario 1:
A room with a type sfsroom can be casted to an mmoroom type to create a room and was working previously but something changed and now it can not be casted to an MMOroom anymore.

Scenario 2:
sfs.login that was working suddenly does not return any data from the custom login wherein the custom code on the backend was unchanged for a long time.

Scenario 3:
Some zone settings suddenly got changed without any prior changes to its .xml files. For example is customLogin:true suddenly went to customLogin:false which was used for the game login system.

It's really a mix of issues and there does not seem to be a constant behaviour for the problems.

If you can help, email me directly at: matt@sparrowia.com

Re: SFS Developer to Troubleshoot

Posted: 20 Oct 2020, 07:57
by Lapo
Just a few suggestions ...

Code: Select all

Scenario 1:
A room with a type sfsroom can be casted to an mmoroom type to create a room and was working previously but something changed and now it can not be casted to an MMOroom anymore.

You should take a look at the class hierarchy in the Java docs. It will probably help to clarify how different Room objects can be cast.
http://docs2x.smartfoxserver.com/api-do ... /Room.html

In order to create an MMORoom you're a required to pass a configuration object, you won't be able to simply cast an SFSRoom into an MMORoom.
In other words, from server side you need to call the SFSApi.createRoom(...) method passing a CreateMMORoomSettings object with the config of the MMORoom you want to create.

Scenario 2:
sfs.login that was working suddenly does not return any data from the custom login wherein the custom code on the backend was unchanged for a long time.

You should probably check the server side logs to see if an error occurs during login that prevents the Extension from returning what you expect.

Scenario 3:
Some zone settings suddenly got changed without any prior changes to its .xml files. For example is customLogin:true suddenly went to customLogin:false which was used for the game login system.

Well, xml files don't change themselves ... :D
You may inadvertently changed some settings via the AdminTool and saved them. If you know what was changed just set it back to its original value. Also keep in mind that in the AdminTool you can always make a backup of the previous settings alongside submitting new ones. If you use that feature you can always return to the previous state.

Cheers