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

Vehicle Groups: create group from vehicles in station list. #1308

Closed
DorpsGek opened this issue Oct 8, 2007 · 4 comments
Closed

Vehicle Groups: create group from vehicles in station list. #1308

DorpsGek opened this issue Oct 8, 2007 · 4 comments
Labels
enhancement Issue would be a good enhancement; we accept Pull Requests! flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) stale Stale issues

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Oct 8, 2007

vc-labs opened the ticket and wrote:

With too many vehicles in game it's practically impossible to group vehicles for Autoreplace dealing with whole list.
It would be much easier to do it on per-station basis, dealing with the only vehicles binded to that station; especially due the fact, that the vehicles binded to same station usually logically grupped by user to share same route and cargo.

I would consider a little more automation:
- Automatically group vehicles with same orders (route), model and refiting.

Reported version: trunk
Operating system: All


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

sulai wrote:

"same station" groups already exist: click on a station and then on the little train in the lower right of the window.

Anyway, "same station" vehicle lists and "shared orders" vehicle lists should be treated as groups. I developed some details about how to do this: http://wiki.openttd.org/index.php/User:Sulai/new_feature_concepts/FlexibleVehicleList

model- and vehicle based groups are already implemented by this patch: http://www.tt-forums.net/viewtopic.php?f=33&t=36648


This comment was imported from FlySpray: https://bugs.openttd.org/task/1308#comment3969

@DorpsGek
Copy link
Member Author

andythenorth wrote:

There is currently no way to create a group based on same-station. That would be a useful improvement imho. It's non-trivial to design, because it needs to consider how/if vehicles are moved from their existing groups.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1308#comment14532

@DorpsGek
Copy link
Member Author

DorpsGek commented Sep 1, 2017

andythenorth wrote:

I've retitled this, as I think it's really about how groups are created. I think creating groups from station lists (1) would be a very useful feature when playing (2) has to consider a lot of awkward behaviour as it must move vehicles from other groups, which not be what players want.

The current groups implementation is based on a vehicle being in one-and-only-one group. which is the only sustainable way (to avoid, e.g. autoreplace circular replacements). Being in multiple groups would perhaps make more sense when creating station groups, but does't look viable to me.


This comment was imported from FlySpray: https://bugs.openttd.org/task/1308#comment14695

@DorpsGek DorpsGek added Autoreplace flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) labels Apr 6, 2018
@andythenorth andythenorth added the stale Stale issues label Jan 5, 2019
@andythenorth
Copy link
Contributor

andythenorth commented Jan 7, 2019

Although this would be nice to have, it isn't something we expect to fulfill in the next year, and on that basis I'm closing it. We do this to keep the project manageable, productive and fun. We hope you do understand. Thanks for contributing though! Here you can find more about how we handle feature requests.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Issue would be a good enhancement; we accept Pull Requests! flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) stale Stale issues
Projects
None yet
Development

No branches or pull requests

2 participants