![New Game Round-up: Agricola Unwrapped, From Stars to Heroes, and a Double Dose of Adventure Time](https://cf.geekdo-images.com/CBxR_eb-UiM1EHEMHA0B6w__thumb/img/gWM_u9rszFPD_oKMgEw9KK2ZpXY=/fit-in/200x150/filters:strip_icc()/pic2995818.png)
• Adventure Time Card Wars: Doubles Tournament, due out June 2016 from Cryptozoic Entertainment, is a team version of Adventure Time Card Wars as Jake and Charlie face off against Grand Prix and Moniker with new decks and special Teamwork cards that can give you and your partner a benefit turn after turn.
• Designer MJE Hendriks, known for Legacy: The Testament of Duke de Crecy, is founding his own publishing house. While he's commissioned artwork for his initial release, he hasn't yet revealed details about it, mostly because he's still trying to nail down what he should name the publishing house. He invites your suggestions here.
• After tweeting the message below, designer Antoine Bauza noted later that Takenokids will be a standalone game for young players, not a second expansion for Takenoko. Adorable tiny pandas incoming!
Working on project Takenokids with @Akashinai #boardgames #gamedesign @La_Thias
— Antoine Bauza (@Toinito) April 26, 2016
• UK publisher Backspindle Games is printing a new multilingual version of Leonard Boyd and David Brashaw's Codinca to debut at the UK Games Expo in June 2016, with new publishing partner Ninja Division picking up the titles for U.S. distribution.
• Agricola fanboi Tony Boydell received an advance production copy of Mayfair Games' new version of Uwe Rosenberg's industry-changing game design courtesy of artist Klemens Franz, with whom Boydell has worked on his own Snowdonia, and Boydell promptly posted many, many pictures of this new version of Agricola on his BGG blog.
Clearly this version will need a separate listing in the database after all, despite it being the same game at heart. Frustrating! We still need to figure out a way to list such new editions in a separate but equal way, despite history showing that "separate but equal" is a terrible policy that's unworkable in the long run. Its use probably isn't comparable to a situation in which you're cataloguing items in a database, but the phrase came to mind anyway. Okay, I should probably stop now.