RuneCore

RuneCore is a modular magic system designed for future Hytale modding. It is fully engine-agnostic and written in pure Java, allowing development and testing even before the Hytale API is available.

---

Features

• Mana-based spell casting
• Cooldown system
• Consumable runes
• Multiple magic schools
• Player level requirements
• Fully testable without a game engine

---

Magic Casting Flow

1. The player selects a spell
2. SpellCaster validates:
   • Player level
   • Available mana
   • Cooldown status
   • Required rune (if any)
3. Resources (mana and rune) are consumed
4. The spell logic is executed using SpellContext

---

Project Structure

com.cookie.runecore
├── api            # Core contracts (Spell, SpellContext)
├── casting        # Spell casting validation and execution
├── cooldown       # Cooldown management
├── player         # Magic player data (mana, level, runes)
├── rune           # Runes and rune registry
├── school         # Magic schools
├── spell
│   ├── impl       # Spell implementations by school
│   │   ├── fire
│   │   ├── ice
│   │   ├── shadow
│   │   ├── arcane
│   │   └── nature
│   └── SpellRegistry.java
├── debug          # Console-based testing environment
└── RuneCore.java  # Mod entry point

---

Console Testing

RuneCore can be tested without any game engine using a console simulation.

Run the console test:

./gradlew runConsole

Available test spells:

• fireball
• frost_spike
• shadow_step
• arcane_missile
• root_bind

---

Design Philosophy

• Core logic never depends on the game engine
• All engine-specific code will be isolated in adapters
• Minimal refactoring will be required when the Hytale API is released
• Clear separation between logic, data, and effects

---

Future Plans

• Hytale API adapter layer
• Visual and particle effects
• Entity-based spell interactions
• Grimoire-based spell learning
• Advanced rune modifiers and variants

---

Requirements

• Java 17+
• Gradle

---