/jp/ - Otaku Culture

>>15940923

For context, here's a dialogue file. If you're at a node that links to this, it'll run requirements (which is optional - for here it's redundant to say allow scenario since that's the default, but I put it there to demonstrate), and if the block evaluates to allowing, it'll let the link show up. If you select "Do you want some candy, little girl?" it'll run this file and look at the attributes tag of the two outcomes here. Whichever matches the loli's attributes better (the * 3 means give 3 times the priority to this attribute vs the other attributes being matches - not useful here since only 1 attribute is being matched though., and the 0-5 means anything between those ranges is matched 100%, whereas the = 20 means only 20 is matched 100%.) and whichever matches better will be chosen, and the message block will get run, which decides what the loli says (multiple outcomeMessage calls are how you can get a sequence of messages without any choice). And the result block gets run for the message that gets chosen. Then once the messages are done being displayed, it runs links, and all the links run there will be where the conversation branches from.

Should I do something like this for the inter-loli dialogue? Basically the same, except I'd have to give the overall file its own attributes block since there is no player to make choices and I'd have to make the the choices via the NPC's attributes.


Although maybe this will be a bit much? I imagine most conversations between NPCs might (initially?) be quite simple, so maybe I should make a simpler system? Although it'd be a bit annoying to see the exact same conversations play out every single time... but I guess I could break out all the non-branching choices in the NPC-NPC dialogue into a single file where you could be like...

message(npc1, "Hey, " + name(npc1))
message(npc2, "Hey!")
message(npc2, "How are you doing, + name(npc1))