Recipe Guidebook of the Future #198
Conversation
We have a Recipe Book. It's out of date. It's unwieldy. I wanna look at the Recipes for the game in the game. These scripts allow that to happen. Running gen_recipes_wiki.exe will update the wiki.txt file in tools with the recipes needed (may need to change where this is placed.) Running update_guidebook.exe will take wiki.txt and translate it's contents using the RecipesGeneratedHeader.xml into RecipesGenerated.xml. RecipesGenerated.xml is pointed to by the new Recipes page of the Guidebook. There is a very solid chance this breaks down. Things that could make it break down: A recipe for a food with a bizarre special character in its name (think $ or @) Requiring something that is not a reagent or a solid in a recipe. (It wouldn't break badly from this, it just wouldn't display the ingredients.) Future formatting changes. (if someone changes Reagents to Liquids, for example.) However, as-is, I've done just about everything I can to future-proof these scripts, and they're designed and commented in such a way that another person should theoretically be able to come in after me and change the variables at the head of each file to get what they want. If they want to do more than that with them, though... Good luck.
|
Saying the wiki is "out of date" and "unwieldy" is very mean and I feel offended. /j Also it would be neater if it could be automatically generated like the Chemicals page or at least have a search bar because that's a lot of recipes just crammed in one page. |
|
I did not mean any offense! I simply want to make maintaining it easier, and that is the plan with these scripts. It is autogenerated with the scripts I've provided in the PR. The lack of a search bar is more of an issue with the Guidebook, unfortunately. Changing it that significantly seems more of an issue for Upstream. I know we have search boxes for Cargo items, but scanning through a list of entities vs a text box may take some consideration. Thank you for your feedback. |
There was a problem hiding this comment.
Mystery files will not be accepted
There was a problem hiding this comment.
It's better to stay consistent and use .py or .ps1 files. Or moving these into seperate folders and using a py/Powershell/batch script to invoke them
We have a Recipe Book on our wiki. It's out of date. It's unwieldy.
I wanna look at the Recipes for the game in the game.
These scripts allow that to happen.
Running gen_recipes_wiki.exe will update the wiki.txt file in tools with the recipes needed (may need to change where this is placed.) Running update_guidebook.exe will take wiki.txt and translate it's contents using the RecipesGeneratedHeader.xml into RecipesGenerated.xml. RecipesGenerated.xml is pointed to by the new Recipes page of the Guidebook. There is a very solid chance this breaks down. Things that could make it break down: A recipe for a food with a bizarre special character in its name (think $ or @) Requiring something that is not a reagent or a solid in a recipe. (It wouldn't break badly from this, it just wouldn't display the ingredients.) Future formatting changes. (if someone changes Reagents to Liquids, for example.)
However, as-is, I've done just about everything I can to future-proof these scripts, and they're designed and commented in such a way that another person should theoretically be able to come in after me and change the variables at the head of each file to get what they want. If they want to do more than that with them, though... Good luck.
About the PR
Media
Changelog
🆑 JJ