There's something quietly subversive about building a fully playable boxing sim inside Excel. It's not just a technical party trick, though it is absolutely that, it's a reminder that the tools we use every day for budgets and data entry are capable of far more than we typically ask of them. The creator spent two months of evenings wrestling with VBA, color-coded shapes, and a commentary system that had to feel alive rather than robotic. That effort shows. And it matters, because it challenges the assumption that meaningful software has to be built on new platforms with new languages. Sometimes the most accessible canvas is the one already sitting open on your screen.
What stands out here is the problem-solving mindset, not the novelty of the game itself. The commentary system alone is a case study in working through constraints. Storing hex codes, converting them to RGB because VBA only speaks that language, then using those values to dynamically color shapes based on which boxer is throwing a punch, that's not just coding. That's translating a design idea into a working system within a tool that wasn't built for it. The creator also recognized the limits of their own approach: they wanted more variety in the commentary, considered using Copilot or random selection, but moved on when the trade-offs didn't make sense. That kind of honest evaluation is rare. It's easy to force a solution because it sounds impressive. It's harder to say no and keep the experience fast and responsive.
For anyone who's ever opened Excel and felt like they were only scratching the surface, this project is a nudge in a more ambitious direction. You don't need to build a game to learn something from how this was made. The logic is laid out plainly across the "Fight Engine" and "Fight Calcs" sheets. The pause functions, the flashing text boxes, the way the active boxer is determined by a separate attack-and-defend interaction, these are transferable patterns. They apply to dashboards, to automation, to any complex workbook where you need events to trigger visual changes or sequenced outputs. The creator didn't invent new tools; they used existing ones more deliberately. That's a lesson worth carrying forward, especially when the default move is to reach for a new app instead of pushing the one you already have.
The honest takeaway is that this project works because it respects the medium. Excel isn't pretending to be a game engine. It's being used as a logic layer, a display board, and a timing mechanism all at once, and it holds up. That's not a critique of game engines or a claim that everyone should build their next project in a spreadsheet. It's an argument for starting where you are and using what you know. The creator even admits they're using VBA less at work now, leaning on Power Query for daily tasks. But this project wasn't about efficiency. It was about seeing an idea through, solving problems as they came, and sharing the result openly for others to pull apart. That's the part worth copying. Not the boxing sim. The willingness to build something that didn't exist in a tool that already did.