-
Notifications
You must be signed in to change notification settings - Fork 105
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
How to develop it? #279
Comments
I abandoned the project when Mojang didn't move blockstate information into the world file (if it happened since I am unaware of it). Making progress without more data in an accessible format means writing scripts that turn Java bytecode into data and I don't have the time for it, nor do I think there is much value in it. |
Yikes, that wouldn't be a fun thing to convert, though it does sound like an intresting side project... |
@eddyb the block data has now been moved into the world file, as well as making the available blocks available. Other stuff in the |
I heard! I don't have the time to get involved for now, but I might later this year. |
Cool! |
As a further note: @FVbico has created https://github.com/FVbico/MinecraftData, which contains loads of information about every single block in the game. I'm sure that he wouldn't mind a practical use of this venture. |
@Levertion Unfortunately, that link appears to be broken. Is there a working link that you could direct to, if at all? Cheers. |
@shymega EDIT: it's permanently deleted now, all files are gone, never to return; it has been for a few years |
newer versions of Minecraft 1.13+ block states can be extracted using the data generator.. |
I am familiar with game engines in C++, however, I ahve not released any game yet. I would like to develop
hematite
if it is possible, however, I don't know anything about the game, the world file structure. If you publish some documentation for developers about how everything works here in thehematite
, it would be very nice, everyone would be able to continue working on it.The text was updated successfully, but these errors were encountered: