Skip to content

Implement Pet Trust system in zander-addon#40

Open
benrobson wants to merge 1 commit intofeat/chat-formatting-11608040139254196549from
feat/pet-trust-system-10580535952557726815
Open

Implement Pet Trust system in zander-addon#40
benrobson wants to merge 1 commit intofeat/chat-formatting-11608040139254196549from
feat/pet-trust-system-10580535952557726815

Conversation

@benrobson
Copy link
Copy Markdown
Member

Implemented a comprehensive per-pet trust system in the zander-addon module.

Key features:

  • Hierarchical Trust Levels: ACCESS (mounting/riding) and MANAGE (leashing, renaming, inventory access, damage bypass).
  • Flexible Trust Management: Supports specific player trust entries and a public toggle for shared pets like carousel horses.
  • YML Persistence: Data is stored per-pet UUID in pettrust.yml.
  • User-Friendly Commands: /pettrust command suite for easy management of the pet currently being ridden or looked at.
  • Robust Enforcement: Event listeners prevent unauthorized interactions and damage.
  • Seamless Integration: Fully integrated into the existing zander-addon module while preserving its original functionality.

PR created automatically by Jules for task 10580535952557726815 started by @benrobson

- Added PetTrust, PlayerTrust models and TrustLevel enum.
- Implemented PetTrustRepository for YML storage and PetTrustService for logic.
- Added PetTargetResolver for entity identification.
- Implemented PetTrustInteractListener and PetTrustDamageListener for enforcement.
- Created PetTrustCommand with subcommands: trust, untrust, public, private, list, help.
- Integrated with ZanderAddonMain and updated configurations.
- Ensured ACCESS level allows riding while MANAGE is required for administrative actions.
- Supported untrusting offline players.
- Preserved existing module features.

Co-authored-by: benrobson <[email protected]>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@benrobson benrobson requested a review from JaedanC as a code owner April 12, 2026 00:14
@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented Apr 12, 2026

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 4da870ee-3448-4765-9d1e-aad762c7b5c5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch feat/pet-trust-system-10580535952557726815

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.

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