User Settings

To change your password, enter your username/email, current password and new password.

Change Password

API Token - you need an API token in order for your clients to connect to the Metajestic Multiplayer Engine:

Note: if you generate a new key, all previous keys will be invalid and will no longer allow access to the 
Metajestic Multiplayer Engine.

Current API Key:

Expiry

Expires:

Generate new API Key:

Authentication Settings

If you require your end users to authenticate prior to being granted access to the Metajestic Multiplayer Engine, enter below:
URL: the url that you host that will be called by Metajestic, passing along the user supplied jwt token as a header (Bearer token)
ResponseElement: the name of the json element that will be in the response from the above url call, as set to either true or false (boolean) .

For example, if your url for authenticating your JWT is at: https://mysite.com/auth, and it expects a valid JWT token to be passed to the end point as a header Bearer token, and if the passed JWT is valid, it responds with: { "responseMessage":"Valid JWT", "responseStatus": true}

Enter above:
Authentication URL: https://mysite.com/auth
Authentication response element: responseStatus

Default Limit Settings

Here you can set the default limit settings for things like the number of users to return in the closest users calls, the get users by distance calls, etc..

For example, if you set the max users to return in the closest users call to 75, then when the client sends a request to get the closest users, it will return the 75 users that are closest to that user. Similarly, if you set the max distance in the get users by distance to 100, then when the client sends a request to get users by distance it will use this default value and return the users within 100 units (x,y,z) from the user who made the request. 

Note these are only the defaults if no value is sent with the respective requests - you can override this value in a specific request.

Allow users to create rooms    not allowed
By setting this ON, when a user connects with a room-zone that does NOT exist, it will create that room. By setting this OFF, users are only allowed to connect to the predefined rooms-zones you have created.