HttT S17: Update to comply with current Wesnoth Lua API specifications

[Wedge009]

Resolves #6517

It might be obvious to experienced Lua API users but it's not a direct translation to map.special_locations as per https://wiki.wesnoth.org/LuaAPI/UpdatingFrom14, but rather wesnoth.current.map.special_locations.

I tested this in master and believe it can/should be back-ported to 1.16.

[CelticMinstrel]

It might be obvious to experienced Lua API users but it's not a direct translation to map.special_locations as per https://wiki.wesnoth.org/LuaAPI/UpdatingFrom14, but rather wesnoth.current.map.special_locations.

That is what the linked page says though – right at the top is a note explaining that wesnoth.current.map has been abbreviated to map.

EDIT: Top of the section, not the page

[Wedge009]

Oh, okay. I completely missed that note because I just did a search for 'special_locations'. Even knyght made no mention of it in #6517.

[stevecotton]

Please would you change the commit message to have "HttT S17" in the title? When looking at the history later, the current "Comply with current Lua API specifications" will sound like something to do with Vultraz' "Upgrade to Lua 5.4.4" change.

[Wedge009]

It looks like the CI failures were introduced with #6527, not this very small change.

[stevecotton]

Schema verification and WML tests all passed, so I'm happy to merge this without rerunning the CI (I believe rerunning the job without pushing a new commit would retry with the exact same source, excluding the fix for the Doxygen issue).

[Wedge009]

Thank you for merging. Back-ported in 0607f31.