Skip to content
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

Handle moving conductors #406

Open
numberZero opened this issue May 2, 2018 · 1 comment
Open

Handle moving conductors #406

numberZero opened this issue May 2, 2018 · 1 comment

Comments

@numberZero
Copy link
Contributor

From #404:

Place a mesecon at the crosshair, and it will crash.
WARNING: it breaks the world! Removing mesecon_actionqueue is mandatory after such experiment, and there may be consequences.
screenshot_20180218_221747
The reason is that it can’t handle moving conductors well at all. It queues activation of the left movestone, but on the next step, the right movestone moves first, substituting it with the gate. The gate expects a named rule, but gets unnamed one that was queued for the movestone.

@numberZero
Copy link
Contributor Author

See also #405, #502.

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

No branches or pull requests

1 participant