The problem is the deployment of the Extension. You should deploy the Tris folder only, not the full path from the example zip file. In other words the Extensions folder on the server side should look like this: > /extensions ---> __lib__ ---> Tris ------> TrisExtension.jar Re-deploy the extension, ...

I would like to add that after the suggested fresh install, you check the AdminTool before moving your files from the old installation.
If the error persist after a fresh install, try clearing the browser cache.

I'm not sure how to help. I guess it's a matter of checking the errors you get and fix them.

If the Room is "owned" by the server (which means it's created on the server side by your Extension), its Room Variables are never destroyed (unless you restart the server, or you implement Room Persistence - check this article we just published). To check the state of Room Variables, afte...

Hello. For the doors state you should use a Room Variable. This can be set using the SetRoomVariablesRequest . You have to give each door an id, and you could use a boolean to indicate if it is opened or closed: void SomeMethod() { sfs.AddEventListener(SFSEvent.ROOM_VARIABLES_UPDATE, OnRoomVarsUpdat...

As the tooltip on the Value field in the Room Variable creation form shows, a JSON block is required. So using [] is correct.

It looks like we made a mistake creating the zip file for the download section of our website. We now fixed it.
Please download the C# API again. Sorry.

We just released v1.7.16 of the SFS2X C# client API for Unity / .Net / Mono / Universal Windows Platform. This new version fixes a crash which could occur in Unity's Android build with il2cpp, due to a Console.WriteLine instruction in the API internal logger. You can download the API at this url: ht...

We just published a new version of the C# API containing the fix. Now under Unity that Console.WriteLine is substituted by a Debug.Log.
Again, thank you for reporting the issue.

Thank you for reporting. We will fix this in the next API release.

Are you sure the API JavaScript file is not corrupted? Because the loading approach you use is the same we use in our examples, and they work as expected. Also, the error you reported doesn't show up in our examples.

SmartFoxServer 2X 2.17.3 is available as a patch for existing SFS2X 2.17 installations. Download SFS2X 2.17.3 patch from here. ______________ RELEASE NOTES Server Side [FIX] issue with the Flood Filter triggering too quickly in respect to the configured message rate, resulting in requests being deni...

Hello, I have a very important question that is a key for our team and will help the decision for future adaptation of smartfix in our upcoming projects :- Is it possible to reduce the size of "sfs2x-api-xxx.js" ? Using custom build/bundle ? We don't want to utilize the full functionality...

It looks like there's an error in the parameters passed to the LoginRequest constructor.
I guess the problem is the params object, which is supposed to be a SFSObject instance.

Thank you, I have another question: can I use older JS-client version(before release v1.7.0) with new server 2.17(with disable binary protocol). I'm not clearly with you doc(http://docs2x.smartfoxserver.com/GettingStarted/migration-213) No sorry. That page refers to the old SFS v2.13. Non-binary pr...