# max buffer units change **URL:** \ **Category:** Bugabee\ **Created:** [November 26, 2015, 2:47pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655 "2015-11-26T14:47:52Z")\ **Posts on this page:** 6\ **Page:** 1
**Author:** ![galtsubery](https://avatars.discourse-cdn.com/v4/letter/g/9e8a1a/32.png) [@galtsubery](https://forum.beeminder.com/u/galtsubery)\ **Post date:** [November 26, 2015, 2:47pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655/1 "2015-11-26T14:47:52Z")
Hi, Did the units of the max-buffer settings change couple of days ago? Seems like it was changed from measuring days to amount of buffer. I liked the previous one better as it means I only need to change the steepness of the road in one place. ---
**Author:** ![philip](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/philip/32/1505_2.png) [@philip](https://forum.beeminder.com/u/philip)\ **Post date:** [November 26, 2015, 5:41pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655/2 "2015-11-26T17:41:31Z")
Hi Gal Yes, it was this week, and no, it’s not universal. Your **do more** (and other) goals still have both retro-ratchet and max-buffer settings in days. But ratcheting **do less** goals less likely to do the ‘right’ thing when, and the fix turned out to be to change the setting to be in buffer units. This means, for instance, that I can specify on my drink-less goal that I don’t want more than, say, 5 drinks of safety buffer, without worrying about the relation to a changing slope. I couldn’t find the announcement in a quick search, but there’s at least one very happy user: > [@Thanks, guys, for the new/improved...](https://forum.beeminder.com/t/thanks-guys-for-the-new-improved/1652/1): > > Thanks for fixing the retro-ratchet on the do-less goals! It now works perfectly, allows us to use “max units” as the buffer, and makes clear that this is what’s being used in the dialogues. Loving this fix! ---
**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\ **Post date:** [November 26, 2015, 8:06pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655/3 "2015-11-26T20:06:05Z")
> [@philip](#): > > I couldn’t find the announcement in a quick search That’s because we failed to announce it till just now: [https://twitter.com/beemuvi/status/669969979228291072](https://twitter.com/beemuvi/status/669969979228291072) ---
**Author:** ![drtall](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/drtall/32/1341_2.png) [@drtall](https://forum.beeminder.com/u/drtall)\ **Post date:** [November 26, 2015, 8:12pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655/4 "2015-11-26T20:12:48Z")
I’m happy to see this change! As a nitpick, the UI for it doesn’t seem to respect the `integery` setting. Not as useful as it could be: [![](https://dl.dropboxusercontent.com/s/5dyzsel1bzgjuow/Screenshot%202015-11-26%2012.12.36.png?dl=0) ](https://dl.dropboxusercontent.com/s/5dyzsel1bzgjuow/Screenshot%202015-11-26%2012.12.36.png?dl=0) ---
**Author:** ![drtall](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/drtall/32/1341_2.png) [@drtall](https://forum.beeminder.com/u/drtall)\ **Post date:** [December 6, 2015, 6:21pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655/5 "2015-12-06T18:21:04Z")
Also, it seems strange that I can’t retroratchet this: [![](https://dl.dropboxusercontent.com/s/8jzfvr02m0g8jia/Screenshot%202015-12-06%2010.20.37.png?dl=0) ](https://dl.dropboxusercontent.com/s/8jzfvr02m0g8jia/Screenshot%202015-12-06%2010.20.37.png?dl=0) I have a buffer of +3, so why couldn’t I retroratchet down to +2, +1, or +0? ---
**Author:** ![dreev](https://sea1.discourse-cdn.com/flex019/user_avatar/forum.beeminder.com/dreev/32/4311_2.png) [@dreev](https://forum.beeminder.com/u/dreev)\ **Post date:** [December 6, 2015, 7:13pm UTC](https://forum.beeminder.com/t/max-buffer-units-change/1655/6 "2015-12-06T19:13:37Z")
Confirmed that it ought to let you ratchet that! That might be an easy #UVI after a recent bugfix from @bee… >