I never really used /recipe, but I think this would be a great thing to happen as I will probably use it more now, knowing it's always in my inventory.

So a +1 from me!

 

+1

ALTHOUGH
I doubt most people got that feature for recipe, i wouldnt mind this addition of all recipe's being unlocked in the recipe book be added to Patron Rank.
As Patron Rank is a bit of a umbrella feature which does lots of stuff, another little perk to be added would be a nice touch and maybe another reason for people to donate for a bunch of goodies that arent really worth a full feature.

 

Here comes 314 tearing our statements into shreads ;~;

 

I think you looked too far into it Pi. I think what this is suggesting is to do away with /recipe, but people who bought the feature that had access to /recipe, shouldn't have to craft stuff before it shows up in the recipe book.

Btw +1 if that is what this is suggestion as that's how I took it.

 

Just give us a limited portion of the new recipe - ie allow us to edit our own recipe books by command. Seems like the best way to handle it honestly although I imagine a plugin to do it wouldn't be all that hard.

 

+1 So that the beginners of playing Minecraft will find it easy how to craft with these commands.

 

From my point of view...
Right now people who once had access to /recipe can't use it. I'm not sure what happened, but it seems to be broken or something conflicting with it. Currently I have to google how to make things and it takes FOREVER for web pages to load while I'm on MC. It's a huge inconvenience for me, so when I seen this suggestion I thought that it was a great idea since MC's latest updated added the recipe book... this is the perfect time to build off of that. I mean it's broken now, I assume it would take some work to fix it, I think that time would be better invested in using MC's new features. This is just my opinion tho.

 

He wasn't suggesting or arguing that /recipe should be removed: /recipe has been removed already (and must stay so, I'm afraid). He started from this matter-of-fact premise and then argued that those who used to have /recipe should now have a recipe book already populated with all recipes (instead of having to manually craft everything at least once in order to populate it manually).

Which makes total sense, under this light, so +100.

About texture packs: do I understand correctly that you are running a 1.12 client with 1.11 texture packs? May I ask... why?

 

Oh, I see.
Could you set it to just use the default 1.12 textures whenever a fancy texture is not found? Or it's more time consuming than it sounds?

 

/recipe is disabled due to a duplication exploit, and won't be added back.

 

You could just scrap essentials old recipe functionality. The vanilla command would be cool, although probably would want to put some limits on it through ess.

 

Because of this, the suggestion was changed: [EDIT: nope]

I think this can be implemented quite easily with the command(*) /recipe give <player> *

• automatically, once and for all, whenever a player purchases the feature;
• manually (I guess?), once and for all, for all the players who already purchased the feature before this suggestion was implemented.

(*) I mean the vanilla command: http://minecraft.gamepedia.com/17w13a

 

torn into 314 pieces in 3.14 seconds