You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
------ Original Message ------
From: "Oliver Burnett-Hall" ***@***.***>
To: "ollybh/18xx" ***@***.***>
Cc: "ianwilson156" ***@***.***>; "Author"
***@***.***>
Sent: Saturday, 12 Nov, 22 At 12:33
Subject: Re: [ollybh/18xx] 1858: connectivity check is wrong when
trading in a private (Issue #29)
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?
—
Reply to this email directly, view it on GitHub
<#29 (comment)> , or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/ASJS6KJDSKYO46VMXALYSULWH6E73ANCNFSM6AAAAAAR6ILPC4>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
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.
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.
The text was updated successfully, but these errors were encountered: