Add TeamEspHack

[LilyKensa]

Description

Added a simple but cool feature, TeamEsp. It's basically just PlayerEsp but using the color of their name tags.

Testing

Additional Stuff

NPC Filtering

I also added a feature called FilterNpcLikeSetting because the white boxes on NPCs were annoying, as it loses the meaning of using TeamESP.

But I can't think of a good way to detect NPCs, so now it will only check the name patterns that NPCs will appear in Hypixel.

Teammates Filtering

It's weird to constantly target and attack your teammates, so I added FilterTeamates to ignore hem

[coderabbitai[bot]]

Walkthrough

Walkthrough

The recent changes introduce the TeamEspHack feature to the Wurst client, enhancing team member visualization in Minecraft games. This addition includes logic to prevent conflicts with the PlayerEspHack. Additionally, new filtering options for NPC-like entities and teammates improve entity management versatility. These updates refine user experience and provide greater customization in gameplay.

Changes

Files	Change Summary
src/.../hack/HackList.java, src/.../hacks/PlayerEspHack.java, src/.../hacks/TeamEspHack.java	Added TeamEspHack for team visualization. Updated PlayerEspHack to disable TeamEspHack when enabled, preventing conflicts.
src/.../settings/filterlists/EntityFilterList.java	Updated genericCombat method to include a new filter for NPC-like entities, enhancing entity management capabilities.
src/.../settings/filters/FilterNpcLikeSetting.java, src/.../settings/filters/FilterTeammatesSetting.java	Introduced FilterNpcLikeSetting for NPC-like entity filtering and FilterTeammatesSetting for excluding teammates based on display name colors.
src/.../hacks/AimAssistHack.java	Added new filters to AimAssistHack to exclude teammates and NPC-like entities from targeting logic, improving gameplay experience.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions[bot]]

This pull request has been open for a while with no recent activity. If you're still working on this or waiting for a review, please add a comment or commit within the next 7 days to keep it open. Otherwise, the pull request will be automatically closed to free up time for other tasks.

Pull requests should be closed if:

• They have been superseded by another pull request
• They are out of scope or don't align with the project
• They have become obsolete due to other changes
• They have bugs or conflicts that won't be resolved

[LilyKensa]

I just realized that I don't need to create a new hack, I can just add a setting to PlayerESP like "Use Team Colors"

[github-actions[bot]]

This pull request has been open for a while with no recent activity. If you're still working on this or waiting for a review, please add a comment or commit within the next 7 days to keep it open. Otherwise, the pull request will be automatically closed to free up time for other tasks.

Pull requests should be closed if:

• They have been superseded by another pull request
• They are out of scope or don't align with the project
• They have become obsolete due to other changes
• They have bugs or conflicts that won't be resolved