metaheavens/spaceship
Watch
1
0
Fork
You've already forked spaceship
 0
Code Issues 4 Pull requests Projects 1 Releases Packages Wiki Activity

#129 (#131, #132, #133): a quest chain, and a World Ship out of reach

Browse source 
Sixteen quests that walk a new game through the things it contains: ore,
the mothership, exploration, a yard and a second hull, planetfall and
conquest, extractors, gas, freight, power, the lab, a new vessel type, an
outpost, and a survey.

The chain turns on the second quest. The fleet builds the mothership to
call the World Ship and hears nothing - and the array is not at fault. The
breach put them further out than that signal will carry, so every quest
after it is a search that has to be flown rather than transmitted.

Three pieces:

  Quests.gd  the chain, as data and nothing else. Two rules it obeys:
             nothing may ask for something unreachable - research points
             come only from conquering a planet, so every doctrine that
             costs them sits after the conquest quest - and a quest names
             one goal, with the research it implies said in the brief
             rather than split into an errand of its own.
  GameState  how far along the chain the player is, and the answer to each
             goal kind. Progress latches for free: the chain is walked one
             quest at a time, so collecting five ore and spending it cannot
             un-complete the quest that asked for five - by then nothing is
             asking. It lives here so a quest finished on a planet surface
             is still finished after take-off.
  the HUD    QuestTracker, the standing objective, in the wave alert's
             idiom; QuestDirector, which reads the lines out.

Lines are QUEUED by GameState and drained by the director rather than
emitted at a banner, because quests advance in the autoload, which runs on
a planet surface too - where a line emitted straight at a banner would be
lost. Both scenes now carry a banner, a tracker and a director, so a quest
finished underground is announced underground.

The chain is armed by reset_new_game(), the same gate the prologue uses -
the only door into a real game - so instantiating a scene is not by itself
a reason to start briefing somebody.
This commit is contained in:
Loïc Wisniewski 2026-08-28 14:41:03 +02:00
commit 397983b611
13 changed files with 917 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
tests/test_fleet_growth.gd
View file

@ -34,8 +34,10 @@ func _initialize() -> void:
# #108: reset_new_game() arms the prologue, and the prologue opens with a
# convoy rather than the game's own starting fleet. This test is about
# what the GAME starts from, which is where the prologue hands over -
# see test_intro_scene.gd for the prologue itself.
# see test_intro_scene.gd for the prologue itself. The quest chain goes
# with it: its briefings are dialogs, and a dialog stops the tree (#128).
game_state.intro_active = false
game_state.reset_quests()
func _process(delta: float) -> bool:
@ -102,8 +104,10 @@ func _process(delta: float) -> bool:
# --- B. what actually flies ----------------------------------
game_state.reset_new_game()
# ... and again here: this is the reset the scene below is built
# from, so the prologue has to be off for THIS one too.
# from, so the prologue has to be off for THIS one too - and the
# quest chain with it.
game_state.intro_active = false
game_state.reset_quests()
scene = load("res://world/Main.tscn").instantiate()
root.add_child(scene)
fleet = scene.get_node("Fleet")