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

1858: connectivity check is wrong when trading in a private #29

Closed
ianwilson156 opened this issue Nov 12, 2022 · 4 comments
Closed

1858: connectivity check is wrong when trading in a private #29

ianwilson156 opened this issue Nov 12, 2022 · 4 comments
Assignees
Labels
1858 Affects the 1858 implementation bug Something isn't working

Comments

@ianwilson156
Copy link

SR5: succeeded in swapping the C&B into the TBF, but the connection was only by mixed gauge (broad, then narrow, then broad). The game then refused to proceed "game is broken", and wouldn't even undo the illegal action.

@ollybh
Copy link
Owner

ollybh commented Nov 12, 2022

That's not good. Can you export the JSON for the game and send it to me? Or is the game so broken that you don't get the option to export it?

@ianwilson156
Copy link
Author

ianwilson156 commented Nov 12, 2022 via email

@ollybh ollybh added bug Something isn't working 1858 Affects the 1858 implementation labels Nov 12, 2022
@ollybh ollybh self-assigned this Nov 12, 2022
@ollybh
Copy link
Owner

ollybh commented Nov 14, 2022

Not received 😞 Can you try sending the JSON file again?

@ollybh
Copy link
Owner

ollybh commented Nov 14, 2022

I can't reproduce this one. I've removed the last few actions from the JSON, to just before Player 1 merged C&B into TBF. The only companies that can acquire C&B are N and MZA. There's no option to swap C&B for a share in TBF. So I'm going to close this issue.

However, that file does show a different bug: there's not an option to swap C&B for a share in A, even though there's a broad/dual gauge route from A's token in Madrid to Bilbao. I'd not noticed this before, but this is from the same cause as issue #1. I thought that was just giving you an extra step where no token was possible, but this is a definite bug.

@ollybh ollybh closed this as not planned Won't fix, can't repro, duplicate, stale Nov 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1858 Affects the 1858 implementation bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants