Unknown switch: 0B27

[2024.12.17 09:12:57.71] ================================================
<< Received packet:      014C - Guild Allies / Enemy List [68 bytes]   2024.12.17 09:12:57
  0>  4C 01 44 00 00 00 00 00    03 00 00 00 A1 F7 B0 A2    L.D.............
 16>  CB B9 BC D3 B5 C2 A1 F7    A1 BA CF C9 B9 AC A1 BB    ................
 32>  00 00 00 00 00 00 00 00    05 00 00 00 A1 BC 4D 75    ..............Mu
 48>  6D 61 A1 BD C2 EA BF A8    B0 CD BF A8 EC E1 A1 EE    ma..............
 64>  00 00 00 00                                           ....
[2024.12.17 09:12:57.71] Your guild is ally with guild 3 (△阿斯加德△『仙宫』)
[2024.12.17 09:12:57.72] Your guild is ally with guild 5 (〖Muma〗玛卡巴卡灬☆)
[2024.12.17 09:12:57.73] ================================================
<< Received packet:      0B27 [5 bytes]   2024.12.17 09:12:57
  0>  27 0B 05 00 03                                        '....
[2024.12.17 09:12:57.73] Packet Parser: Unknown switch: 0B27

#if PACKETVER_MAIN_NUM >= 20190731 || PACKETVER_RE_NUM >= 20190717 || PACKETVER_ZERO_NUM >= 20190814
struct PACKET_ZC_GUILD_AGIT_INFO {
	int16 packetType;
	int16 packetLength;
	int8 castle_list[];
} __attribute__((packed));
DEFINE_PACKET_HEADER(ZC_GUILD_AGIT_INFO, 0x0b27);
#endif

Start at the packet parser handling the reported 0x0b27 switch and compare it with the provided PACKET_ZC_GUILD_AGIT_INFO definition and packet length. Done means the five-byte packet is recognized and its castle-list data is handled without an “Unknown switch” message; no file or test path is named in the issue.