Skip to main content
The Alliance Duel (“VS”) is a weekly alliance-versus-alliance event with one theme per server day. The client learns today’s theme, scoring list, and chest thresholds from one detail read of activity 55000. This page covers that read as the wire shows it, the tables that give the scoring list its meaning, and how goclient’s features use it. Facts confirmed against production on 2026-10-06 are marked confirmed live; everything else is static-analysis-only, from the 1.0.364 Lua and tables.

Finding today’s entry

The init activity entry

The init push’s activity map carries the duel as activity 55000 (type 14, EnumActivity.AllianceCompete). Confirmed live, the entry is:
It’s the only entry in the live activity map, among the types goclient knows, that carries an activityid different from its id (confirmed live, 2026-10-06).

The detail read must send activityid

ActivityInfoData:ParseActivityData sets activityId from the entry’s id, then overrides it with activityid when one is present (ActivityInfoData.lua:129-131, 163-164, 1.0.370). AddOneActivity sends that value for the duel, as a UtfString (ActivityListDataManager.lua:166-175):
Confirmed live: asked for "55000", the server answers with a bare {success=true} and no eventList, and no second message follows. The client would ignore that reply anyway: ActivityEventInfoGetMessage processes a reply only when it has no success key (ActivityEventInfoGetMessage.lua:26). Asked for "70000", the reply carries the data directly.

The reply

Top level, confirmed live: activityId ("70000"), type (15, the duel event type), ranking, isFix, and eventList. The client routes it by type == 15 (ActivityListDataManager.lua:1180-1186). Each eventList entry, field names as confirmed live: Pick the entry with t == 15 whose window contains now. Don’t fall back to another entry: a stale entry’s scoring list belongs to another day.

The week

TB:heroactivity#70000, the type-15 row, maps the server weekday to a theme (static-analysis-only): The server day starts at 02:00 UTC, see Identity, login & session. Confirmed live on Tuesday 2026-10-06: theme 110001, with the window ending at 02:00 UTC.

The scoring list

Each id in score is a row of the score table: {id, type, value, points}, where type is a ScoreType, value narrows it, and points is the base award per unit. The client gates its duel prompts by score type, not by theme (AllianceCompeteDataManager.lua:631-654). Its predicted award is units × points × (1 + Σ effects) (GetAllyDuelScoreInfo.lua:39-43). Score types goclient uses (ScoreType, EnumType.lua:15728-15744, plus table types): Type 51 is keyed by the queue an item is used on, not by the item’s own kind. The 2026-10-06 (Base Expansion) entry listed eight ids, confirmed live: goclient embeds the whole table (1,486 rows, tables 40413) in internal/game/duel_scores_gen.go, which also holds the lw_hero (398 heroes: quality, max rank, max honor level) and officer_recruit (30 pools: type, time type, wish list) rows the duel features read. The generator, internal/game/genduelscores, reads a decoded score.json and the two other tables from the same directory, checks known rows before writing, and refuses another table or shifted columns:

The score push

push.act.score.obtain reports earned points for score events: Arms Race always, and the Alliance Duel when type == 15 (PushActScoreObtainMessage.lua:6-16; static-analysis-only). The duel branch feeds GetDuelScoreManager:PushScoreChangeByType, which reads the added points and the alliance total. Nothing in the client waits for it. goclient logs every one at Info as activity score obtained, with afterCmd set to the last request sent on the connection. A push that arrives after a run’s last read isn’t seen.

Chest claims

A chest is claimed with the day’s actId and the chest’s threshold (static-analysis-only):
A chest is claimable when userScore.score has reached its target, its flag isn’t in newRewardFlagList, and its index is within the number of chests the account’s tech unlocks (3, 6, 9, or 12). Confirmed live: newRewardFlagList is a comma-joined list of claimed chest indexes, for example 1,2,3.

How goclient uses it

