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

[Feature Request] If a player cant access to a item it cant be used in craftings #146

Closed
llchris opened this issue Feb 4, 2019 · 4 comments

Comments

@llchris
Copy link

llchris commented Feb 4, 2019

Hi, I'm asking if this feature may be added. This feature is useful for stage the minecraft gameplay. If a player cant access to an item(not enough skill) it cant be used in craftings.

Thanks - Nov4e

@Lanse505
Copy link
Collaborator

Lanse505 commented Feb 4, 2019

There is no easy or even clean way to do this due to even how simple inventory or normal crafting works.
I know @pupnewfster has talked about looking into crafting stuff in the past, but in general crafting is something we don't really like to tamper with.

@pupnewfster
Copy link
Collaborator

When I was messing around with crafting things in the past, it was a pain and Lanse is right that there is no clean way to do it. And that was with seeing if it would be even feasible to have recipe locking in CompatSkills, without also requiring GameStages and RecipeStages and using CompatSkill's GameStage integration. It was not worth the effort for how many other mods handle things differently allowing for bypasses. Not to mention the added calculations for locking components of recipes, given how many recipes there may be.

One thing if ever implemented might more or less work for this would be Coders-After-Dark/CompatSkills#78

However, in 1.13 where recipes will be modifiable with data packs and iirc be sent to the client from the server it may become possible to handle recipes easier.

@llchris
Copy link
Author

llchris commented Feb 8, 2019

thanks for the help.

@Lanse505 Lanse505 pinned this issue Feb 8, 2019
@Lanse505 Lanse505 closed this as completed Feb 8, 2019
@Lanse505
Copy link
Collaborator

Lanse505 commented Feb 8, 2019

Closing this issue for now, but I've pinned it for future inquiry in 1.13 on-ward.

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

3 participants