![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
working on the hell game codeeeee
i've been kinda messing around with encounters and seeing about making some more actiony, event-driven ones, or ones with more moving parts. all the currently-existing encounters are just... sex scenes, which means they're big, static branching trees of scenes; very self-contained and without many moving parts. and THEORETICALLY the event code can do a bunch more, it's just i've never really used it to do more, or really even seriously considered what that 'more' would be shaped like.
one of the things i've been thinking about doing for aaages, though, is locations. stuff with multiple npcs or stuff with randomized npcs. the machine shop is planned to be that, for example -- to make all of the characters mentioned there actually population-backed, with distinct names and variants, etc. so it's been something i've been considering since the beginning. except at the beginning, i didn't actually have the ability to store encounter data in any meaningful way: either an encounter was raw monster data, or it wasn't, and there was no way to go "okay this machine shop has these machine-shop variants and also this separate flame demon npc with these variants". (this is also why a dryad becomes unvisitable once moved to a farm; the actual dryad variant data couldn't be copied over and was just erased.)
so anyway long story short, i had this vague concept of what it would look like in the code to store sub-events inside events, but it was never more than a vague concept. and today i went and tried actually fleshing it out, and... it required a different approach and for me to write some new general-purpose event data management functions, but it was pretty much all already there. i'm gonna need to restructure a lot of events to basically provide extra access points for other events that might want to include them, but the first location that stores random other npcs is in the game and mostly working. progress!!
i've been kinda messing around with encounters and seeing about making some more actiony, event-driven ones, or ones with more moving parts. all the currently-existing encounters are just... sex scenes, which means they're big, static branching trees of scenes; very self-contained and without many moving parts. and THEORETICALLY the event code can do a bunch more, it's just i've never really used it to do more, or really even seriously considered what that 'more' would be shaped like.
one of the things i've been thinking about doing for aaages, though, is locations. stuff with multiple npcs or stuff with randomized npcs. the machine shop is planned to be that, for example -- to make all of the characters mentioned there actually population-backed, with distinct names and variants, etc. so it's been something i've been considering since the beginning. except at the beginning, i didn't actually have the ability to store encounter data in any meaningful way: either an encounter was raw monster data, or it wasn't, and there was no way to go "okay this machine shop has these machine-shop variants and also this separate flame demon npc with these variants". (this is also why a dryad becomes unvisitable once moved to a farm; the actual dryad variant data couldn't be copied over and was just erased.)
so anyway long story short, i had this vague concept of what it would look like in the code to store sub-events inside events, but it was never more than a vague concept. and today i went and tried actually fleshing it out, and... it required a different approach and for me to write some new general-purpose event data management functions, but it was pretty much all already there. i'm gonna need to restructure a lot of events to basically provide extra access points for other events that might want to include them, but the first location that stores random other npcs is in the game and mostly working. progress!!
