Making conversations between NPCs global events?

[Krim]

need them to be global so that they can change with events, even when its not on the same frame.

I have it right now so its

(Globals are set in another frame)

"Object not moving"
"Overlapping CPU"
"Upon hitting up"
"Event(global)=1
>Display paragraph 1

and then I have another one that is

"Object not moving"
"Overlapping CPU"
"Upon hitting up"
"Event(global)=2
>Display paragraph 2

But that doesn't work(I assume for obvious reasons)

My problem is I can't figure out what code to use to make conversations different based on the global number. SO yep thats my question, how do I make conversation different based on a global value?

[Olivier]

"Upon hitting up" should come first in the condition. That's true for every 'true events' as opposed to 'fake events'. True events are displayed in red when positioned a the top of a condition.

You can learn more about true/fake events here:
http://www.clickteam.com/eng/resources/GTM/GTM2_4.htm

EDIT: Acccording to the link above, "User presses a key" is not a true event.[crazy]

[Krim]

So its not true???? What??? How do I make it a true event??

[Joshtek]

So its not true???? What??? How do I make it a true event??

You don't. It isn't a true event.

[Anders]

MMF2 events are actually of two different types. The "true" events are events that is taken out of the normal event cycle and only evaluated/fired when the event actually occurs. Those events are for example: Fast loops, collisions, keyboard and mouse input.

Those conditions "on loop" and "uppon key pressed" and "on collision" has to be the very first condition in the event so they are seen as true events.

In the latest MMF2 versions you can see the difference between true and non-true conditions by the color of their text.
All true conditions has red text and should always be on top in the event.

[Joshtek]

On loop is a true event.
Object collisions are true events.
Upon pressing any key is a true event.
Upon pressing a specific key is not a true event. While this is counter-intuitive, it is to do with how MMF2 works with Windows. The only way to make it a true event is to put the "upon pressing any key" first followed by upon pressing a specific key.

http://www.clickteam.com/epicenter/ubbthreads.php?ubb=showflat&Board=2&Number=20338#P ost20338

No, as strage as it seems, Upon pressing a key is not a true event...