Tile math
(x / 1000, y / 1000), and its index is x + y * 3000 + 1. Battlefield worlds take their size from Lua instead (static-analysis-only).
Query model
-
Viewport block pull (C#-owned):
world.get.block,world.get.new, and, on the cross-server line,world.get.cross. These never appear in the Lua command catalog; C#WorldPointManagersends them as the camera moves and handles the replies itself.world.get.blockasks for up to 160 block indices per request (static-analysis-only):leftBottomandrightTopare tile indices computed on a 3000-wide grid.world.get.newis the view-level variant,{x, y, serverId, type, viewLvl, timeStamp, worldId}. Replies carry per-server sub-replies (serverPointArr[]) or flatserverId/worldId, with protobuf byte arrays:points[]asWorldPointInfo,lands[]asLandPointInfo,deserts[]asDesertInfo,alInfos[], plus overlays such ashotSpots,triggers, andgreenPoints. After the first request withclearUuidSet=1, the client drops every previously known point the server didn’t return.push.world.get.blocktells the client to re-request its view. -
Single-point pull:
world.get.detail.new {point, serverId, worldId, previewAssistance, pointType, uid}. The field ispoint, notpointId. -
Server-side “find nearest”:
find.resource,find.enemy.point: the client sends criteria only (level, type), no coordinates at all; the server searches from the player’s context and returns a single point id.find.monsteris the same family but (unusually) also sends apointIdalongside its criteria. -
Bulk per-server/per-alliance push:
world.get.alliance.city.info,lw.req.world.occupy.info: the entire dataset for a server, no pagination. Pushes are invalidate-then-refetch, not deltas. - Batch pull by uuid list: radar/detect-event lookups, pipe-delimited uuid lists.
world.get.march.infos {x, y, needCross} finds marches passing near a raw tile coordinate. March state then streams as C#-handled pushes: push.world.march.new carries a protobuf WorldMarch (or a WorldMarchDeltaMeta delta), and push.world.march.del carries the march uuid and isBattleFail. In all, 29 world, scene, and season push.* messages are handled only in C#.
Railway trucks and alliance trains
Trucks and trains are marches, but their cargo and raid state come from the railway module (1.0.370 Lua, unchanged in this part since 1.0.364; static-analysis-only).- The list:
train.list {isRefresh: Bool}returns other players’ trucks inls[], alliance trains inallianceTrainList[], and the servers you’re matched against intrainServers, a comma-separated string. The client sendsisRefresh: truefrom the list’s Refresh button, and on its first call of the server day. - Entry type: each entry’s
typeis1(truck) or2(alliance train), andcfgIdis atrain_propertyrow. For trucks, quality 1-5 is N to UR, and quality 10 is the Reindeer Sleigh. The wire carries onlycfgId, not the quality. - Truck cargo:
baseGoodsandextraGoods, each{full, cur}.fullis what the truck set out with andcurwhat’s left. Goods entries are{type, value}with aRewardType: 1 iron, 20 food, 31 coins, 7 an item{id, num}. - Reroll:
train.change {uuid: Long}replaces a parked truck at random; the reply’smyTrainis the new truck. Its cost in item 1520001 (train_para12) istrain_para9 (“0,1”) at indexchangeCountByGold + 1, the last entry past the end, and 1 withoutchangeCountByGold, so only a truck’s first reroll is free. The game asks first for the sleigh and for a truck holding thetrain_para55 goods (2 of item 2270000 or 500105), and asks before a truck below SSR leaves with its free reroll unused.train.batch.changeis the paid batch path (tickets or diamonds). The opt-intruck-rerolluses only the free one, on N, R and SR trucks, and runs beforetruck-deploy. - Train cargo: per carriage, in
marchInfo.carriageList[].trainGoods. - Past raids:
marchInfo.plunderRecord[]. - Raid count and caps: the count is
marchInfo.robTimes. A truck takes at mosttrain_pararow 21 raids (2), the sleigh 1, and an alliance trainalliance_train.k10(3), less one with a VIP aboard. completeness: shown as “Integrity: %”.- Defensive power:
marchInfo.power, or the sum ofmarchInfo.heroInfo[].powerfor a truck. For a train it’s the sum ofmarchInfo.formation.armyUnit1-3.power. - One entry:
train.refresh {uuid, serverId}re-reads it. The reply is the wholetrain, or only{uuid, lastUpdateTime}. The client sends it at most every 600 s for others’ trucks (train_para39) and every 60 s for its own (row 51). - On the world map: a truck march’s
WorldMarchcarries the sametrainobject, which the C# hands to the same store (CSharpCallLuaInterface.AddOrUpdateTrain). - Your own count: your raids today are
trainData.dailyRobCount(in init and intrain.data), capped bytrain_pararow 11 (4) and shared by trucks and trains.
railway-plunder feature drops every truck and train on the account’s own server before anything else: user.serverId, and user.crossFightSrcServerId during a cross-server fight. The client doesn’t enforce this. CheckTrainInMatchServer only checks the server-sent trainServers, and your own server can be in that list.