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

Involuntary cargo exchange with cargodist via neutral station #6114

Closed
DorpsGek opened this issue Sep 14, 2014 · 5 comments
Closed

Involuntary cargo exchange with cargodist via neutral station #6114

DorpsGek opened this issue Sep 14, 2014 · 5 comments
Assignees
Labels
bug Something isn't working flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) patch from FlySpray This issue is in fact a Patch, but imported from FlySrpay

Comments

@DorpsGek
Copy link
Member

planetmaker opened the ticket and wrote:

When two players serve a neutral station at an industry, a cross-company chain for cargo flow can and will be established which can only be interrupted if one of the players stops competing for the ressources of that industry.

It's a fun thing, but as it's unvoluntary sharing, it would at least need some way the players can control whether they want to share or not.

See the attached screenshot and savegame where fish is carried from all fishing grounds of yellow company via the Koudenhoek Fish Market, the neutral fishing ground De Falom Sandbank to the blue player's Den Haag Fish Market fishing harbour (and also vice versa).

Attachments

Reported version: 1.4.3-RC1
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/6114
@DorpsGek
Copy link
Member Author

fonsinchen wrote:

There is an easy fix for this: If you are loading at the shared station make the order "no unload" and if you're unloading make it "no load". Cargodist will then figure out that it should not create such a route. Is that sufficient?


This comment was imported from FlySpray: https://bugs.openttd.org/task/6114#comment13559

@DorpsGek
Copy link
Member Author

andythenorth wrote:

Discussed with planetmaker & frosch - can be moved to known_bugs.txt and closed. Patch attached.

Attachments


This comment was imported from FlySpray: https://bugs.openttd.org/task/6114#comment14596

@DorpsGek
Copy link
Member Author

peter1138 wrote:

Not sure documenting a known bug counts as closing a bug...


This comment was imported from FlySpray: https://bugs.openttd.org/task/6114#comment14669

@DorpsGek
Copy link
Member Author

andythenorth wrote:

Well it's feature eh? :)


This comment was imported from FlySpray: https://bugs.openttd.org/task/6114#comment14671

@DorpsGek DorpsGek added Core flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 7, 2018
@TrueBrain
Copy link
Member

TrueBrain commented Apr 13, 2018

@andythenorth I expect a Pull Request from you addressing this soon :) (fully agree that known-bugs is sufficient)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) patch from FlySpray This issue is in fact a Patch, but imported from FlySrpay
Projects
None yet
Development

No branches or pull requests

4 participants