Game version: 1.30.164078 (dedicated server, stable). Not reproducible on 1.29 and earlier.

Summary: Since the 1.30 server build, the no3rd tag in the A2S INFO keywords string is emitted with inverted meaning. Historically, a server with disable3rdPerson = 1; in serverDZ.cfg advertised no3rd in its keywords, allowing launchers and server browsers to detect first-person-only servers. On 1.30, third-person servers advertise no3rd, and servers with disableThirdPerson = 1 no longer do.

Evidence (live 1.30.164078 servers, sampled 2026-10-17):

• 14/14 servers with "3PP" in their name advertise no3rd

• 15/15 servers with "1PP" in their name do not advertise it

• 83.6% of all 1.30 servers advertise no3rd (matches the actual third-person server share) vs 15% of 1.29 servers marked 1PP

1. Start a 1.30 dedicated server with disableThirdPerson = 1; and query it (A2S INFO, port = query port): keywords: battleye,external,privHive,shardABC123,lqs0,etm4.000000,entm5.000000,mod,isDLC4,09:32 — no no3rd, despite being 1PP. Example: 217.196.148.212:7716 — "COLDBREWZ Badlands - Nasdara | PvP | vanilla 1PP"

2. Start/query a 1.30 server with third person enabled: keywords: battleye,no3rd,external,privHive,shard123ABC,lqs16,etm5.000000,entm3.950000,mod,isDLC4,11:18 — no3rd present, despite being 3PP. Example: 51.38.89.140:27016

3. The same servers on 1.29 advertise the tag correctly.

Actual result: Third-person servers report no3rd; first-person-only servers do not. Every launcher and server browser relying on the keyword (DZSA Launcher, DZHub, dayz-py-launcher, Steam server browser extensions) shows 1PP servers as 3PP and vice versa on 1.30.

no3rd present only when disable3rdPerson = 1;.