Restrict Action Bug?

[FlyingDeath]

I am having a serious problem with the restrict action function(and maybe other time based functions), in so much as they seem to be ignored after enough time has passed. To be clearer, I would, for example, have a trigger that says "if you are holding the fire button+restrict action for 1 second" then create a projectile. The problem is after a time(usually quite a long time), the restrict action is ignored so that a projectile will be fired every frame. Also I have suddenly noticed that since an update, certain instances of the restrict action are ignored at all times. Is this a problem other people are facing, or am I doing something wrong. Any help would be, well, a real help! p.s. I have searched the forums for this problem, but if this is a repeat, sorry.

[Francois]

Yes it is true. To restrict the action, I have to use an internal counter inside the event. Back in the tgf time, I stupidely chose a two byte value for this counter. So after 21 minutes or so (or 10 minutes cant remember), it starts again.
I cannot change the format of the events now, it will have to be done for MMF3.
So I am sorry, but there is nothing I can do.
The only solution is for you to program the restrict action manually using a counter.

[Dynasoft]

Couldn't you reset that internal counter when the restrict condition runs out? So it would reset every second and there would be no problem?

If that won't work and it's a problem with wrapping round the counter I know how to fix that too.

[FlyingDeath]

Thanks for the response. It's probably for the best that I start using a custom restrict action by counting frames instead of counting real time anyway(I kind of prefer slowdown to drops in frame rate as it is).