Thread:Ffets/@comment-27219153-20170511211040/@comment-27219153-20170521175046

I would have to vote B as well.

Concerning the template and pages with a recipe whose name makes sense to be the pagename, my idea was to have the logic like this:

If option one and two exists, do:   (same as Ffets)

If option one exists but option two does not, do:   (different than Ffets)

vs. Ffets method of the second logic statement:  

The only case that this really matters in is brick pages. Instead of calling the normal brick recipe brick/Brick I used the pagename Angmar Brick, thus you could type instead of  The way Ffets did suspicious meat definitely makes sense for a single recipe page. I'm thinking that the best decision would be to keep my logic statements for the brick pages (Ffets method still works with the additional logic I added back in) and use Ffets method as a cleaner alternative for the single recipe pages. This would allow for much easier addition of recipes (adding recipes to a single recipe page would only require one edit instead of two or three) to single recipe pages if something were to be added to the game.