Timed Text

The simplest way? Use the timer (the stopwatch)

have your object start as invisible then add the events

When (player sprite) is overlapping (your trigger object)-
-reset timer
-start timer
-set (text) to visible

timer reaches 00:00:10:00
-Set (text) to invisible

That's the EASIEST way to do it. you may experience problems if you do this with more than one triggered block of text

Ted's method will work however it won't use "game time" If your game lags, or doesn't run atthe fps set at all times for all computers, then the message may not function correctly.

Glad ya got. that happens to me all the time. I post a question then 5 minutes later I figure it out,..LOL Oh and it's no bother. That's what the sites here for! You can do this another way without using the timer. Here's an example. You can adjust the amount of time that the object stays visible. On line # 8 in the event editor, adjust the 200 lower or higher to taste. I don't know what you're using this for, but for a better effect, look at the next frame in the example.

Please login to see this link.

If you truly want a way for it to work on laggy systems, you going to need to do something like this;

• [Conditions to activate the event]
  
  
  • turn flag 0 on
• Flag 0 is on
  
  
  • Add 1 to AV 1
• IF AV is greater than or equal to [Game FPS * 10]
  
  
  • Turn flag 0 off
• Flag 0 is off
  
  
  • Fade text away.

This calibrates the system to use the fps as a timer.

Quote from ProdigyX

If you truly want a way for it to work on laggy systems, you going to need to do something like this;

• [Conditions to activate the event]
  
  
  • turn flag 0 on
• Flag 0 is on
  
  
  • Add 1 to AV 1
• IF AV is greater than or equal to [Game FPS * 10]
  
  
  • Turn flag 0 off
• Flag 0 is off
  
  
  • Fade text away.

This calibrates the system to use the fps as a timer.

Display More

This sounds interesting and something that I have personally never heard of before. Would you provide more information and an example using the FPS as a timer. I am having a hard time getting my head around this and I think your example would be great for my website for everyone to see and use.

Thanks,

Marv

Maybe you have heard of it before and just don't recognize it.
Essentially there are two types of time in an app; Game Time and Real Time. In most cases, Game Time and Real Time are so close to each other (like within milliseconds) that one wouldn't ever need to worry about the difference. However, there are always those "What If" scenarios where anything could happen. A what if scenario for this situation would be "What would happen if I tell mmf2 to make something visible for 3 REAL TIME seconds?" Well if your app, cause any kind of lag, then the player might not see the visible item for the entire 3 seconds. The game could lag just before it happens and catch up just after the 3 seconds is over and the player would never see the invisible item [imagine if there were instructions]. Typically whenever you want to do an actual time based event, you want the time to be in GAME TIME. With GAME TIME, if the app/game lags, then the time will lag with it. Real Time is unaffected by any kind of lag while Game Time is.
Please login to see this attachment.

How about that. Very interesting and I didn't know about, real time and game time. Thanks for posting this.

Thanks ProdigyX.

Marv

PS: you can retrieve the game's FPS by using FrameRate.

Thanks ProdigyX