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

NewGRF cannot configure purchase prices per wagon #6581

Closed
DorpsGek opened this issue Jul 5, 2017 · 1 comment
Closed

NewGRF cannot configure purchase prices per wagon #6581

DorpsGek opened this issue Jul 5, 2017 · 1 comment
Labels
component: NewGRF This issue is related to NewGRFs enhancement Issue would be a good enhancement; we accept Pull Requests! flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

DorpsGek commented Jul 5, 2017

mb opened the ticket and wrote:

For running costs, a newgrf may set different base amounts, but for purchase prices, the game does use hard-coded memory locations, e.g. for train engines and train "wagons". This results into a very limited variety, especially because "wagons" covers (more expensive) coaches as well as (cheaper) freight cars.

In addition, making purchase base cost addresses available to newgrfs would allow to use different base costs with different multipliers, which is not possible ATM.

Reported version: trunk
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/6581
@DorpsGek DorpsGek added flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) Vehicles labels Apr 7, 2018
@TrueBrain TrueBrain changed the title Vehicles: make vehicle purchase base cost address available like running cost base address is NewGRF cannot configure purchase prices per wagon Apr 13, 2018
@TrueBrain TrueBrain added component: NewGRF This issue is related to NewGRFs enhancement Issue would be a good enhancement; we accept Pull Requests! and removed Vehicles labels Apr 13, 2018
@andythenorth
Copy link
Contributor

andythenorth commented Jan 5, 2019

I ran into limitations with purchase cost ranges recently.

To solve this, frosch indicated I should set them via cb 36 rather than property. This gives a range of ~32000 return cost factors, rather than just 255. In combination with appropriate base cost factor, I was able to set costs appropriately.

I'm closing this as I think it's very unlikely to be addressed further. Thanks.

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

No branches or pull requests

3 participants