3 replies to this topic

[felinoel]

So I was talking with timrem when I came upon a burning question, how should we document recipes for items in modpacks that are seemingly random and insane solely for the purpose of making the pack much, much more difficult?

In the past we've seen a similar concept happening with the GregTech mod and we just documented the GregTech recipes alongside the normal recipes, but this question I have is for the BlastOff modpack and that modpack alone. Just about everything in that modpack is changed from Mana Pearls from Botonia needing Eyes of Galgador from Steve's Carts to sticks and coal only making one torch each.

I figured we can just ignore that modpack as that is likely the simplest route, at least unless we somehow do that thing I proposed a while back that gives you a series of options like Minecraft version and modpack and then somehow only showing you information for that selection. Thoughts?

[Aezex]

It doesn't seem reasonable to have to add new recipes for mods changed by MineTweaker and such. If we were to do that, we would always be changing them due to modpack changes. If somone created an API that could access some master modpack database (*pokes Curse*) and update the page itself, that would be reasonable. But there is no such thing in existence, so I think we should leave it be. Besides, it could be very confusing for any new users trying to find the right recipe.

[dgelessus]

It might be good to reconsider whether we want to include modpack-specific recipes (with MineTweaker or otherwise) at all, since they only affect a relatively small fraction of all Minecraft mod users. If the number of changed recipes is reasonably small, should they be listed on the modpack page instead?

[ostPavel]

Yeah, a page like ModPackName/Recipe_Changes never hurts.