Talk:Realms API - Revision history

imported>NathaanTFM: /* New paths */ new section

2018-07-27T15:55:48Z

New paths: new section

← Older revision		Revision as of 15:55, 27 July 2018
Line 49:		Line 49:

	(Tested with realms 1.13.3)		(Tested with realms 1.13.3)

			== New paths ==

			This should contains every paths which are present in realms-1.13.3.jar realms client : https://pastebin.com/R0Br85aE

2018-07-27T15:17:15Z

← Older revision		Revision as of 15:17, 27 July 2018
Line 42:		Line 42:
	== Connect to local ==		== Connect to local ==

	You could technically connect Realms to a local server. You just have to set the "~~reams~~.environment" java property / environment variable to either "LOCAL" or "STAGE"		You could technically connect Realms to a local server. You just have to set the "realms.environment" java property / environment variable to either "LOCAL" or "STAGE"

	LOCAL connects the Realms Client to http://localhost:8080		LOCAL connects the Realms Client to http://localhost:8080

2018-07-27T15:13:41Z

Connect to local

← Older revision		Revision as of 15:13, 27 July 2018
Line 45:		Line 45:

	LOCAL connects the Realms Client to http://localhost:8080		LOCAL connects the Realms Client to http://localhost:8080

	STAGE connects the Realms Client to https://pc-stage.realms.minecraft.net		STAGE connects the Realms Client to https://pc-stage.realms.minecraft.net

	(Tested with realms 1.13.3)		(Tested with realms 1.13.3)

2018-07-27T15:13:23Z

Connect to local: new section

← Older revision		Revision as of 15:13, 27 July 2018
Line 39:		Line 39:
	Has anyone actually decompiled the current (1.12.2) Realms Api? I'm using IntelliJ Idea to make a Forge mod,		Has anyone actually decompiled the current (1.12.2) Realms Api? I'm using IntelliJ Idea to make a Forge mod,
	and was able to check the client jar, so I may update the documentation myself. (Even though anyone really could if they tried)		and was able to check the client jar, so I may update the documentation myself. (Even though anyone really could if they tried)

			== Connect to local ==

			You could technically connect Realms to a local server. You just have to set the "reams.environment" java property / environment variable to either "LOCAL" or "STAGE"

			LOCAL connects the Realms Client to http://localhost:8080
			STAGE connects the Realms Client to https://pc-stage.realms.minecraft.net

			(Tested with realms 1.13.3)

2018-04-28T18:56:45Z

← Older revision		Revision as of 18:56, 28 April 2018
Line 38:		Line 38:

	Has anyone actually decompiled the current (1.12.2) Realms Api? I'm using IntelliJ Idea to make a Forge mod,		Has anyone actually decompiled the current (1.12.2) Realms Api? I'm using IntelliJ Idea to make a Forge mod,
	and was able to check the client jar, so I may update the documentation myself.		and was able to check the client jar, so I may update the documentation myself. (Even though anyone really could if they tried)

2018-04-25T22:59:53Z

Decompiling - Outdated Api: new section

← Older revision		Revision as of 22:59, 25 April 2018
Line 34:		Line 34:

	--[[User:Mitchfizz05\|Mitchfizz05]] ([[User talk:Mitchfizz05\|talk]]) 07:03, 15 April 2015 (UTC)		--[[User:Mitchfizz05\|Mitchfizz05]] ([[User talk:Mitchfizz05\|talk]]) 07:03, 15 April 2015 (UTC)

			== Decompiling - Outdated Api ==

			Has anyone actually decompiled the current (1.12.2) Realms Api? I'm using IntelliJ Idea to make a Forge mod,
			and was able to check the client jar, so I may update the documentation myself.

2017-02-06T21:40:33Z

← Older revision		Revision as of 21:40, 6 February 2017
Line 1:		Line 1:
	== ~~Session ID format no longer accepted?~~ ==		== Tools that works with the Realms API ==
	~~I can't get the server to accept a Session ID formatted as per the article. I always receive a <code>401 Invalid session id</code>. I'm using~~

	~~<code>http --verbose GET ${realms_server}~~/~~mco~~/~~available "Cookie:sid=token:${access_token}:${uuid};user=${user_id};version=${version}<~~/~~code>~~		I wrote some simple scripts that work: https://github.com/air/minecraft-tools

	~~My <code>access_token<~~/~~code> is freshly validated by the authserver, and my <code>uuid<~~/~~code> is trimmed~~.		There are amazing nodejs tools at https://github.com/zekesonxx/node-yggdrasil

	--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, ~~7 January~~ 2017 (UTC)		--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 21:40, 6 February 2017 (UTC)

	== pc.realms.minecraft.net? ==		== pc.realms.minecraft.net? ==

2017-01-07T01:12:18Z

pc.realms.minecraft.net?

← Older revision		Revision as of 01:12, 7 January 2017
Line 10:		Line 10:
	== pc.realms.minecraft.net? ==		== pc.realms.minecraft.net? ==
	I snooped my Minecraft process and observed it connects to <code>pc.realms.minecraft.net</code>, not <code>mcoapi.minecraft.net</code>. This also responds to Realms API requests. It resolves to a different IP. Anyone know if this is used by clients instead of <code>mcoapi</code>?		I snooped my Minecraft process and observed it connects to <code>pc.realms.minecraft.net</code>, not <code>mcoapi.minecraft.net</code>. This also responds to Realms API requests. It resolves to a different IP. Anyone know if this is used by clients instead of <code>mcoapi</code>?

	--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, 7 January 2017 (UTC)		--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, 7 January 2017 (UTC)

2017-01-07T01:12:09Z

Session ID format no longer accepted?

← Older revision		Revision as of 01:12, 7 January 2017
Line 5:		Line 5:

	My <code>access_token</code> is freshly validated by the authserver, and my <code>uuid</code> is trimmed.		My <code>access_token</code> is freshly validated by the authserver, and my <code>uuid</code> is trimmed.

	--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, 7 January 2017 (UTC)		--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, 7 January 2017 (UTC)

2017-01-07T01:11:52Z

info and questions

← Older revision		Revision as of 01:11, 7 January 2017
Line 1:		Line 1:
			== Session ID format no longer accepted? ==
			I can't get the server to accept a Session ID formatted as per the article. I always receive a <code>401 Invalid session id</code>. I'm using

			<code>http --verbose GET ${realms_server}/mco/available "Cookie:sid=token:${access_token}:${uuid};user=${user_id};version=${version}</code>

			My <code>access_token</code> is freshly validated by the authserver, and my <code>uuid</code> is trimmed.
			--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, 7 January 2017 (UTC)

			== pc.realms.minecraft.net? ==
			I snooped my Minecraft process and observed it connects to <code>pc.realms.minecraft.net</code>, not <code>mcoapi.minecraft.net</code>. This also responds to Realms API requests. It resolves to a different IP. Anyone know if this is used by clients instead of <code>mcoapi</code>?
			--[[User:Air\|Air]] ([[User talk:Air\|talk]]) 01:11, 7 January 2017 (UTC)

			== Unknown edit ==
	When call API /worlds the "players" property is always empty		When call API /worlds the "players" property is always empty