-
Notifications
You must be signed in to change notification settings - Fork 8
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
[WIP] trying to fix things #1
base: master
Are you sure you want to change the base?
Conversation
With your changes, I do see something at http://localhost:13333/ (ran extract_textures.js on 1.8.9, using Safari 9.0.2 on OS X 10.11.2): |
Ah yeah indeed I tried again and it displays something. Maybe there's been a new release of the dependencies, I think I'll try locking them down a bit. |
… info about where the jar might be
I'm getting a Problems:
edit: ah no nevermind, the process terminating is browserify, that's normal |
…t does that for some reason)
it seems the can't move/look around is actually normal because it's following the bot things what should be really fixed is the blockName / textureName mapping I think that mapping should probably be in a minecraft-data. There might be a direct .json source in the client jar we could use ? |
seems https://github.com/mcedit/mcedit2/tree/master/src/mceditlib/blocktypes has some stuff |
Block -> texture data is in resource packs or the client jar, path {
"parent": "block/cube",
"textures": {
"particle": "blocks/crafting_table_front",
"down": "blocks/planks_oak",
"up": "blocks/crafting_table_top",
"north": "blocks/crafting_table_front",
"east": "blocks/crafting_table_side",
"south": "blocks/crafting_table_side",
"west": "blocks/crafting_table_front"
}
} |
Can we get these changes merged? |
Some things have changed since this repo was last updated, mostly in voxeljs (and possibly mineflayer). Since dependencies are specified here with a >=, it's mostly broken.
I've tried updating things, and with these changes, I get no error in the browser and no error in the server, but instead it uses 100% of a core and displays nothing. Not sure what is wrong.