Seeking Feedback: GAS-Based Spell Combination System - Balancing Complexity vs Accessibility

Working on a spell framework for my Mahabharata RPG (Epic MegaGrant submission) and looking for feedback on the design approach. \*\*The Challenge:\*\* I'm building a GAS-based system where players combine elemental essences to create spells. The goal is tactical depth without overwhelming players. Current design: \- 8 elemental essences (fire, water, lightning, earth, etc.) \- Players select 2 essences at a time to create combinations \- Element interactions create emergent effects (fire + water = amplified electricity for chain lightning) \- Hundreds of possible combinations from this system \*\*Questions for the community:\*\* 1. \*\*Complexity vs Accessibility\*\*: Is 8 essences with 2-at-a-time combinations too much for players to learn? Or does it provide good depth? 2. \*\*Data-Driven Approach\*\*: Everything's configured through data assets (no hardcoding). Has anyone tried similar approaches for spell systems? What pitfalls did you encounter? 3. \*\*Co-op/Multiplayer\*\*: With GAS integration, how do you handle spell combination balance when multiple players are creating different element states on the battlefield? 4. \*\*Teaching the System\*\*: What's the best way to teach players complex elemental interactions without overwhelming tutorials? \*\*Technical Context:\*\* Built on UE5.6 with GAS for multiplayer support. Actor-based system where each spell is a spawnable entity. Tag-based architecture for scalability. Demo video (for context): [youtube.com/.../watch](youtube.com/.../watch) Would love to hear from anyone who's built similar combination-based systems or has thoughts on balancing tactical depth with player accessibility!