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 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?
I wouldn't rule out program crashes or some actions being ignored. It might be a better idea to split them into multiple conditions (for example have one of your actions being setting a flag on, then check the next line if the flag is on)
Also, why would you need more than 127 actions in one condition?
Originally Posted by AndyUK Ive never known any condition to even come close to 127. Are you using lots of Ors or something?
He's talking actions, not conditions
Still, seems excessive. as suggested above, spread it over multiple conditions, dont wanna risk breaking it, or perhaps consider another way of doing what you're trying to do, cos it sounds awfully inefficient.
I always have a object specifically for this case. I switch on a flag and right after the condition where I need more actions have a check to see if this flag is on. It runs the extra actions and switches it off.
You can use this same flag for all the instances where this occurs with no interference because it is checked after every condition that uses it.
The less conditions you have to perform one task the more actions you have to use to make up for it.
Thank you for the answers guys
I can handle the problem... I was just curious to know if having more than 127 actions in only 1 condition would cause problems or not.
I'd suggest splitting an event after like 30 actions or so, otherwise it becomes impossible to read in the event list
Edited by Muz
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
I am assuming the reason that there's a fixed amount of actions is because there's a fixed size array associated with the actions somewhere. If you define more than 127 actions they could simply be ignored, or maybe placed in a part of memory that it shouldn't be placed, even though it might not always cause problems. This is probably one to ask at the CT forums.
I think its more to do with how much they can fit into a byte? Got no idea.
But I couldnt imagine using that many actions in 1 events. I would just split up into smaller chunks for the sake of your sanity.
Originally Posted by bigredron I think its more to do with how much they can fit into a byte? Got no idea.
But I couldnt imagine using that many actions in 1 events. I would just split up into smaller chunks for the sake of your sanity.
It's not like all the events in my game are associated to more than 127 actions each
I just have one single event in all the game that is related to more than 127 actions
As I said, that's a problem I can easily manage but since I didn't find any problems to go over the limit, I was just curious to know why I didn't get any errors
The reason you didn't get any errors is probably coz it's a bug. I don't think you can easily read it when it's at 30 actions, much less if it's at 127, so it's just one of those bugs that would get written off as "psychotic user behavior" if any testers ever saw it
Disclaimer: Any sarcasm in my posts will not be mentioned as that would ruin the purpose. It is assumed that the reader is intelligent enough to tell the difference between what is sarcasm and what is not.
Advertisement
Post Reply
Edited by X_Sheep
