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

Make "Transfer" default order in the button instead of "Unload all" #3847

Closed
DorpsGek opened this issue May 19, 2010 · 9 comments
Closed

Make "Transfer" default order in the button instead of "Unload all" #3847

DorpsGek opened this issue May 19, 2010 · 9 comments
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

perk11 opened the ticket and wrote:

"Transfer" is used much more often. "Unload all" is only usefull with newgrfs when industry's acceptance of cargo is limited and cargo which is not accepted may be transfered to another place. This is quite rare case and "Transfer and leave empty" is used almost in every game when it comes to feeder service.

Reported version: Version?
Operating system: All


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

Alberth wrote:

Every newbie will fail to understand that he has to change the unload order in order to get paid for his deliveries.
This will result in dozens of bug reports every week.

As for transfer being used more often, I think it depends on the kind of game that you play. If you make many seperate point-to-point connections, you never need transfer.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment8077

@DorpsGek
Copy link
Member Author

perk11 wrote:

I don't mean default order at all, I mean default when you click the button.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment8078

@DorpsGek
Copy link
Member Author

V453000 wrote:

To use properly working drop orders, you SHOULD be using (unload and leave empty) because for example:
- Near your coal drop spawns a coal mine. Trains without "leave empty" will start picking up the cargo, which will mess your network.
- The industry closes (due to whatever reasons or conditions), the same for example when a town stops accepting goods

As for transfer games, you still need to have trains that drop it, so I think "transfer" is still much less used than "unload". Additionally as Alberth says, it would just make less sense :)


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment9539

@DorpsGek
Copy link
Member Author

perk11 wrote:

V453000, "Transfer and leave empty" works just like "Unload and leave empty" in situatuion you've described. The only difference is that with Transfer order you don't get a vehicle/train/aircraft with negative profit value and this is bad for rating. So if you don't care about rating you may use whatever you want - Transfer or Unload all, if you don't use newgrfs which limit capacity of what production industry can accept, id doesn't make sense. But some people do care (or why this rating still exists in the game?). And some (including me) just don't like having negative profits for vehicles.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment9540

@DorpsGek
Copy link
Member Author

V453000 wrote:

as far as I know, transfer order TRANSFERS the cargo so that no industry nearby can accept it but it remains in the station, where unload order DELIVERS it to that station ... and if it isnt accepted, then it remains.

By the way I thought the point of this issue is that you want to have transfer orders faster reachable in the settings. Since 80% people do not even know what transfer does and not many people use transfer order frequently, "unload" on the first place makes good sense. :) (not mentioning that it basically is a header of "unload menu")


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment9541

@DorpsGek
Copy link
Member Author

perk11 wrote:

But why do you often need to unload cargo if it can't be accepted?
You were right about the point of this issue. And do many people know what unload does?
And menu may be renamed


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment9542

@DorpsGek
Copy link
Member Author

V453000 wrote:

But why do you often need to unload cargo if it can't be accepted?

When it isn't accepted, it usually means that it is temporarily not accepted, thus it should be accepted again (either if you re-fund the industry that died, or grow the town back to accept goods), then:
With "unload and leave empty"
Your trains will keep doing everything as if nothing happened, there will only be stockpiling cargo at the drop station.
More important is that trains will return back to pickups and load, which they couldn't if they didn't unload the cargo.
On the first look, it might seem like there is a downside that trains do not make money at this point. But they actually do, just make a dummy train to load it and drop to deliver it.

With "nothing"
Your trains will stop delivering the cargo and will return back to the pickups full, providing no service what so ever.

With "no loading"
Your trains will not start loading if there spawns a new primary near the primary drop, so that is good, but they drop the same way as "nothing" trains.

As you might see, there IS a reason why to apply proper "unload and leave empty" orders for EVERY train that is dropping something (expecting it shouldn't load again), and since transfer is only situational and definitely less used than unload, this feature request makes in my opinion no sense. :) Transfer has already been made more comfortable by automatically adding the "leave empty", which is nice :).


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment9543

@DorpsGek
Copy link
Member Author

perk11 wrote:

I see your point now. The order you use most depends much on playing style. So I think this issue should be changed to "Change default orders on the buttons in the settings"


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847#comment9546

@DorpsGek
Copy link
Member Author

andythenorth closed the ticket.

Reason for closing: Won't implement

Not worth changing this. Orders are orders. There's no clear obvious correct choice, and changing it to suit one style will irritate those who are accustomed to the other style. Thanks.


This comment was imported from FlySpray: https://bugs.openttd.org/task/3847

@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) enhancement labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant