{"action":"created","issue":{"url":"https://api.github.com/repos/OpenRA/OpenRA/issues/15300","repository_url":"https://api.github.com/repos/OpenRA/OpenRA","labels_url":"https://api.github.com/repos/OpenRA/OpenRA/issues/15300/labels{/name}","comments_url":"https://api.github.com/repos/OpenRA/OpenRA/issues/15300/comments","events_url":"https://api.github.com/repos/OpenRA/OpenRA/issues/15300/events","html_url":"https://github.com/OpenRA/OpenRA/pull/15300","id":336334001,"node_id":"MDExOlB1bGxSZXF1ZXN0MTk3ODExNjMz","number":15300,"title":"Fix Chronoshift-return and Iron Curtain being lost when a RA MCV (un)deploys.","user":{"login":"pchote","id":167819,"node_id":"MDQ6VXNlcjE2NzgxOQ==","avatar_url":"https://avatars1.githubusercontent.com/u/167819?v=4","gravatar_id":"","url":"https://api.github.com/users/pchote","html_url":"https://github.com/pchote","followers_url":"https://api.github.com/users/pchote/followers","following_url":"https://api.github.com/users/pchote/following{/other_user}","gists_url":"https://api.github.com/users/pchote/gists{/gist_id}","starred_url":"https://api.github.com/users/pchote/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pchote/subscriptions","organizations_url":"https://api.github.com/users/pchote/orgs","repos_url":"https://api.github.com/users/pchote/repos","events_url":"https://api.github.com/users/pchote/events{/privacy}","received_events_url":"https://api.github.com/users/pchote/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":{"url":"https://api.github.com/repos/OpenRA/OpenRA/milestones/20","html_url":"https://github.com/OpenRA/OpenRA/milestone/20","labels_url":"https://api.github.com/repos/OpenRA/OpenRA/milestones/20/labels","id":2202516,"node_id":"MDk6TWlsZXN0b25lMjIwMjUxNg==","number":20,"title":"Next release","description":"","creator":{"login":"pchote","id":167819,"node_id":"MDQ6VXNlcjE2NzgxOQ==","avatar_url":"https://avatars1.githubusercontent.com/u/167819?v=4","gravatar_id":"","url":"https://api.github.com/users/pchote","html_url":"https://github.com/pchote","followers_url":"https://api.github.com/users/pchote/followers","following_url":"https://api.github.com/users/pchote/following{/other_user}","gists_url":"https://api.github.com/users/pchote/gists{/gist_id}","starred_url":"https://api.github.com/users/pchote/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pchote/subscriptions","organizations_url":"https://api.github.com/users/pchote/orgs","repos_url":"https://api.github.com/users/pchote/repos","events_url":"https://api.github.com/users/pchote/events{/privacy}","received_events_url":"https://api.github.com/users/pchote/received_events","type":"User","site_admin":false},"open_issues":12,"closed_issues":84,"state":"open","created_at":"2016-12-17T20:43:34Z","updated_at":"2018-07-01T10:32:32Z","due_on":null,"closed_at":null},"comments":5,"created_at":"2018-06-27T18:09:52Z","updated_at":"2018-07-01T11:19:32Z","closed_at":null,"author_association":"MEMBER","pull_request":{"url":"https://api.github.com/repos/OpenRA/OpenRA/pulls/15300","html_url":"https://github.com/OpenRA/OpenRA/pull/15300","diff_url":"https://github.com/OpenRA/OpenRA/pull/15300.diff","patch_url":"https://github.com/OpenRA/OpenRA/pull/15300.patch"},"body":"This PR fixes the long-standing inconsistency (and similarly long-standing balance complaint from parts of the community) where MCVs (but no other actors) can opt out of the chronoshift return by simply deploying (and then optionally undeploying) before the timeout expires.\r\n\r\nThe timeout is now remembered across deploy/undeploy cycles, and if the MCV is deployed when the timer runs out it will be returned to its origin in the undeployed form.\r\n\r\nThe `ChronoshiftReturnTransformedActor` trait, like the rest of the Chronoshift logic, lives in the Mods.Cnc dll and therefore is not considered a general purpose trait.  There are a number of additional things that could be added to it as part of any future migration to Mods.Common, but for now these are out of scope.\r\n\r\nFixes #13473."},"comment":{"url":"https://api.github.com/repos/OpenRA/OpenRA/issues/comments/401600227","html_url":"https://github.com/OpenRA/OpenRA/pull/15300#issuecomment-401600227","issue_url":"https://api.github.com/repos/OpenRA/OpenRA/issues/15300","id":401600227,"node_id":"MDEyOklzc3VlQ29tbWVudDQwMTYwMDIyNw==","user":{"login":"WhoCaresora","id":28893854,"node_id":"MDQ6VXNlcjI4ODkzODU0","avatar_url":"https://avatars2.githubusercontent.com/u/28893854?v=4","gravatar_id":"","url":"https://api.github.com/users/WhoCaresora","html_url":"https://github.com/WhoCaresora","followers_url":"https://api.github.com/users/WhoCaresora/followers","following_url":"https://api.github.com/users/WhoCaresora/following{/other_user}","gists_url":"https://api.github.com/users/WhoCaresora/gists{/gist_id}","starred_url":"https://api.github.com/users/WhoCaresora/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/WhoCaresora/subscriptions","organizations_url":"https://api.github.com/users/WhoCaresora/orgs","repos_url":"https://api.github.com/users/WhoCaresora/repos","events_url":"https://api.github.com/users/WhoCaresora/events{/privacy}","received_events_url":"https://api.github.com/users/WhoCaresora/received_events","type":"User","site_admin":false},"created_at":"2018-07-01T11:19:32Z","updated_at":"2018-07-01T11:19:32Z","author_association":"NONE","body":"I find that decision odd as well. I alwais saw the chrono basepush or \"chrono hidden backline base\" as a legit and valid strat in either 1V1 or teamgame. It is balanced as you know when its happen and like a simple basepush you have the same resources as yourt enemy to counter it if no more.\r\n\r\nAccording to my memory to the old cnc, i never used the chrono in skirmish to attack but i remember it was my way to safely pull back in my base an ennemy's conyard after an enge cap and undeploying. So it was present in the original. \r\n\r\nAs a well establish mechanism and known by mostl players I don't see why it should be changed. It is not harder to counter than execute. \r\n\r\n By making tyhis change you will just make it more costly, the work around is simple : prepare a war factory and an mcv on hold ready to exit : chronoshift, deploy : place WF : unhold the mcv and .... there you go same thing, 2000$ more costly and stronger because you have a vehicule production right on the spot instead of only cheap barrack and infantry. You can even use one of your expansion conyard as it will chrono-return safely after the operation.\r\n\r\nAs for IC, if it can be transfered on mcv -> conyard and vice versa, i fear (personal pov) it can become way stronger to start basepush or retreat an mcv safely for soviet. Right now it has a nice balance as you have to time your mcv movement deployement and IC application following what you want to protect; Standing basepushing conyard or retreating mcv. The transfert of IC would give too much flexibility for the soviet player to play with the mcv. But i would playtest it to make my mind.\r\n\r\n"}}
{"actor":{"display_login":"WhoCaresora"}}