Every optional feature in goclient can declare the duel score types it earns (Feature.Duel, a list of {Type, Value}; an empty Value matches any). A feature with Hold set runs only on a day whose entry lists one of those types. With no current entry (Sunday, not in an alliance, the read failed) a held feature stays held. -list-features shows each feature’s policy as duel:hold, duel:always, or duel:-.
  • duelPolicy in the session config overrides a feature’s default: {"duelPolicy": {"radar-claims": "always"}}. Valid values are hold and always. An entry for an unknown feature, or with any other value (the match is exact, so Hold is ignored too), is warned about and ignored, so that feature keeps its default.
  • -run <feature> of a held feature is refused with the reason; -run-anyway runs it regardless. A spend feature still checks today’s scoring list inside its run, so -run-anyway on a non-scoring day sends nothing.
  • Status line: with any feature enabled, every run logs one alliance duel line: theme, score, next chest, and day end.
The duel-aware features are all off by default (finished-timers is one the production config enables); see the README for the full list. finished-timers holds each completion inside the run instead of declaring Feature.Duel, so it shows duel:- and duelPolicy doesn’t apply to it: duel-speedups-plan, secret-tasks-start-plan, radar-inventory, and the 1.0.370 additions duel-gacha-plan, secret-task-assist-plan (the allies’ finished Secret Tasks secret-task-assist would assist, never an assist) and explorer-treasure-plan (Explorer Treasure keys, never a chest open) are read-only previews. secret-task-assist (opt-in) sends hero.dispatch.assist for up to 5 allies’ finished Secret Tasks a day and declares no score type: no duel score row is an assist (the only Secret Task row, 90204, type 99, is “Perform a UR secret task”), so it is never held. Whether an assist on a UR task still books type-99 points is open; a push.act.score.obtain logged after hero.dispatch.assist on a Tuesday or Saturday would show it. Since the 1.0.370 fixes (static-analysis-only):
  • Wish confirmations. Before a pull from the recruit window the client may ask about the wish hero (LotteryInfo.lua:839-893): alert 1 when the pool shows a wish list and no wish hero is chosen; alert 2 or 5 when the chosen hero is owned at max rank (or max honor level) while another wish-list hero isn’t. duel-recruit-tickets keeps that pool’s tickets instead. A pool newer than the generated officer_recruit is pulled unless that question applies, and is logged. free-recruits still takes the free pull (a free pull does not stack) and logs a Warn naming the confirmation the window would have asked.
  • Finished timers wait for their day (the 1.0.370 follow-up). A finished upgrade is completed by the client’s free.building.upgrade.finish, whose reply carries the new level, and the duel’s go-to for building power (score 90202, type 23) points at a finished, uncollected upgrade (GoToUtil.lua:4440-4458). A finished research stays in its queue until queue.finish. So finished-timers holds a finished upgrade until a day that lists type 23 and a finished research until one that lists type 6, logging each held one with today’s theme and the days it waits for. It holds only in an alliance with the duel activity open and its info read; a rest day with no current entry holds too. Without a duel it finishes as before, and when the duel can’t be read (an error, no eventList, entries without a day window, or a current entry naming no known score id) it finishes with a Warn. A held research keeps its Tech Center’s queue idle until a scoring day, up to four days after a Saturday finish, and a held HQ upgrade delays everything gated on the HQ level.
  • Enemy Buster. On a day that scores type 51 4 but not type 4, duel-troop-training starts a batch only while a training speed-up item (200230-200235) is held and a run three hours later still falls before the day ends.
  • T11. The tier unlocks in season 4 from day 64 (soldier_eleven_param 4|64, from init playerServerSeasonInfo.seasonStartTime), and in any later season.
  • duel-speedups leaves a job that ends more than a year out; arms-race-chests claims only before the stage’s stage_end_time; secret-tasks-start skips a placement the server refuses; item counts read goodsId over itemId and itemLeftCnt over num over count, as the client does.

Speed-ups

The speed panel sends items in the items-only form (UISpeedView.lua:1540-1586):
  • The diamond forms are a useGold key (BuildCcdMNewMessage.lua:12-16, QueueCcdMNewMessage.lua:10-12, BuildingCampAccelMessage.lua:9-11) and, for queue.ccd.m.new, an empty itemIDs, which is the client’s own instant finish behind its diamond confirm (ArmyManager.lua:204-210, UISpeedUpConfirmView.lua:131-135). For a running research the client sends the same bytes as its free finish, but only inside the free research time, init effect 30100 (UIScienceView.lua:648-654, BuildBubbleManager.lua:4123-4128). goclient doesn’t send this free finish: the same bytes are the diamond instant finish, and on a 3-hour cron it would complete nothing earlier, since the window is at most 3 h and finished-timers completes the research on the next run anyway. golloesSpeedTime spends a different free-time pool.
  • No isGold on the wire. The UI passes isGold to queue.ccd.m.new, but the message class never puts it on the wire (QueueCcdMNewMessage.lua:3-17).
  • goclient’s guard. duel-speedups refuses any key outside the three items-only sets above, an empty or malformed item string, and a count above the owned count from init items. It also stops for the rest of the process if a reply shows the diamond balance falling or lacks itemCostArr for the items sent.
  • The tripwire outlives the run. When duel-speedups, duel-recruit-tickets, duel-troop-training, secret-tasks-start, supplies-search or a dig game trips, the first observed diamond drop is also written to <session config>.tripwire.json (time, feature, command, reason). A duel-speedups reply that only lacks a field it checks (itemCostArr, the camp’s gold) halts that run but writes no file. While the file exists, every duel spend, the Treasure Hunt pickaxe digs, treasure-digs’ brick opens and supplies-search refuse to run, in later runs too, with a warning naming the file; every run also warns at startup, and a -collect run exits 1. Free dig claims (vault stones, hammers, chests) and the read-only -plan features still run. An unreadable file counts as a trip. After checking the account, remove the file, or run lastwar-client -clear-tripwire (with -config when the session config isn’t the default one).
Speed-up goods (goods table, static-analysis-only): type2 is the menu, para3 the seconds.

Radar tasks

radar-execute runs the client’s Quick Execute flows for the march-free task types {6, 18, 26, 44} and talks (type 14), only while the client’s Quick Execute is open. That takes three gates, each logged when closed:
  • init dataConfig turns on radar_quick_operation_switch;
  • the account is in season 2 or later, from init playerServerSeasonInfo.seasonId (IsFuncOpen, RadarFakeUIMarchManager.lua:117-123; lw_function_season row 106, FunctionSeasonUtil.lua:1-68), checked before any request;
  • the radar is at level 6 or above (detect_config.k100; DetectEventCompleteOneClickBtnView.lua:41-62), from the get.detect.info reply’s level. A missing level counts as closed.
Only types 6, 18, 26 and 44 are placed on the map; a talk starts without placing (DetectEventCompleteOneClickBtnView.lua:104-131, DetectEventItem.lua:150-159):
  • Never sent: reset.detect.event (a diamond re-roll), any battle or march type, and any client-computed result.
  • Help stamina: a Help Teammates task costs 10 stamina unless its cost is 1.
  • Day gating: the talk flow runs only on days whose entry lists type 82, because it claims as it finishes.
The client’s bank model for reference: each refresh adds N tasks into free slots and then into stock, up to detect_max_num, so a refresh with a full bank loses eventNum + N − max(show − slots, 0) − maxNum tasks (detect_level; UIDetectEventCtrl.lua:371-394). goclient claims radar tasks only on days whose entry lists type 82 (radar-claims), and radar-inventory logs the bank figures.

Open questions

  • When each duel action books its points. Start, finish, or claim, per action type: radar tasks, UR secret tasks, power gains, and training. The client’s own Claim All dialog points at the claim for radar tasks (en detect_quick_reward_confirm_text), and the push.act.score.obtain log is in place to settle each one live. Power gains, static reading: at the completion request. The duel’s go-to for building power (score 90202, gotype2 504 GotoBuildingPowerUp) points at a finished, uncollected upgrade (GoToUtil.lua:4440-4458), and the finish reply carries the new level, so finished-timers holds completions for their day. For research, which event sends push.science.change isn’t visible statically.
  • Is activity 55000 open on the rest day, and what does its info reply carry then? finished-timers holds through Sunday only if it is open and lists type-15 entries; otherwise Sunday completions finish as with no duel.
  • Are unclaimed chests mailed at the day’s end? A mail template exists; it isn’t confirmed.
  • Does a finished radar task survive its endTime? The live task list shows finished (state 1) tasks carrying an endTime like unstarted ones.
  • Is an empty or over-count itemIDs charged in diamonds? goclient never sends an over-count or an empty itemIDs, so this stays a static reading.
See also Live validation against production for the reply shapes these features have round-tripped.