-
-
Notifications
You must be signed in to change notification settings - Fork 225
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 recipe format #3
Comments
Any ideas how to do this? |
I think trying to apply the new format to several recipes in recipes.json might give a good idea if the format is good. For example :
|
Hm, I tried to do that with the example at the bottom. Also writing the spock implementation now, nearly done. |
Oh yeah right. Looks good. { // Polished Granite
"result": {"id": 1, "meta": 2, "amount": 4},
"inShape": [
[[1,1], [1,1]],
[[1,1], [1,1]]
]
}, better or : { // Polished Granite
"result": {"id": 1, "meta": 2, "amount": 4},
"inShape": [
[{"id":1, "meta":1}, {"id":1, "meta":1}],
[{"id":1, "meta":1}, {"id":1, "meta":1}],
]
}, the array is a bit confusing I think (since we also have array of ids in that file) |
I prefer the first one, personally. |
First one is shorter and more human-friendly, although support for both is trivial. |
Ok let's keep the first one then. |
what about repairing a tools? |
Not sure if that should be included, as an entry per tool and damage value would be the only way with the current format. |
Yeah I don't think this is a recipe. It's not crafting either. The "recipe" is even simple to figure out ("Two items of the same type and material can be placed anywhere on the crafting grid, and the result is a single repaired item"). Maybe the data in the tables in that Repair page would be useful for the implementation but that would be in a different .json. |
Python utils for Spock: Done! |
I'm thinking about building a converter from old to new format, just for testing, as long as the wiki scripts are not ready. |
Converter done! See #4 |
Ok, I've done a schema for the old recipes format, I'm going to do one for the new schema too I think. |
The schema for the new recipe format is done, see http://prismarinejs.github.io/minecraft-data/ |
I added a link to the README to the wiki page of the new recipe format. I wonder if that page should stay in the wiki or be added as a .md file in the doc/ folder ? |
For documents that won't change often, |
👍 for doc/*.md. Wiki is cool for quick collaboration, but it quickly becomes hard to navigate; |
Ok I'll put it there, once I checked everything is ok with the format by doing the last two points (implementing in mineflayer and updating my wiki extractors scripts) |
Implemented in mineflayer. Now the only thing remaining here is updating the wiki scripts. |
Ok, problem : I think we're going to need to scrape the wiki in the end |
Is it really called Smooth Granite and not Polished? |
Yeah I think it's Polished Granite, my confusion came from there https://github.com/PrismarineJS/minecraft-data/wiki/Proposed-new-recipe-format#metadata-in-the-shapes |
We are using the new recipe format now, and the remaining problems are all covered with issues. So this can actually be closed. |
Yeah you're right. |
change structure of the protocol : types and states
This may not be strictly necessary, in either case Forge server with -Dfml.debugNetworkHandshake=true logs: [14:26:03] [Netty Server IO PrismarineJS#3/INFO] [FML]: Client protocol version 2
Some cases are not handled by the recipes format, in particular a lot of thing related to metadata.
See https://github.com/PrismarineJS/minecraft-data/wiki/Recipe-format vs https://github.com/PrismarineJS/minecraft-data/wiki/Proposed-new-recipe-format
What should be done :
Might also be related to PrismarineJS/mineflayer#222
It might also be a good idea to define a jsonformat for this ( see #2 ) if it's not too complicated.
The text was updated successfully, but these errors were encountered: