queen spear
Abstract: I am proposing an enhancement to the inventory/loadout system that makes individual weapon builds more identifiable, shareable, and ultimately more meaningful, both from a gameplay and ecosystem perspective.
Current Problem: When experimenting with multiple builds of the same weapon (e.g., several Kestrel variants), there’s currently no way to distinguish them at a glance. If I maintain three different Kestrel builds with different attachments or stat tradeoffs, the only way to identify which is which is to manually add each one to a loadout and click “Modify.” This creates unnecessary friction, especially for players who actively test or iterate on builds.
Proposed Feature: Enable players to name individual custom weapon builds within their inventory/loadouts.
This would allow players to:
• Quickly identify specific builds (e.g., “Kestrel – Joker Build,” “Kestrel – ADS Optimized,” “Kestrel – What Would Seli Do,” etc.)
• Manage multiple variants of the same weapon more efficiently
• Reduce loadout friction for both casual and competitive players
Future Extensions (Optional / Iterative)
• Once naming exists, this naturally unlocks additional layers:
• Toggle builds as private or public
• Archive/retire builds with era data and statistics - museum mode
• Share builds with the community
• Display aggregate metadata such as
• Usage frequency
• Win/success rate
• Popularity and distribution
This would meaningfully increase player expression and community-driven discovery around weapons and playstyles.
Chain Justification & Incentives (Optional, Opt-In)
Public builds could be optionally “published” on-chain by pinning the build data (e.g., via IPFS/Pinata). Publishing a build could require a small $GUN listing fee, creating:
• Increased on-chain transaction volume at scale
• A lightweight economic sink tied directly to gameplay
• A foundation for future creator- or reputation-based systems
Importantly, this does not need to be mandatory. Players who want pure gameplay can ignore it entirely, while power users and creators opt in.
Why This Matters
This is a low-friction UX improvement that:
• Solves a real, current usability issue
• Scales naturally into deeper systems over time
• Appeals to both casual and competitive players
• Aligns with long-term on-chain and ecosystem incentives without forcing them
Happy to expand further, but even the base version (named builds) would be a quality-of-life win and be of interest to myself and maybe a much greater part of the community as well.