How I Built a Fast-Loading Game Guide Site for Arms of God (And What I Learned About Roguelike Depth)
Been playing Arms of God for about 3 weeks now and honestly, this game has no business being this deep. You pick up these divine weapons, each with completely different move sets, and suddenly you're theory-crafting builds at 2am.
So I did what any sleep-deprived dev would do — built a guide site.
The technical side was actually interesting because roguelike data is messy. Weapon synergies aren't linear, blessings stack in weird ways, and the community keeps discovering new tech every week. Static pages wouldn't cut it.
I ended up structuring everything as modular content blocks:
- Weapon data lives in JSON with relational tags for synergy mapping
- Build guides use a custom MDX setup so I can embed interactive weapon comparison tables
- Image optimization pipeline keeps load times under 1.5s (critical when someone's mid-run checking a guide)
The Arms of God content was way more nuanced than I expected — things like the Gauntlet's timing windows varying by 3-4 frames depending on which blessing you've stacked, or how the Spear's divine judgment proc actually scales with movement speed not attack speed (still waiting for that to get patched tbh).
Built the whole thing on Astro with minimal JS. Lighthouse scores are 98+ across the board and it stays snappy even with 40+ embedded gameplay clips per page. If you want to see how it turned out, I put together a quick overview of the Arms of God structure and the specific weapon guides that took the most research.
What roguelike systems have you found surprisingly hard to document properly? The RNG seed mechanics always trip me up.
Top comments (0)