#saturngame

[saturnalmoss]

QUESTS

When setting up story and quest progression, I've got two goals:

I want the characters you interact often with to have something to say about what you've been up to.

I want to have small quests that you do gathering information for NPCs.

To support these goals, I made a general side quest structure we can use to track for individual NPCs. For the updates, we track the general flow of the story. Right now, I'm trying out a granularity of major and minor arcs.

When you trigger the dialogue with an NPC, we can go through their quest, see where we are at with them, and allow the appropriate response. We start the quest at UNSTARTED, then depending on our interactions, we can set it however it progresses, and also reference it with other NPCs.

Here, our hunter wants immediate information. We can tell him the right answer, and later get an additional reward, or the wrong answer where the poor guy just keeps looking.

We can talk to another NPC who would see the PENDING status, and tell us, hey, some hunters gave us meat! And discreetly set the quest to success so that our hunter moves on to the final state.

[saturnalmoss]

I've been setting up rooms and the contents of the rooms. I made a reusable scene Door to help with the transportation. It takes the scene and optional coordinates. Position Locked here means to keep the player scene where initially created. Either your player would already be in the right spot (one exit rooms) or you need to tell the door were to put you (say, a town map with many houses to visit).

I want the maps to feel lived in and populated so I keep making interactions on the objects and making plenty of NPCs. Slow Going.

[saturnalmoss]

I've put in the very first of our "tools". Eavesdropping! This requires you to be empty-handed.

You can try to spy on anyone you can talk to (and other places) and the action will take advantage of the already existing configuration for talking to the npc to attempt to find an eavesdropping line. :)

I also fixed it blowing up if you talk to someone with nothing to say whopps.

[saturnalmoss]

Folks we're struggling to add a video...

Imagine the fellow on the path pacing back and forth. The others are wiggling in place.

I've set up two types of NPC blanks, they have a place for collision but one also has a place to add the dialogue reference. Then, I have three different NPC movement AI script; one which wiggles in place, one that moves between a given list of markers, and one that wanders aimlessly.

[saturnalmoss]

More gameposting!!!

I'm using a godot plugin for dialogue from Nathan Hoad, which is really easy to use. Since I was coming from an rpgmmv game, I have been wanting to put interactions on everything.

The game itself has a strong element of information gathering, so it's important to check around and talk to people.

[saturnalmoss]

I'm making a lil lozlike game in godot! Learning once again since I switched to Linux and it personally shot my copy of RPGMaker MV.

I'm using a beautiful set of assets from pixel boy on itch, until i feel like drawing lil guys.

[saturnalmoss]

[saturnalmoss]

Neon kung-fu voyage design thought doc

Play a little guy who kicks and jumps with the exact same flying high kick in a side scrolling runner through cyber retro locations.

Example of Play

Player will start the game. Potentially, the player will select the level. The pc will start at the left side of the screen and begin running on any key press. The pc will run right, centered in the viewport, until they die or reach the end of the level. The player hits a key to jump. If the pc collides with an enemy while jumping (or falling), the enemy is destroyed. If the player collides with an obstacle, jumping or not, the pc dies. When the height of a level changes, the wall is considered an obstacle and the pc dies if they player hits it instead of jumping to the new height. The pc dies if they fall into a pit.

When the pc dies, the player has a chance to start the level over or to return to game screen.

When the pc reaches the end of a level, the player is rewarded visually then placed at the beginning of the next level. The pc waits for the first key press before running.

Level Settings

Levels will be similar to a 2D platformer, with a mixture of enemies, obstacles, pitfalls, and changes in grade. Enemies will start with a simple pattern to move towards the level start. Later levels will have more complex movement, pacing, reverse on collision, jumping, and projectiles.

Locations will be old fashioned transportation: River boats, blimps, hot air balloons, trains, ocean liners. Things that lend the sense of voyage.

Aesthetically, neon colors. Bright things. Each level should have a distinct pallette, with the pc changing color each level as though lit by it. While the shape of the terrain should be recognizable as the anachronistic transport, the color should put the player in mind of vaporwave, 90's, and cyberpunk. The obstacles will likely be objects associated with the location. The enemies should make no sense - concept or locality - and be cool 😎. The style of art should be reminiscent of 8bit, as discussed, even if i would like it to imitate Jacob Drawfee's style.

The contender for game system is PICOtron. It is a good choice for the retro console style, and allows for pallette swapping. Further discussion needed of the limitations of PICOtron to see it interferes with above stated goals.