Projects

Project

Pythagorean Harmony

Equation-duel combat prototype for a fantasy third-person action RPG.

Playable Prototype

Problem

Educational games often become homework with graphics or trivia pasted onto combat.

That is not the interesting version of the idea. The interesting version is making math part of the combat grammar itself: visible, physical, tactical, and legible under pressure.

The design problem for Pythagorean Harmony is whether equation solving can become a combat loop instead of an interruption. The player should not stop playing the game to answer a worksheet prompt. The equation should be the enemy state, and combat should be how the player transforms it.

Core Idea

Enemies are not just HP bars.

Each enemy has an equation. The player reads that equation, survives the enemy, uses operation weapons to transform it, then uses the X weapon to execute once the correct value is known.

Wrong answers should not merely say “incorrect.” They should create combat consequences, such as enemy evolution or a changed enemy state. The math has to matter inside the fight.

Prototype Combat Loop

01

Enemy Equation

Enemy state is shown as an equation, not just HP.

02

Read Under Pressure

Player survives attacks while reading the equation.

03

Operation Weapon

Weapon actions apply algebraic operations.

04

Transform Equation

The enemy state changes as the equation is simplified.

05

Solve x

Player identifies the correct value.

06

X Weapon Execute

Correct value enables execution.

07

Wrong Answer Evolution

Incorrect answer changes enemy state instead of only showing failure.

System diagram, not a gameplay screenshot. It shows the intended equation-duel loop while the prototype visuals remain early.

  1. Read the enemy equation.
  2. Survive enemy attacks.
  3. Input numbers or choose operation weapons.
  4. Use operation weapons to simplify or transform the equation.
  5. Identify the correct value of x.
  6. Land the X weapon execution.
  7. If the answer is wrong, the enemy state changes or evolves.

Example Encounter

An enemy displays:

x + 5 = 10

The player reasons:

x = 5

Then the player lands the X weapon with 5 to execute the enemy.

A more advanced enemy could require multiple operation steps before the X weapon is safe. The prototype direction is not only “type the answer.” It is operation choice, timing, reading, pressure, and execution.

Core Systems

Equation Enemy

The enemy's state is an equation, making the learning object part of the combat target instead of a separate quiz layer.

Operation Weapons

Weapon actions represent algebraic operations, letting the player transform the enemy equation through combat interactions.

X Weapon Execution

Once the correct value is known, the player uses the X weapon to execute the enemy with the answer.

Wrong Answer Evolution

Incorrect answers create combat consequences, such as enemy evolution or changed state, instead of ending at a simple failure message.

Combat Readability

The prototype depends on readable equation state, visible operation effects, clear execution timing, and understandable failure feedback.

UE5 Third-Person Prototype

The first playable prototype uses Unreal Engine 5's Third Person Template as the movement and camera foundation.

C++ Core / Blueprint Tuning

Core systems live in C++, with Blueprint used for tuning and simple linking where iteration speed matters.

Technical Highlights

  • Designed a combat loop where the learning object is the enemy state, not a separate quiz.
  • Turned algebra operations into weapon interactions.
  • Scoped the project around proving the core loop before building a full game.
  • Used UE5 third-person foundations with C++ core systems and Blueprint tuning.
  • Built around readable player feedback: equation state, operation effects, correct answer execution, and wrong-answer consequences.

Current Status

Pythagorean Harmony is a first playable prototype and lab project.

The current focus is proving whether equation-duel combat can feel readable, tactical, and physical enough to justify deeper game development. It is not a full RPG yet. A full world, progression system, enemy roster, and long-term content are out of scope for the current prototype.

The working frame is “Math Souls Prototype: Equation Duel”: prove the duel, then decide whether the larger game deserves to exist.

Source repo is currently private while the prototype is being cleaned up.

What This Demonstrates

Gameplay systems design Educational mechanic design Unreal Engine prototyping C++ gameplay architecture Combat loop design Scope control Abstract math into interactive systems

Screenshots / Demo Proof

placeholderEquation enemy

Equation enemy

planned

Planned screenshot slot for an enemy presenting equation state in combat.

placeholderOperation weapon interaction

Operation weapon interaction

planned

Planned demo slot for transforming an equation through combat actions.

placeholderX weapon execution

X weapon execution

planned

Planned demo slot for executing an enemy with the correct value of x.

placeholderWrong-answer evolution

Wrong-answer evolution

planned

Planned demo slot for showing combat consequences after an incorrect answer.

placeholderUE5 prototype view

UE5 prototype view

planned

Planned screenshot slot for the first playable third-person prototype.

Proof Notes

  • First playable prototype, not a full RPG.
  • Core loop is equation-duel combat.
  • Core systems are C++ with Blueprint tuning.
  • Source repo is currently private while the prototype is being cleaned up.

Links

All projects