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

Autorenew to manage in same way as Autoreplace #1321

Closed
DorpsGek opened this issue Oct 9, 2007 · 1 comment
Closed

Autorenew to manage in same way as Autoreplace #1321

DorpsGek opened this issue Oct 9, 2007 · 1 comment
Labels
flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Oct 9, 2007

vc-labs opened the ticket and wrote:

Here is the in-game situation:
- I have a group of hundred small Opel mailtrucks (Pika's RVS 3.34), which I want to stay unchaged forever (they use to burst mail generation in towns a lot, making a good profit at same time). I don't want to enable Global Autorenew, because I don't want other vehicles to be silently renewed. Meanwhile, I want Autorenew to be applied to that mentioned mailtrucks group (so it wouldn't bother me anymore).
Would I want to Autoreplace these mailtrucks - no problem, - this feature is already manageable. But I cannot set the group for Autorenew.

As it currently designed, there is an Icon: "Protect this group from Global Autorenew".
I'd suggest to replace it to (or add another one): "Set Autorenew for this group".

*) One minor issue about this mentioned button: it's currently unclear from the icon if protection is set or not. If you decide to implement this requested "Autorenew" functionality, I'd suggest radio-switch: "Autorenew/Autoreplace", so it would be perfectly clear which function set active.

Reported version: trunk
Operating system: All


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

andythenorth closed the ticket.

Reason for closing: Won't implement

Interesting suggestion, but this level of fine-grained control is not a current goal for OpenTTD. This would add complexity this would add complexity in both code and playing experience, notably to the groups implementation and usability which are already creaking and need to not have even more piled on top. Thanks for the suggestion.


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

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

No branches or pull requests

1 participant