I've been working on a fan site for Killer Bean lately and figured I'd share some of the more interesting implementation details, especially if you're building game hubs or wiki-style sites.
The biggest challenge was rendering firearm stats in a way that actually helps players compare loadouts. Most shooter wikis just dump numbers into tables, but Killer Bean's weapon pool has weird modifiers — some guns have "bean-seeking bullet physics" that aren't reflected in base DPS values. So I ended up building a quick data layer that pulls from in-game testing data spreadsheets and renders them as visual stat bars with conditional tooltips explaining the hidden mechanics.
For the mission guides, I ditched the traditional walkthrough format and went with a decision-tree component. Each boss fight section dynamically loads tips based on which weapon loadout you clicked earlier, since strategies diverge hard depending on whether you're running the Dual Wield Deagles or the Explosive Burrito Launcher. The state management for that got messier than expected — definitely underestimated how many branching paths there are.
A few things that worked surprisingly well:
SVG bean sprites for the weapon icons. Way lighter than PNG spritesheets when you're rendering 40+ guns on a single page, and they scale perfectly on mobile without looking blurry.
