TGB 1.7.4: Anatomy of a 2D Game Engine

For all you TGB fans, you might have noticed a recent disturbance in the force. First, you should know that Melv May's got his thinking cap on and is working on new plans for TGB. We're taking a good hard look at the internal guts of TGB and figuring out ways to improve it for future big releases. We have some super active GG community members who are voicing their opinions and helping us tackle the bigger pictures. Keep throwing the ideas at us, guys!


Leonardo would have drawn a better picture of TGB's internal anatomy, but I don't have his sketching skills.

Before we tackle the big issues, however, there were a couple of things we wanted to touch-up from the release of TGB 1.7.3. Which leads me to...

TGB, Under the Knife

This fix was mainly some minor cosmetic surgery: removing a mole here, shaving off some unwanted fat cells there. Specifically, the release has been enhanced as follows:

• t2dTrigger onLeave working properly again without source code modifications
  
• "LINK" mode image-maps back to "normal" (image maps, that is)
  
• Mac hardware cursor showing
  
• Unstuck sticky corners
  
• Killing particle effects without making them all disappear
  

Big thanks to Melv May (of course!), Matt Langley, and Ken Holst for administering all treatment to v. 1.7.4, from check-in to post op.

Recommended Check-Ups for TGB

So what's in store for TGB's future? We're still working out the details. We have a pretty good idea of what you want in future versions of TGB, but it's always good to gather opinions in various formats. Start voicing things here, in Melv's previous blog, in the TGB forums, and also via this survey. Because without symptoms, we can't correctly diagnose the problem.

Happy game making and remember to eat your veggies!