Alliance Duel

​

Finding today’s entry

​

The init activity entry

activity["55000"] = {
  id:           55000,           // the activity table row (type 14)
  activityid:   "70000",         // the heroactivity row: the id the detail read must send
  name:         "370026",        // locale key of today's theme name
  startTime, endTime:  <ms>,     // today's server-day window
  readyTime:    <ms>,
  matchGroupId: <int>,
  uuid:         <32 hex chars>   // equals today's eventList actId
}

​

The detail read must send activityid

hero.event.info.get {activityId: "70000"}     // not "55000"

​

The reply

​

The week

​

The scoring list

go generate ./internal/game    # with LASTWAR_TABLES and LASTWAR_TABLE_VERSION set

​

The score push

​

Chest claims

accept.personal.reward {actId: UtfString, stage: Int (the target value), eventType: 15}

​

How goclient uses it

• duelPolicy in the session config overrides a feature’s default: {"duelPolicy": {"radar-claims": "always"}}. Valid values are hold and always.
• -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.

​

Speed-ups

build.ccd.m.new     {bUUID: Long, isFixRuins: false, itemIDs: "tmpl;n|tmpl;n"}   // construction
queue.ccd.m.new     {qUUID: Long, itemIDs: "tmpl;n|..."}                          // research, hospital
building.camp.accel {uuid: Long, itemId: "tmpl;n|..."}                            // camp training

• 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 (ArmyManager.lua:199-203). 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.

​

Radar tasks

detect.event.batch.put.point.in.world {uuidList: "uuid|uuid"}       // state 3 → 0
start.pick.garbage {uuid} … ≥ 3 s … finish.sampling {uuid}          // types 6, 26; 44 adds finish.visitor
detect.event.help.start {uuid, eventType: 18} … detect.event.help.end {uuid, eventType: 18}
start.detect.event.talk {uuid} … end.detect.event.talk {uuid}       // type 14: finishes and claims at once

• 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.

​

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.
• 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 either, so this stays a static reading.