Skip to content

Release v1.7.1 - #59

Merged
moust4ki merged 2 commits into
mainfrom
claude/release-v1.7.1
Oct 15, 2026
Merged

moust4ki merged 2 commits into
mainfrom
claude/release-v1.7.1

Conversation

@moust4ki

Copy link
Copy Markdown
Owner

Release v1.7.1:

  • Objectives matched by name, else by rank among their kind (Data:MatchObjectives): Forever's monsters often have no name in DingDB in the client's language, and the arrow kept leading to monsters already killed (Thendal Grove, French client); the nameplate marks and counters come back the same way.
  • Quest rewards: never a piece the class cannot wear (a druid's reward was taken in mail); only Gear:CanWear items are upgrades, the price goes to what the class can use first; the chat says which reward was taken and why.

Checks: tools/check_all.sh ALL GREEN (82 test files, 12 smoke runs), release_test green, DingDB unchanged. Installed in game.

🤖 Generated with Claude Code

moust4ki and others added 2 commits October 15, 2026 15:31
Forever's monsters often have no name in DingDB but their English one,
while the quest log is in the client's language: in a French client the
arrow kept a farming loop on Al'Aketh Neophytes already killed (4/4)
instead of leading to Malduko Cloudcrush. Data:MatchObjectives maps each
target to its live objective by name, else by rank among the objectives
of its kind left over; the engine's pending targets, ObjectiveDone, the
objectives along the way and the nameplate marks, and the panel's rows
use it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A druid's reward was taken in mail: the quest window's usable flag was
the only check. Only what Gear:CanWear accepts (the class's armor and
weapons at its level) is an upgrade now; without one, the most expensive
of what the class can use, a piece it cannot wear only when nothing else
is. The chat says which reward Ding took and why.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@moust4ki
moust4ki merged commit cd7a52c into main Oct 15, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant