Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Added option to only show activated spawners (Spawner-Based Stash Detection) #5054

Closed
wants to merge 1 commit into from

Conversation

Lyzev
Copy link
Contributor

@Lyzev Lyzev commented Dec 20, 2024

Type of change

  • Bug fix
  • New feature

Description

This feature leverages a recently discovered exploit to enhance stash searching capabilities on anarchy servers like 2b2t. Inspired by FitMC’s video, the method addresses a common practice where players hide stashes in naturally generated chests, such as those found near spawners. These stashes typically remain undetected since they do not alter the surrounding terrain.

A week ago, a player named ETIANL revealed a technique to identify player activity near spawners by analyzing the spawner's spawn delay. If the delay has been reset or altered, it indicates that player was nearby. This discovery significantly improves stash detection by pinpointing spawners that might have been triggered by players hiding their loot.

This new setting in BlockESP implements this technique, allowing players to identify and locate activated spawners as potential stash locations.

NOTE: In theory, this method does not detect all activated spawners. A player could leave the spawner radius at the exact tick the spawn delay reaches its default value (20), making it undetectable in such cases. Additionally, spawners in the Nether can sometimes have their spawn delay set to 0 instead of 20, leading to potential false positives.

Related issues

None.

How Has This Been Tested?

Tested the new feature in the development environment to ensure that the added setting works and only activated spawners are rendered. No issues were found during testing.

Checklist:

  • My code follows the style guidelines of this project.
  • I have added comments to my code in more complex areas.
  • I have tested the code in both development and production environments.

@DrParanoya
Copy link
Contributor

Trouser Streak Skid kicks in

@Lyzev
Copy link
Contributor Author

Lyzev commented Dec 20, 2024

Trouser Streak Skid kicks in

To be honest, I don't fully understand your comment. If you're implying that implementing a published exploit is "skidding" or something similar, I don’t see the issue with adding this as a feature in Meteor Client. The player who discovered it is known for publicly sharing his ideas and findings. Moreover, I created my own implementation of this feature without copying any code - just using the knowledge I gained from the video.

@RacoonDog
Copy link
Collaborator

There’s not much point adding it to meteor client considering etianl, the person who found this trick, did so on his meteor client addon.

Perhaps if someone could improve on the method we would consider it, but as it stands you should just use the addon.

@Lyzev
Copy link
Contributor Author

Lyzev commented Dec 20, 2024

If this feature is not desired in Meteor Client, I have no issue with having my PR declined.

@Lyzev
Copy link
Contributor Author

Lyzev commented Dec 20, 2024

There’s not much point adding it to meteor client considering etianl, the person who found this trick, did so on his meteor client addon.

Perhaps if someone could improve on the method we would consider it, but as it stands you should just use the addon.

Oh, I see. I wasn’t aware that an addon for this already exists. My apologies, I thought there wasn’t any addon or feature in Meteor Client for this exploit. That’s my mistake.

@Lyzev Lyzev closed this Dec 20, 2024
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.

3 participants