I recommend using a different tone of wood for all the furniture in the Hub, perhaps a light yellowish shade, to create a contrast with the red walls, red floor, and the character's blue clothes.
Amazing explanation of the different systems. Regarding world, Do you have a pipeline with "in" properties or it's more like a graph and any property affects any other property with its own propagation rules? Additionally, how are the quest description (text) from the world properties? Maybe... I'm asking too much! Keep the good work!
There's a world state object that contains everything important for the simulation and there's a pipeline of functions that gets run after each mission, where each function gets passed the world state, performs whatever transformation it likes and then passes the new state to the next function in the chain. Each function has a particular aspect of the world that it's responsible for updating. In the narrative system, storyblocks specify world state requirements needed in order to be considered for selection. Text is generated by having a bunch of string templates where specifics can be substituted and then those templates can be combined, i.e. "Please save {SUBJECT}!" That happens during the storyblocks -> procgen config rendering part. I made it look simple in the video, but in reality the procgen config ends up large and complicated, containing all the conversation trees and everything important that can happen in an environment. Sorry for the wall of text!
@@TechronomiconDev impressive answer! Thanks! Then functions/results are order dependant or the order is also dynamic? Ok, I'm just curious, I understand it's your secret sauce. Don't feel obligated to answer ☺️
Thanks for watching! If you have any thoughts or questions leave a comment
I recommend using a different tone of wood for all the furniture in the Hub, perhaps a light yellowish shade, to create a contrast with the red walls, red floor, and the character's blue clothes.
You got a sub singlehandedly for excluding escorts.
The environment of the game looks nice.
Love all the world simulation stuff. Feel like i could watch these little systems go for ages...
Sounds interesting. I'd love to hear more about how you implement your narrative generation system.
Amazing explanation of the different systems. Regarding world, Do you have a pipeline with "in" properties or it's more like a graph and any property affects any other property with its own propagation rules? Additionally, how are the quest description (text) from the world properties?
Maybe... I'm asking too much!
Keep the good work!
There's a world state object that contains everything important for the simulation and there's a pipeline of functions that gets run after each mission, where each function gets passed the world state, performs whatever transformation it likes and then passes the new state to the next function in the chain. Each function has a particular aspect of the world that it's responsible for updating.
In the narrative system, storyblocks specify world state requirements needed in order to be considered for selection. Text is generated by having a bunch of string templates where specifics can be substituted and then those templates can be combined, i.e. "Please save {SUBJECT}!" That happens during the storyblocks -> procgen config rendering part. I made it look simple in the video, but in reality the procgen config ends up large and complicated, containing all the conversation trees and everything important that can happen in an environment.
Sorry for the wall of text!
@@TechronomiconDev impressive answer! Thanks!
Then functions/results are order dependant or the order is also dynamic? Ok, I'm just curious, I understand it's your secret sauce. Don't feel obligated to answer ☺️
The game graphics look really good