Filterning terrains without overlay doesn't work as intended?

[BajMic]

According to the wiki:

The overlay (including the preceding ^) is optional; if omitted, only terrains without overlays can be matched.

So I tried:

Code: Select all

terrain=*

All terrains got matched.

Next, I tried:

Code: Select all

[not]
	terrain=*^*
[/not]

No terrain got matched. Is there a way of implicitly filtering out terrains with no overlays?

[Ravana]

Confirmed. Seems you have to filter by terrain code.

Code: Select all

$ #wesnoth.get_locations{formula="1-contains_string(id, '^')"}
636
$ #wesnoth.get_locations{formula="contains_string(id, '^')"}
234
$ #wesnoth.get_locations{}
870

[Spannerbag]

Edited out because of Ravana's far superior method below
FWIW you can replicate Ravana's logic in WML, I've done some brief testing and here's what happened on v1.16.8...

Cheers!
-- Spannerbag

[Ravana]

You dont need such tricks, standard location filter is same logic no matter if you call it from wml or Lua.
So formula="1-contains_string(id, '^')" instead of terrain=

[Spannerbag]

You dont need such tricks, standard location filter is same logic no matter if you call it from wml or Lua.
So formula="1-contains_string(id, '^')" instead of terrain=

Ah, cool. The code below worked first time

Code: Select all

    [store_locations]
      terrain=*^*
      variable=terrain_all
      include_borders=no
    [/store_locations]
    [store_locations]
      formula="contains_string(id, '^')"
      variable=terrain_with_overlays
      include_borders=no
    [/store_locations]
    [store_locations]
      formula="1 - contains_string(id, '^')"
      variable=terrain_without_overlays
      include_borders=no
    [/store_locations]

Handy to know, thanks.

Cheers!
-- Spannerbag

[Celtic_Minstrel]

Note: I recommend using not instead of 1 - in that formula. It has the same effect but gets the intended meaning across better.