Difference between revisions of "Talk:Realms API"
| Line 3: | Line 3: | ||
== Up to date IP == | == Up to date IP == | ||
| − | In order to get a world IP without calling the join endpoint, requests to worlds/{id} appear to have the current IP available instantly, whereas worlds/ alone does not. | + | In order to get a world IP without calling the join endpoint, requests to worlds/{id} appear to have the current IP available instantly, whereas worlds/ alone does not. (Only the owner (or possibly an op?) can call worlds/{id}, however.) |
--[[User:Ispillmydrink|Ispillmydrink]] ([[User talk:Ispillmydrink|talk]]) 21:39, 2 May 2015 (UTC) | --[[User:Ispillmydrink|Ispillmydrink]] ([[User talk:Ispillmydrink|talk]]) 21:39, 2 May 2015 (UTC) | ||
Revision as of 22:00, 3 May 2015
When call API /worlds the "players" property is always empty
Up to date IP
In order to get a world IP without calling the join endpoint, requests to worlds/{id} appear to have the current IP available instantly, whereas worlds/ alone does not. (Only the owner (or possibly an op?) can call worlds/{id}, however.)
--Ispillmydrink (talk) 21:39, 2 May 2015 (UTC)
Join behavior
It appears that /worlds/$id/join calls actually prompt the service to start an instance of the server if it is not already running. This is why the first few calls to the join endpoint will return a 503 while the server is still starting. If no player actually signs on, the created server instance only stays alive for approx 10 minutes until it shuts back down.
--Ispillmydrink (talk) 17:41, 29 April 2015 (UTC)
Some documentation here is out of date.
Some of the Realms protocol has changed as of 1.8.
The "handshake" process documented here no longer works, as well as various other things. I'm not exactly sure what is broken and what isn't, that'll require a bit more investigation than what I've done.
--Mitchfizz05 (talk) 07:03, 15 April 2015 (UTC)
