Have you tested the scenario above with the latest versions of SFS2X and relative API? If not I'd suggest to do so and let us know.
I am not sure why the described use case would not work. RoomVariables do not depend on Room Groups and even less so from the suppressUserList setting.

In particular ...

Hi,
We have seen the official documentation mentioning that turning off Wi-Fi should not be used to test reconnection. However, it is unclear why this method worked correctly in 2.9 but does not work in 2.16.
Most of this depends on "luck", but generally speaking it will not work.
As outlined in ...

I will probably email tomorrow for the pre release patch just to test out if it solves some other problems,

Yes, I think this would be best so if other related issues persist we can fix them out before releasing an update.

Thanks

Hi,
thanks for reporting. We'll add it to the next patch update.
If you need it sooner we can send a pre-release. Send us an email to support@... with a reference to this topic.

I sent an email on 27/01/2025.
That stack trace from 2025 was happening in a different system where i was also calling ...

Hi,
Metaspace is affected when Running lots of Rooms each with its Extension, especially when the Extension is pretty big maybe because of dependencies. Since every Room Extension is by default loaded in a new classloaders you end up with many copies of your Extension class and dependencies, one for ...

I am referring to a warning message in the client side logs.
For example in Java or C# (client) you'll get a "Lag Monitoring requires that you are logged in a Zone" message.

Cheers

If you enable the LagMonitor before having successfully logged in, you will get a warning message in your client side logs.
As regards unexpected disconnections in a local network I agree they should never happen. Not even rarely, unless the there's some weird technical issue in the network or some ...

Check the logs and see if there's a message relative to that User that was kicked for being idle.
If the config was done correctly you should not find it. In which case it means that the client got disconnected due to bad network conditions.

To remedy some of those cases you should turn on the ...

Hi,
yes and no :)
No in the sense that the "max idle time" is the same for everyone in the Zone, but also Yes : you can simply make sure that the client sends a small request every now and then to keep the connection alive and never get disconnected for being idle.

There's two ways to do this:
1 ...

Since 2.20.5 we have added the ability to access custom http headers.
See here for more details:
https://docs2x.smartfoxserver.com/Advan ... tp-headers

Let us know if this helps solving your use case.
Cheers

Hi,
I want to forcibly reclaim all rooms within a certain Zone and refund the balances of all users in those rooms, or implement other functionalities.

The best way to do this is either with a custom admin Extension for your app, or a custom AdminTool module. The latter would allow you to ...

Hello.
Premise: the detection of the original IP works only with Websocket connections, not with the TCP SFS2X protocol.

Client -> CloudFront -> Nginx -> SFS
It depends on what Nginx is sending to SFS. If Nginx is sending the "x-forwarded-for" header correctly, SFS2X will detect the original ...

One more thing. In the mini log dump you posted it is shown a number of Rooms apparently with the same name.
I suspect this is due to the way the provided RoomSettings object is passed to the QuickJoin request. The name of the the new Room that gets created if the match expression returns nothing ...

SFS2x version is 2.19.0
Client api version 1.8.5
The issue is incorrect order of onRoomJoin and onRoomAdded events. This does not happen consistently, in some cases onRoomAdded is received after onRoomJoin.

We've tested with C# API 1.8.5 and both SFS2X 2.19.0 and SFS2X 2.20.5 and haven't found ...

Thanks.
We'll post an update after testing the use case.

Cheers