Story name % V1 = Initialization Counter % S101 = Load new episode when S101 = 1 % S102 = # PC Wins % S103 = Difficulcy Level, load ending when S103>75 % S104 = # Wins when level last increased % S105 = Location Clue % The first START, force a conversation with Hyolee. Start GoSetOps .intro Msg1 Msg2 Msg3 GoCheckClue GoNoClue Msg5 Element1 Element2 Element3 Stat 3 10 XREnemy 0 XRMystery 2 XRBadThing 2 hour GoLoadEpisode GoCheckHint .xplot .xend .xhint inv NPC Mecha Pilot mecha EquipChar 50000 Plot 0 % Note that I am hotloading this plot- DO NOT % DO THIS YOURSELF!!! I can get away with it because % I'm the programmer. Note that because this plot is % getting sneaked into the adventure riding under a % story gear, it will not be initialized by the % MATCH_PLOT_TO_ADVENTURE procedure. In this case % it shouldn't matter because the story is loaded at % the game's setup, and all the elements are starting % initialized. However, in general, I think this is % very bad form... name start GoDelete % Element 1 is Hyolee. Element1 Stat 1 1 % Element 2 is Megi. Element2 Stat 2 17 sub Persona 1 % Hyolee will greet the PC and tell him to go % speak with Megi. greeting result1 result2 result3 result4 result5 Msg1 Msg2 Msg3 Msg4 Msg5 Msg6 Prompt1 Prompt2 Prompt3 Prompt4 Prompt5 GoBeenBefore result101 result102 Msg101 Msg102 Msg103 Prompt101 Prompt102 Persona 2 % Megi will speak with the PC and then allow % conversation branches to load the various job % plots, or the tutorial plot. greeting result1 result2 result3 result4 .JobStory .CrimeStory .Tutorial Msg1 Msg2 Msg3 Msg4 Msg5 Msg6 Prompt1 Prompt2 Prompt3 Prompt4 GoFirstTime result101 result102 result103 result104 result105 result106 Msg101 Msg102 Msg103 Msg104 Msg105 Msg106 Msg107 Prompt101 Prompt102 Prompt103 Prompt104 Prompt105 Prompt106 end end