This is a long shot, but writing up the ingredient variables made me think of it: If you know what specific ingredients are going into a dish, it is 100% possible to predict the unstarred and starred dish sell values. (It’s not 100% possible to predict the star rate… yet. I’m working on it.)
Given that PPA already allows hosts to specify different ingredients to be used, it could also potentially calculate the dish sell values. This could be useful to hosts (i.e., help choosing what fish, mushroom, etc. to use, either to ensure consistent stacks, or to avoid the Ancient Koi “rare fish that doesn’t make you money” trap) and useful to prospective partygoers (“Will this food stack with the stuff I already have?” “How much more is this hour-long poke party worth than than this 40-minute sashimi party?” “Is this for selling or for eating?”)
I have a whole writeup on this based on Dalia del Rosa’s initial findings and my own further research after the Luna New Year 2024 and Elderwood updates, on this Google Sheet.
The main wrinkle is that there are a few very weird exceptions to the rules — Stuffed Cabbage Rolls and Spicy Honey-Baked Muujin come to mind, as well as several vegetables that don’t contribute properly to the dish sell value when chopped. So it’s not as simple as just plugging the unstarred sell values of all the ingredients into the formula.
Building on this concept, it would also be nice if hosts could choose to display any combination of the following on a cooking party:
Focus amount granted if you eat the dish (starred and unstarred) — I seem to remember that PPA used to display this, a long time ago?
Dish sell value (starred and unstarred)
Estimated expected star rate (a percentage — can’t calculate this yet, but experienced partygoers will have a pretty good feel for it and could enter it manually)
Expected revenue (by combining the previous two bullet points and the dish quantity)
OR minimum/maximum revenue (based on 50% base star rate for the minimum, and 100% star rate for the maximum)
Expected duration (iirc you already have this planned!)
Base XP per round/per item (fixed values — always the same every time the recipe is completed), which also tells you how much focus each cooking round consumes
Expected XP for the whole party before focus bonus (previous item x dish quantity)
(The last two could also apply to charged flow tree parties, where instead of dish quantity, it’s # of trees.)
While we’re dreaming, perhaps at some point these items could be used to filter parties: I need to make 150k gold in the next 24 hours to complete this building project — show me all the parties over 50k revenue with duration under 60 minutes from this date to this date
In all truth, I probably should be looking into writing my own tool for this — but since it could also be a potential value-added for PPA, I figured I’d float it by you anyway. :)
Please authenticate to join the conversation.
In Review
Feature Request
About 1 month ago

Eliot Reinald 🧮
Get notified by email when there are changes.
In Review
Feature Request
About 1 month ago

Eliot Reinald 🧮
Get notified by email when there are changes.