Talk:Cauldron
How to: add an entry to the Cauldron table
Currently, we're using the following format for a single Outcome Item:
|-
{{:Bee Stinger|regionalRow}}
|-
{{:Bee Stinger|regionalRowMirrored}}
Ensure you add both rows, so users can use column sorting to search more easily.
How we got here:
I'm new to wiki editing, but I've been tinkering with this one. This page caught my attention since it was an obvious problem in terms of maintenance / upkeep.
Previously: each row's data was entered manually, and two rows per output item (the second has the Source Item 1/2 reversed (2/1) so that sorting the columns gives table searchability). This lead to a huge table which was basically impossible to expect the community to maintain.
As a result, the table was hugely outdated before my update a day or so ago (as per below).
Currently: I've replaced manual entries with implementations of regionalRow and regionalRowMirrored. This draws the data from each individual item page, making them the source of truth instead. I also updated many of them.
Whilst the duplication is not ideal, it serves to keep the previous versions' searchability (some discussion on my user page).
- Note: I've removed seasonal recipies (those including
Hard-boiled egg and 
Seasonal Pumpkin) since many of them lacked their own dedicated item page, and we can't correct / create / update anything since they're not in the game currently (as of writing) and we can't confirm their correct info. I'd guess it's highly plausible they wouldn't be the same next time they come back, anyway.
Future Improvements:
- if possible (idk) a singular function to call that returns both regionalRow and regionalRowMirrored on the next line. This would remove code duplication in order to generate the two rows we currently want for each entry, with only a single code line. I'd guess this could be done by simply adding another switch statement in Infobox cooked item/as.
- add an actual search / filter function. I'd guess a drop-down containing each Source Item in the table, which only shows rows with a matching Source item 1/2 once selected.
- I think search/filter by Source Item 1 or 2 individually is probably not useful, since:
- the order in which they are listed is arbitrary
- filtering down by both Source Item 1 & 2 yields results sufficient for the other use case anyway (particularly once mirrored rows are removed)
- I think search/filter by Source Item 1 or 2 individually is probably not useful, since:
- remove duplicate rows (requires an alternative search function to be in place before removal in order to maintain searchability)
- Seasonal Recipies: Maybe they could/should be in their own table(s)? Maybe a table per unique event (Halloween / Easter / Christmas)? Maybe that's at the cost of searchability, but I wouldn't want recipies that aren't in the game for most of the year clogging up the main table. idk.
Benjiminio (talk) 12:51, 3 July 2026 (UTC)
