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

New Feature Proposal - Automatic Torch Placement #897

Closed
MineYuanlu opened this issue Nov 4, 2023 · 3 comments
Closed

New Feature Proposal - Automatic Torch Placement #897

MineYuanlu opened this issue Nov 4, 2023 · 3 comments

Comments

@MineYuanlu
Copy link
Contributor

I have developed a new feature and I'm not sure if it would be helpful: Automatic Torch Placement.

The primary motivation behind creating this feature is to automate torch placement in mob spawning areas, which is particularly useful for survival mode.

Currently, I have created a demo that includes two settings: Placement Range and Detection Range. My program will automatically choose an appropriate location to place a torch based on these two ranges.

As this is a demo, I have only implemented torch placement for now, but in reality, it can work with any light source.

Here's how my program works:

  1. It identifies all blocks within the detection range that may potentially spawn mobs (block light< 1).
  2. Among these blocks, it finds a location that can illuminate the most number of blocks.
  3. If the location is within the placement radius, it places a torch. Otherwise, it provides a notification.

图片
图片
图片
图片

@dingzhen-vape
Copy link

useful

@MineYuanlu
Copy link
Contributor Author

useful

#911

@Alexander01998 Alexander01998 linked a pull request Dec 11, 2023 that will close this issue
Copy link

github-actions bot commented Feb 9, 2024

This issue has been open for a while with no recent activity. If this issue is still important to you, please add a comment within the next 7 days to keep it open. Otherwise, the issue will be automatically closed to free up time for other tasks.

Issues should be closed if:

  • They are duplicates of other issues
  • There is not enough demand
  • They are no longer relevant
  • There are not enough details

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Feb 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants