by Robc » Sat Aug 16, 2014 3:46 pm
Looks like I goofed up pretty seriously again... I am glad you are keeping me honest. The complexity of brewing is amazing especially when you try to teach it to a computer. Anyway, the fault in this case is definitely mine.
I added the barleywine styles at the same time as the sour styles. In the process of creating the new quality algorithms I made a last minute decision to replace Gueuze with an English Barleywine (split off from the American Barleywine style). My mistake was that I still left the 'sour' requirements and other recipe info associated with a Gueze attached to the style... so unless you chose to make a sour barleywine you would be penalized heavily. My bad. I have removed the sour requirements which should make a huge difference in your quality. The American Barleywine style was not affected by this problem.
Furthermore...
I modified the hop character of the English Barleywine algorithm to be closer to the Old Ale style and to reflect that the English style is less hoppy than the American style.
I modified the algorithms' expected grain bill to be closer to the Old Ale style.
Not much I can do to make up for my mistake in the past batchs but I will do the following for you River and anybody else who has an English Barleywine label. First I have reset your "New Release Party" flag so you can have a new release party when you get the quality where you want it. Second I will adjust the beer quality in your cold storage to match the quality in your first (or one of your early) batches which should bring your quality score up considerably and you won't suffer from the averaging effect of adding new beer to old. Remind me please to do this when you have a batch quality you think is good enough, thanks.
Thanks again River, I am in your debt for calling my attention to an important problem in the code.
-Robc