Motivation / Problem

Open a file, read something I wasn't expected, think about it once, think about it twice, realise we really did a poor job, fix it, leave the commit in the wrong branch for a few days, get reminded by it again, finally manage to PR it. Pfft.

Description

This was already removed from the "ci-build", but not yet from
"release".

Should have been done with 3dfee97#diff-68ba9d12f6f2601fe3c9f7f9d0d02aaea52384559d6d08fae7afc941663fdfcd , but here we are :)

Limitations

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

• The bug fix is important enough to be backported? (label: 'backport requested')
• This PR affects the save game format? (label 'savegame upgrade')
• This PR affects the GS/AI API? (label 'needs review: Script API')
  • ai_changelog.hpp, gs_changelog.hpp need updating.
  • The compatibility wrappers (compat_*.nut) need updating.
• This PR affects the NewGRF API? (label 'needs review: NewGRF')
  • newgrf_debug_data.h may need updating.
  • PR must be added to API tracker