Skip to content

Conversation

@manuq
Copy link
Collaborator

@manuq manuq commented Oct 28, 2025

So the magical thread is not occluded by the dialogue. And to give it
more narrative sense:

  • From the Void runner level, there is an ellipsis.

  • The StoryWeaver is about to grab a magical thread and be teleported.

  • But the Void ruins their plans. Has to take an alternative path.

  • At the end of the level, the StoryWeaver comes from the other
    direction.

Also add a dialogue at the start of the Void + grappling level.

Helps #1410

@github-actions
Copy link

Play this branch at https://play.threadbare.game/branches/endlessm/more-void-narrative.

(This launches the game from the start, not directly at the change(s) in this pull request.)

@manuq manuq force-pushed the more-void-narrative branch from bbda3f9 to ba42f46 Compare October 29, 2025 01:05
@wjt
Copy link
Member

wjt commented Oct 29, 2025

image

Is this pin-in-the-void intentional?

@wjt
Copy link
Member

wjt commented Oct 29, 2025

That's in the start level. Here's the "same" thing in the "end" level:

image

.oO( can we make these actually be the same scene, by storing some state in GameState? one for another day perhaps )

So I think you meant to move that pin up a little? Or is the enemy eating one tile too many perhaps?

@manuq manuq force-pushed the more-void-narrative branch from ba42f46 to 98c5ebf Compare October 29, 2025 10:47
@manuq
Copy link
Collaborator Author

manuq commented Oct 29, 2025

@wjt thanks for spotting the difference! That island was 1 row taller. It is indeed hard to keep these 2 scenes in sync. The "only" game state needed would be the grappling hook "has more string" and I had that in my prototype. But I think we agreed to leave that out for now to avoid adding more state.

@manuq manuq force-pushed the more-void-narrative branch from 98c5ebf to 84e9b36 Compare October 29, 2025 15:24
@manuq manuq marked this pull request as ready for review October 29, 2025 15:25
@manuq manuq requested a review from a team as a code owner October 29, 2025 15:25
@manuq
Copy link
Collaborator Author

manuq commented Oct 29, 2025

@wjt I think after this the remaining narrative is the outro. I will add a separate scene for it, like in the first lore quest, all cinematic. It will show the town and people from the town celebrating and thanking the StoryWeaver.

@wjt wjt requested a review from a team October 29, 2025 15:35
Copy link
Contributor

@Gatorrante Gatorrante left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I love the story added in the levels after the first one — the new dialogues really give meaning to the lore being built. The cinematic that interrupts the second level is fantastic! I haven’t found many issues, but I did notice that if you go from Level 2 - Scene 2 back to Level 2 - Scene 1, the cinematic plays again.
image

@manuq
Copy link
Collaborator Author

manuq commented Oct 31, 2025

I love the story added in the levels after the first one — the new dialogues really give meaning to the lore being built. The cinematic that interrupts the second level is fantastic!

Thanks for testing it!

I haven’t found many issues, but I did notice that if you go from Level 2 - Scene 2 back to Level 2

Yes, I noticed it too, I'm thinking how to fix it. Thanks!

manuq added 4 commits October 31, 2025 16:48
So the magical thread is not occluded by the dialogue. And to give it
more narrative sense:

- From the Void runner level, there is an ellipsis.

- The StoryWeaver is about to grab a magical thread and be teleported.

- But the Void ruins their plans. Has to take an alternative path.

- At the end of the level, the StoryWeaver comes from the other
  direction.

Add a spawn point to the end sublevel and use it from the previous
(the powerup) sublevel just to use its "look at side on spawn" property.

Helps #1410
Use a new animation and call it from the cinematic dialogue.
Telling the player what to do (reach the town). The level is still
placeholder.
By running the update_tilesets.gd script
@manuq manuq force-pushed the more-void-narrative branch from 84e9b36 to dde4077 Compare October 31, 2025 19:51
@manuq
Copy link
Collaborator Author

manuq commented Oct 31, 2025

I merged with main which had the updated tilesets, picked the scenes from this PR and then ran the amazing update_tilesets.gd script again. Then committed it. Since the commit splits is not good and I won't redo the work, I'll use squash & merge in this case.

@manuq manuq merged commit a7bcacf into main Oct 31, 2025
6 of 8 checks passed
@manuq manuq deleted the more-void-narrative branch October 31, 2025 19:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants