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

[1837] Cannot token by reverse over junction #11600

Open
ianwilson156 opened this issue Mar 3, 2025 · 2 comments · May be fixed by #11602
Open

[1837] Cannot token by reverse over junction #11600

ianwilson156 opened this issue Mar 3, 2025 · 2 comments · May be fixed by #11602
Assignees
Labels
1837 rules-broken Game comes to the wrong outcome compared with the rules (fixing these will break games)

Comments

@ianwilson156
Copy link

ianwilson156 commented Mar 3, 2025

https://18xx.games/game/199252

BH is running for the first time in OR6.1, it lays a tile in its home (Sarajevo), and it should be able to place a token e.g. in Marburg (reversing over the junction in O19), but the program is skipping the lay token step.

This is a special rule for 1837, that you can token by reversing over a junction. I suspect that this used to work previously.

@ollybh ollybh added rules-broken Game comes to the wrong outcome compared with the rules (fixing these will break games) 1837 and removed needs triage labels Mar 3, 2025
@ollybh
Copy link
Collaborator

ollybh commented Mar 3, 2025

BH's turn starts at action 782. The token step is being skipped.

There's definitely code added to 1837 to allow for backtracking when placing tokens. Not sure why it's not working here.

@ollybh ollybh assigned crericha and ollybh and unassigned crericha Mar 3, 2025
@ollybh
Copy link
Collaborator

ollybh commented Mar 3, 2025

Got it, the token step isn't using the graph that includes the backtracking.

ollybh added a commit to ollybh/18xx that referenced this issue Mar 3, 2025
1837 has two graphs: a standard one and one that allows track to
backtrack at junctions. The latter is needed for placing station tokens,
where this type of route is allowed.

The token step was not using this graph, it was using the standard one.
This meant that not all possible token locations were being included,
and an auto-pass was being generated for the token step if the only
possible token locations involved backtracking.

Fixes tobymao#11600.
@ollybh ollybh linked a pull request Mar 3, 2025 that will close this issue
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1837 rules-broken Game comes to the wrong outcome compared with the rules (fixing these will break games)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants