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

world.get_block_at((x, y, z)) always returns None #19

Closed
fqhd opened this issue Sep 23, 2024 · 1 comment
Closed

world.get_block_at((x, y, z)) always returns None #19

fqhd opened this issue Sep 23, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@fqhd
Copy link

fqhd commented Sep 23, 2024

I'm using minecraft version 1.21.1 on manjaro linux. Here is the code I am testing with:

    world = mc.load(world_path)
    block = world.get_block_at((0, 0, 0))
    print(block) # This always prints None

After placing a block at 0, 0, 0 and saving the world, the library fails to identify the correct block at that location.

@MestreLion MestreLion added the duplicate This issue or pull request already exists label Sep 29, 2024
@MestreLion
Copy link
Owner

Yes, this is known and already reported in #10

It is supposedly fixed by #17 , but I don't have the time to test that PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants