Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Created foods should be searchable on the guidebook like drinks are. #34342

Open
Alpaccalypse opened this issue Jan 9, 2025 · 1 comment
Open
Labels
A: Guidebook Area: Ingame guidebook, content or technical implementation D3: Low Difficulty: Some codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Needs Content PR Merged Status: Requires an existing SS14 PR to be merged first. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: New Feature Type: New feature or content, or extending existing content

Comments

@Alpaccalypse
Copy link
Contributor

Alpaccalypse commented Jan 9, 2025

Description

Other than base reagents, food cannot easily be added to the guidebook.

Reproduction
If you want to add foods to the guidbook, you have to add them as entities, one at a time, and without any supporting XAML layout to go with them, like reagents have.

Additional context
It would be a useful addition to the guidebook to be able to browse foods and see their recipes and properties, like you can with drinks. Adding support for food entities to a guidebook group category and giving them XAML support to show their recipes and effects would allow for a much more informative chef section of the guide and also an easily browsable list as is the case with drinks.

Recipes can be added currently, but are just a static line of text, that could also benefit from some XAML layout improvements, along similar lines, and would tie in with this nicely.

If the above was implemented, you would be able to setup much of the guide to automatically update as new foods are added to the .yml

@github-actions github-actions bot added the S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. label Jan 9, 2025
@lzk228
Copy link
Contributor

lzk228 commented Jan 10, 2025

yeah, there is already a pr for this #34105

@lzk228 lzk228 added P3: Standard Priority: Default priority for repository items. T: New Feature Type: New feature or content, or extending existing content D3: Low Difficulty: Some codebase knowledge required. A: Guidebook Area: Ingame guidebook, content or technical implementation S: Needs Content PR Merged Status: Requires an existing SS14 PR to be merged first. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. and removed S: Untriaged Status: Indicates an item has not been triaged and doesn't have appropriate labels. labels Jan 10, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A: Guidebook Area: Ingame guidebook, content or technical implementation D3: Low Difficulty: Some codebase knowledge required. P3: Standard Priority: Default priority for repository items. S: Needs Content PR Merged Status: Requires an existing SS14 PR to be merged first. S: Requires Content PR Status: Requires a change to SS14, for which there is no open PR currently. T: New Feature Type: New feature or content, or extending existing content
Projects
None yet
Development

No branches or pull requests

2 participants