TechPack on 5.4.1 Server Doesn't Display Recipe for Gravel Sieve, An Overlooked Modding Error?

[joe7575]

TechPack on 5.4.1 Server Doesn't Display Recipe for Gravel Sieve, An Overlooked Modding Error?

[BuckarooBanzay]

Ok, i got it to work with the sfinv mod, the problem was the aliasing after the craft registering,
this patch should do it:

diff --git a/gravelsieve/init.lua b/gravelsieve/init.lua
index dd530a2..7dc155c 100644
--- a/gravelsieve/init.lua
+++ b/gravelsieve/init.lua
@@ -693,7 +693,7 @@ minetest.register_node("gravelsieve:compressed_gravel", {
 })
 
 minetest.register_craft({
-       output = "gravelsieve:sieve",
+       output = "gravelsieve:sieve3",
        recipe = {
                {"group:wood", "",                      "group:wood"},
                {"group:wood", "default:steel_ingot",   "group:wood"},
@@ -702,7 +702,7 @@ minetest.register_craft({
 })
 
 minetest.register_craft({
-       output = "gravelsieve:auto_sieve",
+       output = "gravelsieve:auto_sieve3",
        type = "shapeless",
        recipe = {
                "gravelsieve:sieve", "default:mese_crystal",  "default:mese_crystal",

[joe7575]

I have no idea how to do that.
I recommend to use the mod unified_inventory. That has an interface function to register foreign recipes.
AFAIK sfinv does not provide something similar.

Edit: Sorry, I did not read the question correctly. I thought you mean sieving recipes and not the recipe for the Gravel Sieve itself.

[BuckarooBanzay]

This looks like a bug in the sfinv mod, the recipe is properly registered:

techpack/gravelsieve/init.lua

Lines 704 to 710 in 7f7c568

	minetest.register_craft({
	output = "gravelsieve:auto_sieve",
	type = "shapeless",
	recipe = {
	"gravelsieve:sieve", "default:mese_crystal", "default:mese_crystal",
	},
	})

[FriendlyGamer]

This looks like a bug in the sfinv mod, the recipe is properly registered:

techpack/gravelsieve/init.lua

Lines 704 to 710 in 7f7c568

	minetest.register_craft({
	output = "gravelsieve:auto_sieve",
	type = "shapeless",
	recipe = {
	"gravelsieve:sieve", "default:mese_crystal", "default:mese_crystal",
	},
	})

Then how come everything elses in this mod pack get registered into the guide? We can see among other things...
Tubes
Grinder
Pushers (both variants)
Distributors
Techpack Street Lamp (or whatever it was)
and so on...

How come the Gravel Sieve is the "single man out"?

[FriendlyGamer]

Ok, i got it to work with the sfinv mod, the problem was the aliasing after the craft registering,
this patch should do it:

diff --git a/gravelsieve/init.lua b/gravelsieve/init.lua
index dd530a2..7dc155c 100644
--- a/gravelsieve/init.lua
+++ b/gravelsieve/init.lua
@@ -693,7 +693,7 @@ minetest.register_node("gravelsieve:compressed_gravel", {
 })
 
 minetest.register_craft({
-       output = "gravelsieve:sieve",
+       output = "gravelsieve:sieve3",
        recipe = {
                {"group:wood", "",                      "group:wood"},
                {"group:wood", "default:steel_ingot",   "group:wood"},
@@ -702,7 +702,7 @@ minetest.register_craft({
 })
 
 minetest.register_craft({
-       output = "gravelsieve:auto_sieve",
+       output = "gravelsieve:auto_sieve3",
        type = "shapeless",
        recipe = {
                "gravelsieve:sieve", "default:mese_crystal",  "default:mese_crystal",

Applied to server and worked like a charm. Thanks you @BuckarooBanzay for caring to help us diagnose this issue with the mtg_craftguide as Rudenwardy on Discord kindly reminded me of. :)

@joe7575 If I may kindly have your attention and your dedication for just a minute please...

I would just like you to become aware of the critical importances of supporting Sfinv and consequently mtg_craftguide at least in the basic senses. I would like to explain a bit on why these interfaces assists me in being able to enjoy the game...

You see I am Deaf and Blind and among other settings and controls I am required to have the UI (or otherwise menus) setting increased up to 2x the size of the MTG defaults. Thus far the people on Discord express to me also there's currently on way for an alterative menu such as Unified Inventory to support this.

So if you could please @joe7575 reconsiders your decision and stance on Sfinv to at least allocate enough time to make sure the basics are support (e.g. like the CRAFT recipes of your blocks like we just did with @BuckarooBanzay ) that would be wonderful and much appreciated on my end. :)

I thought to express myself in such manners because I totally gets it, you probably didn't mean this at all and just had your testing setup and/or workflows only to addresses it on Unified Inventory standpoints.

So all in all, I hope you are able to understand all of this @joe7575 and I appreciate if you can give it a 2nd consideration. :)

Thank you very much in advance for your time and efforts once again. :)