Honey Buzz cover
2020BGG rank #470

Honey Buzz

by Paul Salomon · Elf Creek Games

Browsing is free. Ask BoardGameBrain about this game when rules coverage is ready.

Players1–4
Time45–90m
ComplexityMedium-Light
Age10+

About the game

What is Honey Buzz?

The bees have discovered economics. The queens believe that if they sell honey to the bears, badgers, and woodland creatures, they will find peace and prosperity. Spring has arrived and it's time to build the hive, find nectar, make honey, and, for the first time ever, set up shop. Honey Buzz is a worker bee placement game where players expand a personal beehive by drafting various honeycomb tiles that grant actions that are triggered throughout the game. Each tile represents a different action. Whenever a tile is laid so that it completes a certain pattern, a ring of actions is triggered in whatever order the player chooses. A tile drafted on turn one could be triggered up to three times at any point during the game. It all depends on how the player places their beeples (bee+meeple) and builds their hive. After all, in the honey business, efficiency is queen. As you continually expand your hive, you'll forage for nectar and pollen, make honey, sell different varieties at the bear market, host honey tastings, and attend to the queen and her court. There's only so much nectar to go around, and finding it won't be easy. Players will have to scout out the nectar field and pay attention to other players searches to try to deduce the location of the nectar they need for themselves.

How it plays

Mechanics

Action RetrievalContractsEnclosureEnd Game BonusesGrid MovementHexagon GridIncomeMarketMemoryModular BoardOpen DraftingPattern BuildingPieces as MapRaceResource to MoveSolo / Solitaire GameSquare GridTile PlacementVariable Set-upWorker Placement

On the shelf

Categories

AnimalsEconomic

Questions players ask

Questions to bring to BoardGameBrain

  • How do setup and the first turn work in Honey Buzz?
  • When does scoring happen and what ends the game?
  • How should the table resolve an unusual timing or rules interaction?