Giving the player a useful answer
A tactics game asks players to make decisions with incomplete information. That uncertainty can create tension, but it can also create frustration when the result of an action feels impossible to judge.
For Everlasting Odyssey, we want players to spend their attention on the plan itself. Which target matters most? Is this the right time to spend action points? Does moving first create a better sequence? The battle forecast is meant to support those questions before the player commits.
Iterating on the combat interface
The screenshots for this update show three stages of the interface. The first pass helped us identify where important combat information needed more attention. The next pass cleaned up the battlefield presentation and turn controls. The latest version adds a forecast panel that appears while an action and target are being considered.
The goal is not to predict every consequence. It is to present enough information for the player to understand the immediate result and make an intentional choice.
Why this matters in an action point system
Everlasting Odyssey uses action points, so a character may perform more than one action during a turn. That makes sequencing important. A player might move, use one skill, reposition, and spend the remaining points on another action.
When several actions can be combined, an unclear result early in the sequence can undermine the rest of the plan. A forecast gives the player a moment to compare the selected action with the resources it consumes and the result it is expected to produce.
This becomes especially useful when positioning, status effects, and battlefield hazards interact. The player should be thinking about the tradeoff, not trying to decode the interface.
Clarity without covering the battlefield
There is always a risk of showing too much. Tactical games can fill the screen with values, icons, ranges, and probabilities until the battlefield becomes harder to read than the decision itself.
Our current direction is to keep detailed information available when the player asks for it. The forecast belongs to the moment of target selection. Outside that moment, the battlefield should have room to breathe.
The exact information shown in the panel may continue to change as combat systems develop and we watch players use it. The important part is the role it serves. It should reduce avoidable guessing without solving the tactical problem for the player.
What we are validating next
The next step is testing whether players can read the forecast quickly and whether it gives them enough confidence to act. We also need to watch for information that looks useful in a design document but becomes noise during an actual turn.
That feedback will help us decide what belongs in the default forecast and what should remain available through deeper inspection.
