New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Undeploying a chrono MCV at just the right moment duplicates the MCV #15793

Open
ashleynewson opened this Issue Nov 5, 2018 · 0 comments

Comments

Projects
None yet
2 participants
@ashleynewson

ashleynewson commented Nov 5, 2018

Issue Summary

When a chrono MCV is undeployed at just the right moment it is erroneously duplicated.

System Information

  • OpenRA Version: release-20180923 (compiled locally)
  • Mod: Red Alert

Additional Information:

  • Steps to reproduce

    1. Start a game
    2. Create chronosphere
    3. Chronoshift an MCV
    4. Deploy the MCV
    5. Wait until chronoshift period is almost over and undeploy the MCV such that the undeployment finishes at exactly the same time as the chronoshift period ends.
    6. There will now be two MCVs: one in the chrono-return position and another in the undeployment position.
  • OpenRA Replays

@abcdefg30 abcdefg30 added the Bug label Nov 5, 2018

@abcdefg30 abcdefg30 added this to the Hotfix release milestone Nov 5, 2018

@ashleynewson ashleynewson changed the title from Undeploying a chrono MCV as just the right moment duplicates the MCV to Undeploying a chrono MCV at just the right moment duplicates the MCV Nov 5, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment