TalkToAndListenToStory problem

[blancharke]

TalkToAndListenToStory.cs doesnt seem to work for me

log keeps spamming

[FONT=Arial]c:\Users\Tom\Desktop\Honorbuddy\Bot\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0122: s is vanwege het beveiligingsniveau niet toegankelijk[/FONT]
[FONT=Arial]c:\Users\Tom\Desktop\Honorbuddy\Bot\Quest Behaviors\TalkToAndListenToStory.cs(32,92) : error CS0118: s is een type maar wordt gebruikt als een variabele[/FONT]

anyone being able to quickfix this or tell me what to do?
thx

 

[nlr]

I would like to know this as well, please let us know a work around.

Regards,
Nick.

 

[Liferose]

Its not your code in the profile its the custombehavior itself so it just needs to be fixed. Would also like to see it

 

[Fetterlein]

Support. Fix required ;o) we're stuck on the quest profiles.

 

[daystar]

Changing line 32 from

                    Logging.Write("Unable to parse {0} as an integer! check your profile", s);

to

                    Logging.Write("Unable to parse {0} as an integer! check your profile");

Fixes that error. It also spits out the error written there, as it isn't parsing the NPC ID correctly. To make it do that you must change line 29

                if (uint.TryParse(o, out id))

to

                if (uint.TryParse((string)args["NpcId"], out id))

Then it will successfully talk to the NPC, but only the first option. And I'm not sure it could do it more than once for multiple parts of the story. If the person you are talking to has a single quest to give you, the dialog option that you may need moves from dialog button 1 to dialog button 3. I wouldn't know how to code it specifically, but it should be possible to add an argument for which dialog option to choose and have the code parse that into which it processes? <If> tags can then be used to indicate which needs to be chosen based on how the options change when someone's on a quest or not.