There are actually two modes of operation for this:
wl_force_addr1 / wl_force_addr2 contain even/odd addresses (even/odd seconds after :30 correspond to these two slots alternating), which allows the master to communicate intensely with 2 specified addresses. They may even be the same, so setting/reading timers for example can be coordinated in a single burst of activity.
:30 :31 :32 :33...
SYNC A1 A2 A1...
via wl_force_flags - there exists a longer sync packet variant (distinguished by length) that contains 32bit force flags bitmap instead of 2 byte wl_force_addr* specification. This mode enables the master to communicate with clients enumerated by set bits in the wl_force_flags (client 0 has position 0 in the flags, 1 has bit 1, etc.)
It is needed to wake the clients up before their low frequency reporting happens.