Merge lp://staging/~widelands-dev/widelands/bug-1767187-preciousness into lp://staging/widelands

Works nicely. Also code looks good. It can go...

But I still think we need a max value for preciousness (this is for future discussion)

Since this function is verified now, might it be sufficient for whoever edits the init.lua files to pick sensible values? We could add a recommendation to the documentation in data/tribes/wares/armor.lua. If we want to enforce it, I would enforce it upon tribe loading in src/logic/map_objects/tribes/ware_descr.cc. This way, we will only need to check it once per game.

I am strongly for enforcing the max value. Just to avoid surprises in the future. Or rather unexpected behavior...

Will I open new bug report so that we can discuss the issue there? Or will we do it in this branch?

Let's have a new bug for this, so that we can get this branch in. It's blocking you from training the AI.

BTW this particular surprise can't happen again now, because it's checked. Let's discuss the details in a bug though, it will be hard to follow this up later if the discussion is in a merge request.

@bunnybot merge

Continuous integration builds have changed state:

Travis build 3427. State: failed. Details: https://travis-ci.org/widelands/widelands/builds/373538965.
Appveyor build 3232. State: success. Details: https://ci.appveyor.com/project/widelands-dev/widelands/build/_widelands_dev_widelands_bug_1767187_preciousness-3232.

Refusing to merge, since Travis is not green. Use @bunnybot merge force for merging anyways.

Travis build 3427. State: failed. Details: https://travis-ci.org/widelands/widelands/builds/373538965.

@bunnybot merge

Continuous integration builds have changed state:

Travis build 3438. State: passed. Details: https://travis-ci.org/widelands/widelands/builds/373854929.
Appveyor build 3243. State: success. Details: https://ci.appveyor.com/project/widelands-dev/widelands/build/_widelands_dev_widelands_bug_1767187_preciousness-3243.