安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题




The new API will use ASP.NET SignalR[signalr.net], which will allow us to take advantage of WebSockets and gracefully fall back on AJAX. However, this may be an issue for your particular project because, as far as I can tell, a SignalR client does not exist for Python. That being said, if any third parties are using our current GMR API, we could re-create it in Multiplayer Robot.
As for the turn history, the new API will offer the ability to get the turns for a game or user. However, if you want to use it for estimating turn completion times, the new Multiplayer Robot will actually do that server-side, using some predictive analytics. The new API will be able to give you an estimate in the form of a date range.
We're expecting to roll out the initial alpha test of Multiplayer Robot within a couple months. If you'd be interested in targeting the new API, we could probably get you in on the alpha.
Thanks for the response. Your new API sounds very cool.
It would be great to get early access to the API, thank you. Hopefully someone (ideally not me) will make a Python SignalR client by then.