-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Add Crafting command #3960
Draft
rycbar0
wants to merge
44
commits into
cabaletta:master
Choose a base branch
from
rycbar0:crafting
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Add Crafting command #3960
Changes from 1 commit
Commits
Show all changes
44 commits
Select commit
Hold shift + click to select a range
e14afe5
Create CraftCommand.java
strubium aa18fdf
Update CraftCommand.java
strubium 5c0fe9c
Update Settings.java
strubium 15efa2b
More info in description
strubium 4c5a5da
Update DefaultCommands.java
strubium 31976c1
Add chat notifier
strubium 6e71d89
Merge pull request #5 from strubium/master
rycbar0 1547431
prototype
rycbar0 a443dcc
not sure if this goes in the right direction
rycbar0 e7a36ec
resolving some mixin problems
rycbar0 98c1d64
revert some changes as they didnt worked out.
rycbar0 645dbc4
Update CraftingProcess.java
strubium 5c61f53
Merge pull request #6 from strubium/patch-1
rycbar0 b009df2
craft-ability check
rycbar0 13c31c1
refactoring
rycbar0 c34eb89
small fix
rycbar0 49a33d0
remove autocraft setting because unused
rycbar0 79e417e
refactoring CraftingProcess
rycbar0 8d1b2c7
delete mixins because unused
rycbar0 1cb53c7
delete mixins because unused
rycbar0 c1f2d0c
revert changes on GetToBlockProcess
rycbar0 6d34c50
im hard at my limit here
rycbar0 f5c50df
i need help
rycbar0 f79077f
its amazing that it works sometimes
rycbar0 eae2dc3
delete extra line
rycbar0 ecfbc49
craft command
rycbar0 48dc674
getting closer to a finished product
rycbar0 0a85399
todos
rycbar0 4e71b04
codacy and selecting crafting table
rycbar0 d8c8884
comments and edge cases
rycbar0 857acd4
copying a good part of builder process
rycbar0 4285f53
small tweaks
rycbar0 8c40be4
i think its ready
rycbar0 49e7892
Merge branch 'cabaletta:master' into crafting
rycbar0 7eed809
Merge remote-tracking branch 'origin/crafting' into crafting
rycbar0 32bd0b4
changes on CraftCommand
rycbar0 15a4cc3
changes on CraftingProcess
rycbar0 df3f7a3
changes on CraftingProcess II
rycbar0 29d1df4
add recipe switching for item crafting
rycbar0 1ef0feb
ready for round two
rycbar0 913ae06
Merge remote-tracking branch 'upstream/master' into crafting
rycbar0 fbd1e0c
oopsie
rycbar0 6ddfdd5
change CraftCommand
rycbar0 927fa43
CraftingProcess uses now List<IRecipe>
rycbar0 File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
comments and edge cases
- Loading branch information
commit d8c8884bd1f86ab4c40a401fd5a9b459b6e764ab
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why not reverse the order to be
[quantity] <item>
like for#mine
? That way you can try getting an integer (is there something calledargs.getAsOrDefault
?) and then an item and if the item fails you can doargs.rawRest
instead of replacing underscores with spaces.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think it would be better to first get the item by id or name and then do the same for both. You should at least move the item-by-name thingy into a helper method which returns just an item (no logging etc.).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i understand the logic behind the first comment but not the second.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Basically I mean you should first get the item by either method (id or name) and then continue along the same code path for both cases.
Currently this is
and I think it should be
Why should there be a difference between
#craft wooden_sword
and#craft wooden sword
?Not sure how easy that is though, due to the way you use items in the id case and recipes in the name case.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
it maybe doesnt make that much sense with a wooden sword as there only exist 1 wooden sword.
take the example of a red bed
if you type:
#craft bed
it will craft any bed this can be a white bed, a blue bed or a red bed.if you type
#craft red bed
it wont find a item that is named like that so it searches a recipe that produces a item stack with that display name. note here that there are 2 recipes for red beds, one with red wool and one dying a white bed.i use crafItem() if i want any instance of that item crafted and i use craftRecipe() if i want baritone to use that specific recipe to craft
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can't you get all recipes that produce the desired item (be it by name or id) and then use that collection of recipes from that point on? That way there is only one case (n recipes) instead of two. In general even if the user specified one exact item there can still be multiple recipes for it and the current recipe switching mechanism is sketchy (doesn't it even bypass what you said about
#craft red bed
becauseredBedRecipe.getRecipeOutput().getItem() == Items.BED
and getting a recipe for that doesn't need to returnredBedRecipe
again?).