Hi, when user joins MMORoom i don't set SetUserPositionRequest (for testing purposes).
After time i get this exception in console, is this expected behavior by sfs if limbo position is not set ?
Just feels weird that sfs produces an exception and not well managed error or warning instead (if SetUserPositionRequest is the reason).
In attachment i added screenshot
MMORoom SetUserPositionRequest
- YoungDeveloper
- Posts: 48
- Joined: 02 Mar 2014, 21:38
- Location: Latvia
MMORoom SetUserPositionRequest
- Attachments
-
- 1f750586bb9673c91880751fbb2f6dfa.png
- (24.18 KiB) Not downloaded yet
Re: MMORoom SetUserPositionRequest
YoungDeveloper wrote:Hi, when user joins MMORoom i don't set SetUserPositionRequest (for testing purposes).
After time i get this exception in console, is this expected behavior by sfs if limbo position is not set ?
It is expected that the User is kicked out of the Room.
The state in which a User is joined in an MMORoom but not positioned "anywhere" in the virtual coordinates is called "Limbo". You also have a setting in the MMORoom itself that determines how long a player can remain in "Limbo" before getting kicked out.
The idea being that if one or more clients are in Limbo no one can interact with them and only by setting their position they will appear in other player's AOI.
However the exception in the screenshot is not expected.
What SFS2X version are you using? Can you tell us the steps to reproduce the problem?
Thanks
- YoungDeveloper
- Posts: 48
- Joined: 02 Mar 2014, 21:38
- Location: Latvia
Re: MMORoom SetUserPositionRequest
Hi, it was developers fault, instead of managing users and room via getApi().joinRoom instead it was executed directly - room.addUser.
Sorry for false alarm
Sorry for false alarm
Who is online
Users browsing this forum: Stevenor and 110 guests