Proposal - Cargo Class refinement

[andythenorth]

\o/

[michael blunck]

\o/

Oh yeah. Even more mess to play with. Why use 3 when you might get 5? Bloated ...

regards
Michael

[andythenorth]

Why use 3 when you might get 5? Bloated ...

Ah well, hopefully grf v8 might remove prop 1D (trains, and equivalent for other vehicle types).

Then there's 50% less bloat

[Yexo]

Why use 3 when you might get 5? Bloated ...

Ah well, hopefully grf v8 might remove prop 1D (trains, and equivalent for other vehicle types).

Then there's 50% less bloat

There is absolutely no reason to remove that property. Just don't use it anymore (since I don't see a reason to do so with the two new properties available).

[andythenorth]

There is absolutely no reason to remove that property. Just don't use it anymore

Couldn't same be said for cb11, which is being removed for grf v8? Or is that a different case?

EDIT - after discussion: deprecating a prop is indeed different to deprecating a callback. So the prop is unlikely to be deprecated for grfv8.

However it could be marked as 'do not use for grfs targeting ottd only', as there is no reason to use it in that case.