EngineHub / EngineHub/CraftBook
More Advanced Crafting Issues... 2-3 issues.
- Dominant language
- Java
- Stars
- 320
- Forks
- 166
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 2
Description
CRAFTBOOK-2999 - Reported by Kainzo
Greetings!
This is a bit in-depth, apologies but is very needed :D
I am attempting to make an advancement system where you can use previous gathered items and then combine them to make the "next tier"
In this pastie below, I am combining 3 of RelicPaladinI, 3 of PaladinRelic2, and 3 of PaladinRelic3 - to make PaladinRelic4. However, this is not functioning. I can combine all 1-5 to make the "CodexPaladin" item just fine so multiple items with custom names and lores WORK. However, it doesn't work if there are multiple of the same involved, I believe. I could deal with that, because its kind of confusing and I really just want to add in
http://pastie.org/private/lawdlb0mznq7igjrreankg
Using the RelicNecro crafting - it seems to have odd issues. It can't combine RelicNecro4 x 9 into RelicNecro5 x 1... and the other ones also have issues.
http://pastie.org/private/h69shl5p2vdevasmbdpkjw - the config.
On this config, RelicNecro1 x 3 - does not make RelicNecro2 x 1. However, RelicNecro2 x 3 - makes RelicNecro3 x 1 without an issue.
In summation it seems that if a particular "item-type" is used for a crafting recipes - another item type with different lore/names can't be used to produce its own advancement to its next tier.
RelicNecro1 requires PAPER - however, RelicPaladin1 also requires PAPER and is the only one that works from my entire list (probably because its listed first in the config, to create the next tier on its path)
Also, it seems that it isnt possible to override vanilla recipes using this. I have 9 uniquely named Iron_ingots and it will always craft a block of iron - I figured there was a bug report on this already, just wanted to report it again.
Possible solutions? Make an /assemble - command to bypass some of the workbench issues.
Unsure, it may be bukkit issues but im not certain.
Contributor guide
Assessment
This issue has not been assessed yet.