-- benilla's own: tolerate the server's AIO blocks this client has no feature for.
--
-- AIO dispatches a server block by name through `AIO_BLOCKHANDLES`, and an unregistered name is
-- an `error()` (`AIO.lua:547-549`). That is the right shape — except **pfUI replaces the global
-- `error` with one that prints to chat and returns** (`pfUI.lua:453-460`, which it does to feed
-- `seterrorhandler`). A non-raising `error` turns AIO's clean abort into a fall-through: the
-- next line calls the handler it just failed to find, so the player sees two errors, the real
-- one being `attempt to call local 'handledata' (a nil value)` at `AIO.lua:558`.
--
-- That is pfUI's bug and it would bite the reference client the same way; what changed here is
-- only that benilla now loads AIO at all (for the calendar). So the blocks this client does not
-- implement are registered as no-ops, which is what "no handler" was always supposed to mean.
--
-- `OctoRadio`: the realm's radio is driven entirely from the client — a station click sends
-- `.radio <n>` as a SAY command and the server answers with `SMSG_PLAY_MUSIC`
-- (`OctoRadioPlaceholder.lua`'s own header says so, and that file contains no AIO call at all).
-- Whatever this block carries is therefore supplementary to a feature that already works, so
-- dropping it costs nothing visible. Logged once so a block that turns out to matter is still
-- findable.
if AIO and AIO.RegisterEvent and not AIO_SERVER then
    local ignored = { "OctoRadio" }
    for _, name in ipairs(ignored) do
        AIO.RegisterEvent(name, function()
            -- Nothing: the block is for a feature this client does not implement.
        end)
    end
end