Added Several Hunts in Shard

[MrQuosig]

Added two levels of Peccary and two levels of Clouded Arzumos.

Summary by CodeRabbit

• New Features
  • Added four new hunting areas to Ilithi: Peccary Shard, Peccary Shard Plus, Clouded Arzumos Shard, and Clouded Arzumos Shard Plus. The Plus variants offer higher appraisal values.

[coderabbitai]

Warning

Rate limit exceeded

@MrQuosig has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 56 minutes and 6 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: d038efb9-430f-4306-b93b-1b9f1e859876

📥 Commits

Reviewing files that changed from the base of the PR and between 05a3310 and 10388cc.

📒 Files selected for processing (1)

• data/base-hunting.yaml

📝 Walkthrough

Walkthrough

Four new Ilithi hunting zones are added to the base hunting configuration: peccary_shard and peccary_shard_plus with their room mappings, followed by shard_clouded_arzumos and shard_clouded_arzumos_plus with corresponding room IDs. The plus variants include notes on relative appraisal values.

Changes

Ilithi Hunting Zones

Layer / File(s)	Summary
Hunting Zone Definitions data/base-hunting.yaml	Four new hunting zones are added under Ilithi: peccary_shard and peccary_shard_plus (lines 1632–1654) map to specific rooms with shard context, and shard_clouded_arzumos and shard_clouded_arzumos_plus (lines 1682–1702) map to rooms; the plus variant notes a higher appraisal value.

🎯 2 (Simple) | ⏱️ ~5 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 'Added Several Hunts in Shard' directly and clearly reflects the main change: adding new hunting areas (Peccary and Clouded Arzumos variants) to the shard hunting zone configuration.
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

Tip

💬 Introducing Slack Agent: The best way for teams to turn conversations into code.

Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.

• Generate code and open pull requests
• Plan features and break down work
• Investigate incidents and troubleshoot customer tickets together
• Automate recurring tasks and respond to alerts with triggers
• Summarize progress and report instantly

Built for teams:

• Shared memory across your entire org—no repeating context
• Per-thread sandboxes to safely plan and execute work
• Governance built-in—scoped access, auditability, and budget controls

One agent for your entire SDLC. Right inside Slack.

👉 Get started

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In `@data/base-hunting.yaml`:
- Around line 1682-1702: The shard_clouded_arzumos and
shard_clouded_arzumos_plus blocks are out of sort order relative to the file's
rank-based grouping; move the entire block for shard_clouded_arzumos and
shard_clouded_arzumos_plus so it appears before the shard_gryphons* (250+ rank)
entries, preserving their internal list items exactly as shown (IDs 6285–6303)
to maintain rank ordering and readability.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 700cc65d-0caf-4eb0-86b5-0aa16b91b75a

📥 Commits

Reviewing files that changed from the base of the PR and between 39f3b45 and 05a3310.

📒 Files selected for processing (1)

• data/base-hunting.yaml

[coderabbitai]

⚠️ Potential issue | 🟡 Minor | ⚡ Quick win

Reorder shard_clouded_arzumos* to keep rank ordering consistent.

Per the file’s ordering convention, the 230-340 block should appear before the shard_gryphons* (250+) entries. Please move this block earlier to preserve sorted readability and maintenance consistency (Line 1682 onward).

🤖 Prompt for AI Agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In `@data/base-hunting.yaml` around lines 1682 - 1702, The shard_clouded_arzumos
and shard_clouded_arzumos_plus blocks are out of sort order relative to the
file's rank-based grouping; move the entire block for shard_clouded_arzumos and
shard_clouded_arzumos_plus so it appears before the shard_gryphons* (250+ rank)
entries, preserving their internal list items exactly as shown (IDs 6285–6303)
to maintain rank ordering and readability.