From the development notebook. These entries discuss story details and describe the game at the time of writing.
October 22, 2026: Gabby changes the battle
I do not want to lose Gabby's part in the first fight. She brings a Gorgon onto
her side, and that character, Golgotha, becomes important to Jack later. If the
game only asks the others to rescue her, it misses what she contributes herself.
The manuscript review confirms the eye contact, her command to help Haley and
the Gorgon's return with her. The later books develop the alliance into Jack's
partnership with Golgotha. I want the game to preserve that progression. Being
under Gabby's charm and choosing to stand beside Jack are different stages of
the relationship, and both matter.
The required encounter revision is now recorded with source references. The
current build still uses the rooftop rescue. That needs to change before I
consider this the story's first battle; the trampoline can become academy
training without taking Gabby's moment away from her.
October 22, 2026: Give me a reason to try again
I want another layer of polish, but Braden's opening keeps me honest about what
that means. The player should have something interesting to choose and a reason
to try another approach. This pass lets me choose a team plan instead of leaving
every call to context. The shield, ice combination and launched distraction
should each feel like a useful answer to the situation.
The academy now has a small movement course. I like the idea of finding my own
line, making the jump and seeing whether I can improve my time. It is optional;
I do not want a stopwatch standing between a player and the story. A quick retry
and a saved personal best give the experiment somewhere to go.
I also want to read the action at a glance: where a strike will land, which cousin
needs me and when Gabby's ally changes our fortunes. The new feedback gives us
more to work with. I still need to judge the fun through play; passing checks
and adding features are not the same as making something I want to replay.
October 22, 2026: Give the family a world and a reason
The characters have moved ahead of the scenery. I want the world around them to
feel like somewhere they belong, with a market they can cross and an academy
they can recognize from a distance. This pass uses the tower assets I supplied
and adds more detailed stalls, trees, benches and grounded terrain around them.
I also want the player to understand why the next action matters. "Explore the
courtyard" does not carry the same weight as getting Gabby down safely. The
Gorgons are under Sarlak's influence, and freeing them should feel different
from simply clearing enemies out of the way. The family is trying to get through
this together.
Danny's training needs that same clarity. The relay powers the training path;
Jack makes the channel safe; Haley learns to reach the terrace while protected.
These are game adaptations, and I want their purpose to fit Discovery even
while we continue developing the full story. I still need to judge the result
by playing it. More detailed scenery and better instructions support the fun;
they do not replace it.
October 22, 2026: Let Braden hold us to it
I asked for Braden's opening in Discovery to guide the game design. He sees the
pattern, repeats the solution, and eventually gets a pile of enemies that asks
him to mash faster. He knows that is not the kind of challenge he wants. I do
not want to build the same thing around the characters who criticize it.
The rewritten encounter gives the powers a purpose: make enough room to bring
a cousin through. I can guide either group first and choose how to create the
opening. Gabby then changes the battle herself. Her Gorgon returns with her,
helps the family and leaves alive. That preserves the beginning of a relationship
that will matter to Jack later.
The trampoline belongs in training, where the player can try the gentle route
or chase the optional sparks without treating Gabby as a prop to rescue again.
I want the retry to feel inviting. These changes give us a more useful structure
to test, but I still need to judge the fun by playing it, not by counting checks
or looking at a polished screenshot.