Hi guys,
I have this problem :
Every condition line can perform no more than 127 actions.
So if I try to add a 128th action, MMF says that I can't do it since the maximum number of action per condition is 127.
I discovered that if I copy/paste some action, I can go over the limit and have an higher number of actions.
The question is :
Is it fine or is it a problem?
Having more than 127 action could result in some sort of bug or lag or something bad?
Thank you in advance
Func loop?
If something... then
your actions and at end run function "asdf"
On function "asdf" then
others actions
Didnt you post this question on The Daily Click? I am sure you got your answers there.
I would assume that there was a reason for the limit and going over it is a bad idea. It could cause the extra events to be ignored, or it could crash in interesting ways.
I can't think that it'll cause the file to go bad so you might as well try it out as long as you don't go way, way over the limit.
If not loops as suggested another idea would be to set a value and then have a event after the main one. So on the second you compare to see if it was triggered and then run the next set of actions and in the next set turn off the first sets value and keep adding these triggers/switches as needed. It might not work though depending on what your doing though, but similar to loops i guess as another possible workaround.
Half of the answers I got on TDC were not useful because they tought I was speaking of condition limits, while I was speaking of actions limit.Originally Posted by bigredron
The other half of the answers I got was : "sorry, I don't know".
Then I got a last answer that said : "Try to ask on the clickteam forum".
So here I am
By the way, thank you for all your answers.
I agree that if there is a limit, there must be a reason.
I just don't see the reason, but I think it will be better to avoid to overload the condition with more than 127 actions.
Thank all of you for your help
If you need more than 127 actions, it's bad design. Simple as that.
Actually, I used to have an event that was close to 120 actions. Reason: I needed to "reset" my active objects. Those objects used a lot of alterable values and I had several of them (not clones, but all different objects). I couldn't do a loop, because the initial values were not all 0. And destroying/creating was also not an option, because that would make active objects flash.
I ought to request a "reset active object" feature sometime. So it's not bad design per se, just a lack of features from MMF
You could do them in separate events within a group, eg with On Group Activation events, and have the trigger activate the group and the last event in the group deactivate itself.
The best way would be fastloops
Posting Permissions
Reply With Quote