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

Explore replacement of pymclevel with local equivalent #29

Open
mathuin opened this issue Apr 21, 2013 · 0 comments
Open

Explore replacement of pymclevel with local equivalent #29

mathuin opened this issue Apr 21, 2013 · 0 comments

Comments

@mathuin
Copy link
Owner

mathuin commented Apr 21, 2013

I use very few of the pymclevel features.

Some constants I take from pymclevel:

  • max level height
  • chunk width
  • names and values for blocks

The methods I use:

  • retrieve bounds of world (buildmaps)
  • create worlds (buildregion, tiles)
  • copy blocks and data from one world to another (buildregion)
  • save worlds (buildregion)
  • create chunks in region (tiles)
  • set block and data at location (tile, ore, tree)
  • get block and data at location (ore)

Right now, each tile is a Minecraft world. It may be worth changing tiles to work as arrays first to see if this saves time.

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

No branches or pull requests

1 participant