Skip to content

fix(ebounty.lic): v1.10.1 foraging fixes#2337

Merged
mrhoribu merged 1 commit into
masterfrom
fix/ebounty-v1.10.1
May 25, 2026
Merged

fix(ebounty.lic): v1.10.1 foraging fixes#2337
mrhoribu merged 1 commit into
masterfrom
fix/ebounty-v1.10.1

Conversation

@mrhoribu
Copy link
Copy Markdown
Contributor

@mrhoribu mrhoribu commented May 25, 2026

Updated version to 1.10.1 and added new fixes for foraging.

Summary by CodeRabbit

  • Bug Fixes
    • Updated foraging result parsing to recognize additional failure messages and improved handling for no-result scenarios
    • Modified distance filtering logic so nearest location searches are no longer constrained by distance thresholds
    • Enhanced debug logging to provide more detailed information for foraging operations

Version 1.10.1

Review Change Stack

Updated version to 1.10.1 and added new fixes for foraging.
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented May 25, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: b63ea9d9-4d1f-4440-b60a-27d50694395f

📥 Commits

Reviewing files that changed from the base of the PR and between ce2925a and 2881922.

📒 Files selected for processing (1)
  • scripts/ebounty.lic

📝 Walkthrough

Walkthrough

Updated scripts/ebounty.lic to v1.10.1 with forage-related fixes: expanded the @forage_result regex to recognize additional failure messages including a variant with optional "briefly wonder if it could even thrive" suffix, updated forage_bounty to handle the new message variant, added herb/location debug logging in forage_find, and modified distance filtering to skip the <= 90 constraint when location is "nearest".

Changes

Forage System Improvements

Layer / File(s) Summary
Version update and forage result pattern parsing
scripts/ebounty.lic
Changelog bumped to v1.10.1 with forage fixes. @forage_result regex expanded to recognize additional foraging-failure message patterns, including a longer variant with optional "briefly wonder if it could even thrive" suffix.
forage_bounty no-result handling
scripts/ebounty.lic
forage_bounty "no result / no hint-evidence" conditional updated to match the new extended failure variant, routing it to the existing "nothing found" path.
forage_find logging and distance filtering
scripts/ebounty.lic
Debug logging in Task.forage_find expanded to include herb and location arguments. Distance filtering condition changed to apply <= 90 constraint only when location is not "nearest", allowing nearest-location searches to bypass distance filtering.

🎯 2 (Simple) | ⏱️ ~8 minutes

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately summarizes the main change: a version bump to 1.10.1 with foraging-related bug fixes in the ebounty.lic script.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/ebounty-v1.10.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@mrhoribu mrhoribu merged commit 350e98d into master May 25, 2026
4 checks passed
@mrhoribu mrhoribu deleted the fix/ebounty-v1.10.1 branch May 25, 2026 14:33
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