The Figy, Wiki, Mago, Aguav and Iapapa Berry all use the Gen III/IV flavors, even in Gen V/VI. I'm not sure if it's a good idea to consider Berries' colors to be flavors, when the old flavor mechanic is still subtly present. --SnorlaxMonster 09:17, 4 June 2016 (UTC)
Split: Colors/Ice cream
The Gen V/Dream World ice cream "flavors" have nothing to do with spicy/dry/etc. Those should be on a different page.
SnorlaxMonster originally suggested the color split, but personally, the best reason I can think for it is that XY has 6 colors (compared to 5 flavors). ORAS does have 5 colors that correspond directly to conditions like flavors do/did, but I don't know if that might be enough reason to (perhaps) include only the ORAS color listing on this page. I have a feeling the simple answer is just having a dedicated page for "colors".
- FWIW: candidates: User:Tiddlywinks/Berry color, User:Tiddlywinks/Flavor (ice cream). Tiddlywinks (talk) 18:51, 17 February 2017 (UTC)
Incomplete for Generation 3?
Generation III flavors
When researching Poffin mechanics, it struck me that the flavors seem to be the same as for Pokéblocks, but represented in a different way. After checking the Ruby disassembly, it confirmed my suspicion: our flavors for Generation III Berries are derivations, not the raw values. This also explains why the circled flavors in Generation III often don't seem to make sense (they're actually the real flavors).
In fact, Pokéblocks have the exact same algorithm as Poffins, except that at step 4 you apply the RPM multiplier instead of the cooking time multiplier and spill/burn penalty. The flavor values we have for Generation III are the effective flavors after applying flavor penalties (e.g. Spicy is weakened by Dry, Dry is weakened by Sweet, etc.), divided by 10. In the algorithm we've defined on the Pokéblock page, as the first step you multiply the flavor totals by 10, but that's only because we've divided the real values by 10 in the first place.
There's an argument to be made that the post-penalty flavors are more useful than the raw values; a Razz Berry will never increase the spiciness of a Pokéblock, because its spiciness is cancelled out by its own dryness. However, if we want to display effective flavors instead of true flavors, I think we should be displaying the proper effective values (so 10 times what we currently display), and we should do it for both Generation III and IV.
However, I would prefer we display the real values. They actually make it clear why certain flavors are circled in Generation III. The only problem is that, while the Ruby disassembly shows us what the flavors for the Berries in the games' code are, we don't have the values for the e-Reader Berries. Most of the e-Reader Berries' true flavors are easy to reconstruct due to knowing which flavors are circled in red, but that's not possible for the Nutpea and Kuo Berries, due to all 5 flavors being present. While it doesn't actually have any functional impact (since the flavors always cancel each other out to make each other 0), if we're displaying the true values, this is something we would need to know. --SnorlaxMonster 10:55, 7 July 2019 (UTC)