Lightning Forge Games

Lightning Forge Games is a game studio in Newcastle, New South Wales, Australia. It develops Gladiator Mayhem, a 2v2 hero battler, and mints its Forge Key assets on Avalanche.

Ecosystem

Lightning Forge Games appears in no ecosystem directory. This record comes from the 2026-09-04 AVAX typed-edge research pass (backend/scripts/data/avax-typed-edges-proposal-2026-09.json), which sources relationships from first-party prose rather than from listings. PRIMARY SOURCE FOUND (this row's blocker is cleared): the studio's own domain lightningforge.games 301-redirects to gladiator-mayhem.com, whose footer reads '(c) 2025 Lightning Forge Games. All rights reserved.' and whose body carries a LIGHTNING FORGE GAMES section naming Newcastle, New South Wales. The earlier gam3s.gg trade-press citation is no longer load-bearing. HANDLE COLLISION FOR LAM: lfg_gtfo is linked from the game site's footer and reads like the studio's account, but it is already the ACTIVE, POLLING primary handle on the existing gladiator-mayhem entity (tags/1xU3enJqkCr8XnE6F2GA, 50 tweets fetched). This row therefore takes handle:null; whether the handle should move from the game to the studio is a curation decision with a live polling consequence and is not taken here. Sourced in the 2026-09-04 typed-edge research pass; this row exists to carry that researched edge, not because the org appears in any directory.

Enrichment note

This entry is a SHELL created from the 2026-09-04 typed-edge research pass. Its prose restates what the cited first-party sources say and nothing more — it is not editorial and no company profile has been written. It exists so the graph can carry the researched typed edge for Lightning Forge Games (gladiator-mayhem DEVELOPED_BY lightning-forge-games); replace it with a researched About body before it carries coverage.

Chain membership: The Gladiator Mayhem site's Forge Key section carries a 'MINT ON AVAX' call to action, placing the game's on-chain asset on Avalanche. Third-party aggregators additionally claim a Beam deployment; Beam is not a registry chain and no first-party Beam statement was found, so it is not recorded.