Recipes are not staged reliably
justinrusso opened this issue · 5 comments
Recipes are not being staged reliably in v1.0.5.
Reverting back to 1.0.2a fixes the issue, but breaks the recipe. (1.0.2a just shows a feather for an arrow)
Script:
mods.ItemStages.addItemStage("two", <minecraft:arrow>);
mods.recipestages.Recipes.setRecipeStage("two", <minecraft:arrow>);
Crafttweaker.log:
1.0.2a:
[INITIALIZATION][CLIENT][INFO] CraftTweaker: Building registry
[INITIALIZATION][CLIENT][INFO] CraftTweaker: Successfully built item registry
[INITIALIZATION][CLIENT][INFO] Loading scripts
[INITIALIZATION][CLIENT][INFO] [crafttweaker | SIDE_CLIENT]: Loading Script: {[0:crafttweaker]: test.zs}
[INITIALIZATION][CLIENT][INFO] Added 1 entries to stage two - [ Arrow ]
[POSTINITIALIZATION][CLIENT][INFO] Setting the stage for recipes that output: Arrow
[SERVER_STARTED][CLIENT][INFO] Fixed the RecipeBook
1.0.5:
[INITIALIZATION][CLIENT][INFO] CraftTweaker: Building registry
[INITIALIZATION][CLIENT][INFO] CraftTweaker: Successfully built item registry
[INITIALIZATION][CLIENT][INFO] Loading scripts
[INITIALIZATION][CLIENT][INFO] [crafttweaker | SIDE_CLIENT]: Loading Script: {[0:crafttweaker]: test.zs}
[INITIALIZATION][CLIENT][INFO] Added 1 entries to stage two - [ Arrow ]
[POSTINITIALIZATION][CLIENT][INFO] Setting the stages for recipes based on their output stack.
[SERVER_STARTED][CLIENT][INFO] Fixed the RecipeBook
CraftTweaker: Latest build (from Kindlich) fixes global maps
RecipeStages: v1.0.5
Forge: 14.23.0.2512
#4
I believe the Dev fixed this issue as it may be the same as me.
These are not related at all, in fact, the person reporting this issue is
using a dev version, that already has your fix.
…On Dec 1, 2017 20:46, "Justin Russo" ***@***.***> wrote:
I don't think these issues are related
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AFS9xYjTN0UTE6qUopF0j6TB5LWbwlbOks5s8EmdgaJpZM4Qxwg0>
.
My mistake. I apologize.
…On Dec 1, 2017 1:49 PM, "Jared" ***@***.***> wrote:
These are not related at all, in fact, the person reporting this issue is
using a dev version, that already has your fix.
On Dec 1, 2017 20:46, "Justin Russo" ***@***.***> wrote:
> I don't think these issues are related
>
> —
> You are receiving this because you are subscribed to this thread.
> Reply to this email directly, view it on GitHub
> <#5 (comment)-
348576022>,
> or mute the thread
> <https://github.com/notifications/unsubscribe-auth/
AFS9xYjTN0UTE6qUopF0j6TB5LWbwlbOks5s8EmdgaJpZM4Qxwg0>
> .
>
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#5 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AUH5G_uKkTBtdC-dzoRsYLH7BIe9OoHhks5s8EocgaJpZM4Qxwg0>
.