Offline DAoC fork v0.276.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.276.0

Added

• Starter gear is marked in the companion gear window (TASKS 129): a
  gold * in the corner of a slot marks an item that stays with the
  companion, so you see it before a give is refused.

Changed

• The companion gear window is now part of the Companion Manager
  client (TASKS 129). build_companion_manager_client.py builds it into
  the manager's own game.dll section, without the probe's debug status
  codes. The title shows the companion's name, the backpack heading counts
  its items, and the last reply to a move stays in the window.
• [Open inventory] in the Companion Manager opens the gear window
  instead of the House Vault list. An older manager client, which cannot
  show the window, gets the House Vault list after three seconds, and at
  once on later opens.
• The command is now /companions gear [name] (/companions gear off
  closes it). /companions gearprobe still works.
• The manager client stage is companion-manager-stage-0.276.0
  (game.dll bfefe97d…). Install-CompanionManager.ps1 upgrades an
  installed 0.272.0 manager or either paperdoll probe in place. It backs up
  and restores custom6_window.xml too. The release pack ships the new
  stage and may replace the 0.272.0 and probe client files.

Removed

• The paperdoll probe tooling (probe_companion_paperdoll.py, its test
  and Install-CompanionPaperdollProbe.ps1). The manager builder and its
  emulation test now cover the window; the probe files remain in the
  v0.275.0 history.

Offline DAoC fork v0.275.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.275.0

Added

• Companion gear window with drag and drop (TASKS 129): the companion's
  19 worn slots, labelled in three columns, and its 40-slot backpack as a
  grid, with the items' real icons. Click one of your items, then a slot to
  give or equip it; click a filled slot to pick its item up, then click
  where it goes (another slot or your own bag). Open it with
  /companions gearprobe [name] [plain] (plain: without the House Vault
  list). Works in the real client. The window's client files are a
  separate install (tools/dev/Install-CompanionPaperdollProbe.ps1, stage
  built by source/server/tools/probe_companion_paperdoll.py) and are not
  in the release pack yet. What is still open is listed in section 8 of
  docs/COMPANION_PAPERDOLL_RE.md.

Changed

• The companion inventory view (the paperdoll window, the House Vault list
  of [Open inventory]) shows every backpack item, starter gear included.
  Starter gear still stays with the companion: taking it out is refused
  with a message.
• An item given to a companion, unequipped into its backpack or returned to
  you lands in the slot it was dropped on when that slot is empty, instead
  of the first free one.
• Bug 161 (0.274.0) is verified in the real client and moved to Finished.

Offline DAoC fork v0.274.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.274.0

Changed

• Unequipping a companion's item leaves the slot empty. The Companion
  Manager's [Unequip] and the paperdoll pick-up now mark the slot as your
  choice. The starter kit no longer fills it at once with a newly created
  piece, while earned gear may still go there. The reply now reads "...
  stays empty until you equip something or finds better gear".

Fixed

• Companions of another realm than yours can equip their armor again
  (bug 161). An owned companion takes its owner's realm, and so does the
  starter gear made for it. The item rule then looked up the owner realm's
  armor skill (a Midgard Shaman with an Albion owner has no Albion armor
  skill) and refused class-realm loot. Manual equips, automatic upgrades
  and merchant buys of armor failed for every such companion. The rule now
  judges armor and weapon skills by the companion's class realm and
  accepts items of either realm. Found when the manager's [Equip] refused
  a Shaman's starter Chain Helm after the paperdoll probe (TASKS 129).
• The real-client results of the 0.273.0 paperdoll probe (R1-R5 pass) and
  the server findings for the full window are recorded in section 7 of
  docs/COMPANION_PAPERDOLL_RE.md.

Offline DAoC fork v0.273.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.273.0

Added

• game.dll analysis for a companion paperdoll with drag and drop
  (docs/COMPANION_PAPERDOLL_RE.md, TASKS 129): the client's move-item
  sender, item array and icon lookup, drag record and drag-source kinds,
  and the stock quiver window as the pattern for item slots in an XML
  window.
• Companion paperdoll probe (research only, offline-tested; the owner's
  real-client check is pending). A four-slot Custom6 window (the
  companion's helm, chest and first two backpack slots) built on the
  0.272.0 Companion Manager client:
  • Click an item in your bag, then a slot: the client sends the stock
    move-item packet and the companion equips or takes the item through the
    existing inventory view and its protections. Click a filled slot to pick
    its item up and click your bag to take it back.
  • The window shows the items' real icons and a status line that reports
    what the client did, for the probe's four questions.
  • /companions gearprobe [name] [plain] opens it (plain: without the
    House Vault window), /companions gearprobe off closes it.
  • Builder source/server/tools/probe_companion_paperdoll.py, Unicorn test
    test_companion_paperdoll_probe.py, installer
    tools/dev/Install-CompanionPaperdollProbe.ps1 (dry run by default,
    backup and -RestoreBackup). The probe client files are not part of the
    release pack.

Changed

• Companion Manager protocol 3 gains operations 7-9 (paperdoll icon refresh,
  show and hide Custom6); clients without the probe ignore them.

Offline DAoC fork v0.272.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.272.0

Added

• COMPANIONS window as a group window (Custom7, task 128, offline only).
  The window can now stand in for the stock group window:
  • Member rows show what the group window shows, from the client's own
    group adapters: power and endurance percent, a health bar with the name
    over it and the health percent, class and level. The server adds each
    companion's stance (Aggressive, Defensive, Passive, Assist train, Dead,
    Away) and a gold leader mark. Rows cover every group member, players
    included, and a click on a row still targets it.
  • A click on a companion's stance cycles its saved stance (aggressive,
    defensive, passive) through the roster's tactics path; the reply names a
    group order that still overrides it.
  • A third tile row: Invite (the client's stock invite on your target),
    Kick (benches your targeted companion, dismisses a temporary helper,
    or removes a player when you lead), Leader (hands the lead to the
    targeted player), Leave (twice within 10 s; closes a companion raid
    and dismisses temporary helpers like bare /disband) and
    Grind / Stop grind (/grind). Disabled tiles explain why.
  • The window now shows while you are in any group, not only while an owned
    companion is with you; the status line reads "Group of N | no
    companions" for a plain player group.
  • Window 440×312 with five tiles per row; status and message lines widened.

Changed

• Companion Manager client files (protocol 3 unchanged): game.dll now
  registers 538 label adapters (98 for the COMPANIONS window: 14 tiles ×
  4, 8 rows × 5) and custom7_window.xml is rebuilt; custom8_window.xml
  and uimain.xml are byte-identical to 0.251.0. Controls 0xB2–0xB5 are
  the new tiles and 0xB6–0xBD the row stance clicks. Install the new stage
  with tools/dev/Install-CompanionManager.ps1: it now upgrades an
  installed 0.251.0 build in place and backs up its window files. The
  release pack defaults to companion-manager-stage-0.272.0 and may replace
  the 0.251.0 game.dll and custom7_window.xml. Until the client files
  are updated the old window keeps working with the old tiles only; a
  0.251.0 client ignores the new labels and sends no new controls.
• /companions bar help, docs/QUICK-COMMANDS.md, ALL SERVER COMMANDS.txt
  and docs/COMPANION_MANAGER_INTEGRATION.md describe the new window.
• Offline checks: UT_CompanionBar (30 tests) and UT_CompanionManager
  pass; the client emulation test passes on the 0.272.0 stage (538 adapters,
  stock GroupInvite and SelectGroupMember events, no overlapping click
  areas, server constants match); the installer's upgrade, re-apply and
  restore were exercised on a scratch copy of the installed 0.251.0 client.
  The real-client check is the owner's (task 128). The stage 6 integration
  fixture fails at HEAD for an unrelated reason (see docs/BUGS.md).

Offline DAoC fork v0.269.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.269.0

Fixed

• Gothwaite PvP mode: review fixes to the stage 6 tactics (an Opus
  review of 0.268.0, docs/GOTHWAITE_PVP_MODE.md 13.5):
  • A follower promoted to leader while its group was running (its leader
    died, or went home after the run) inherited a run with no end: it never
    scanned, never fought back and held its followers with it. A follower now
    carries its leader's own run clock, and a promoted leader's open clock
    ends at once.
  • A run or a regroup no longer carries into the walk home or the next
    outing (every return path and the castle clear it; sprint ends with it).
  • A running bot that is caught (crowd-controlled, at the end of its run,
    or hit in melee) turns and fights instead of standing as a free kill;
    GOTH_PVP_RETREAT_END reason=caught.
  • Followers no longer go home for low health or power while their
    leader's group rests; the regroup filter now reads the leader's state.
  • A follower no longer flaps between assisting and dropping a target that
    stands beyond 1,500 units of its leader; it follows instead.
  • The leader's "far" chase rule measures from where the target stood when
    the fight opened, not from the leader's spot a scan range away.
  • The add draw skips fights within 1,000 units (the group's own last kill)
    and takes the newest beyond that.
  • A formation slot the navmesh refuses is not proved again for 5 s; the
    opening scan runs the appetite test before the line-of-sight raycast.

Offline DAoC fork v0.268.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.268.0

Added

• Gothwaite PvP mode: the bots fight the way DAoC players fought (stage
  6, docs/GOTHWAITE_PVP_MODE.md section 13). The rules were read from
  player guides and forum accounts of 2002–2004 group RvR, the Thidranki
  battleground and the PvP servers (sources in the plan):
  • A tank leads. When a group walks out, its best main assist takes the
    lead (a guard tank, then any melee, an archer, a caster, a healer last),
    and a dead leader hands the group to the best-ranked living member. In
    the last live run 753 groups dissolved because their leader died first;
    many were led by a healer or caster.
  • Kill order. Inside a fight a mode bot now picks its target the way
    the world warbands do: it sticks to a target for a while, a damage dealer
    follows the leader's call after the 1–2 s /assist delay (and now and
    then ignores it), bots that can interrupt turn on an enemy caster who
    starts a cast, and healers, mezzers, wounded enemies and whoever hits our
    support weigh more. Before this the mode kept pure threat order.
  • Picking fights. A leader or solo only opens on a party its group can
    take: a solo takes a solo, a small-man avoids full groups, an eight takes
    nine and rarely dares more; the leader's aggression colours it, and the
    opening target is drawn by the kill-order weights instead of "nearest".
  • Retreats. A group breaks off a fight it is losing (its healer dead,
    half of it down, or clearly outnumbered; the leader's risk tolerance
    decides) and a solo flees when it is added on or losing. The run goes back
    toward the castle gate with sprint, nobody fights back meanwhile, and the
    group either takes a new leg or goes home.
  • Regroup after a fight. An arrived group sits down where it won, waits
    for its members and recovers to 70 % health and 50 % power (at most 45 s)
    before it moves on; low health and power no longer send a bot straight
    home from a won fight. In the last run 505 returns were low health or
    power.
  • Formation. Followers walk in their doctrine's travel shape: a column
    behind the leader with guards and melee first, healers in the middle and
    casters behind, or a loose fan for stealth groups, instead of piling onto
    the leader's spot. A slot that is off the mesh falls back to the leader.
  • Chase discipline. A follower drops a runner beyond 1,500 units of its
    leader and a leader a chase 2,500 units from where the fight began,
    unless the target is about to die.
  • Adds. A roaming leader hears a fight within 5,000 units of it from the
    last 45 s and walks to it about a third to two thirds of the time by its
    aggression. Hunters do not add.
  • Hunting stealthers. An assassin or archer alone (or in a stealth pack,
    gank squad or archer group) stays stealthed outside the castle, waits
    30–90 s at a point, opens only on a lone target, a caster or healer in a
    duo, or a wounded one, uses its stealth opener, and breaks away after
    the fight.
  • /gothpvp shows a tactics line (tanks took the lead, openings refused,
    retreats, regroups, adds, stealth openings). New logs GOTH_PVP_RETREAT,
    GOTH_PVP_RETREAT_END, GOTH_PVP_REGROUP, GOTH_PVP_ADD,
    GOTH_PVP_AMBUSH, GOTH_PVP_GROUP_LEADER reason=main_assist,
    GOTH_PVP_CHASE_LIMIT reason=overextended|far, and doctrine= on
    GOTH_PVP_DEPART.

Changed

• Three guarded hooks outside the mode folder: the brain's RvR target choice
  returns the mode's kill order for a mode bot, and the two stealth gates
  (keep stealth while idle, use a stealth opener) also accept a mode hunter.
  With the mode off every one of them answers as before (mode-off test).
• Tests: UT_GothwaitePvpTactics (pure rules, lines, counters, status) and a
  stage 6 mode-off check. Automated tests were run for the Gothwaite
  fixtures; real-client verification is left to the owner (stage 5).

Offline DAoC fork v0.267.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.267.0

Fixed

• Gothwaite PvP mode: bots no longer clump on the slope below Caer
  Gothwaite. In the second live run (300 bots, watched with a position
  sampler), fewer than one bot on average stood beyond 7,000 units of the
  castle, the harbor stayed nearly empty, and 778 of 892 kills fell in the band 5,000–6,000 units out.
  The bots stood in one line where the no-fight ring ends below the gate.
  Groups leaving the gate now walk to a patrol point picked at random over
  the island before they open any fight; they still fight back when
  attacked, as a group. A fight that ends because the target ran back toward
  the castle sends the leader to a new random point instead of the nearest
  one, which was next to the gate.
• Mode bots spread over the whole island: one spot full of recent fights now
  draws a group at most four times as often as a quiet spot (it was about a
  hundred times by the gate), and spots that other groups are already
  heading to are picked less often. Bots wait 6–15 seconds at a spot instead
  of 15–40.
• About 70% of mode bots stood queued in the castle: only 15 groups or solos
  could leave per minute. Now one leaves per second on average.
• Mode bots could still die inside the Caer Gothwaite safe area. A bolt,
  arrow or damage-over-time spell that hit outside could finish its target
  after it was back in the castle, often at its landing spot. Spell damage
  between players and bots now stops at the castle edge, also for a real
  player's spells, while the mode is on.

Offline DAoC fork v0.266.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.266.0

Fixed

• Gothwaite PvP mode: no more permanent gate camp. The first live run
  had every kill within 300 units of the Caer Gothwaite safe circle: all
  groups walked to one exit point and held there, so each new group ran into
  the last. Now mode bots open no fights within 1,500 units outside the safe
  circle (new gateRing setting; self-defence still allowed), the gate is
  only a waypoint, a group's first patrol point is drawn evenly over the
  island instead of toward recent fights, and at most one group or solo
  leaves the castle every 4 seconds.
• Mode bots no longer log in at their capital or get stuck in the castle:
  the random spread around the bindstones could land off the walkable floor.
  They now use 16 courtyard spots, each proven on the installed navmesh to
  route to the gate.

Changed

• gothwaite-pvp.json gains gateRing (default 1500). The 0.266.0 server
  and launcher read files with or without it.

Offline DAoC fork v0.265.0

Install or update

1. Need the base game first? Download and extract the original Offline DAoC v0.3 release.
2. Close the game, server and launcher. Download UPDATE-OFFLINE-DAOC.cmd and Update-OfflineDAoC.ps1 into your game folder (next to START OFFLINE DAOC.cmd) and run the .cmd.
3. It downloads the update pack, checks its SHA-256, backs up every file it replaces under update-backups, and installs it. Saves, account.txt and configs are never touched. After the first update, run UPDATE OFFLINE DAOC.cmd from the game folder to get later releases.

Coming from a v0.3 game with characters? The first launch asks for a one-time Camlann world reset (full backup first, local account kept). Old characters do not carry over.

Changes in 0.265.0

Added

• Gothwaite PvP mode, stage 4: status and load (docs/GOTHWAITE_PVP_MODE.md,
  TASKS 125). /gothpvp (GM) shows the mode bots by level band and phase,
  the castle groups by shape, mode bot kills and deaths per band, kills by
  con colour, and the mode's turn load.
• A GOTH_PVP_LOAD log line once a minute while the mode is on (bots, turn
  average, p95 and maximum, scan and group-former cost), and three new
  BOT_THINK_PROFILE phases (GothwaitePvpDriver, GothwaitePvpScan,
  GothwaitePvpFormer). The plan's section 12 describes how to measure the
  mode at 300, 600 and 1,000 bots.
• Mode bots now and then say a short line in local chat after an arena kill
  (15%, at most once per 2 minutes per bot and once per 30 seconds in the
  arena).

Changed

• Cheaper mode turns: patrol points are cached per arena edge, and a bot's
  opponent scan runs only when it is due (every 1.5 s).