A Freezing Trigger Doesn't Do All Its Actions

[I34w90_238j]

I'm creating and filling in a large multiboard, and that trigger is very large too. The problem is that it does only about one quarter out of all of its functions and does no more. The trigger proved not to work in any other maps, where I paste it in.

While doing diagnostics I managed to put text functions between most of the trigger's actions, to check how many text messages Warcraft will display in total. Here's the result: of all the numbers, Warcraft shown 1, 2, 3, 4, 5, 6, 7, 8 and 9. After I removed action "Multiboard - Set the display style for Multiboard in column 0, row 0 to Hide Text and Hide Icons" Warcraft displayed 2 more numbers during testing: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 and 11.

Could someone please either fix the trigger or tell a solution or at least help with what to do next in diagnostics.
I upload the map too, in case if you don't want to make the whole trigger on your own.

 

[ap0calypse]

Well, as a starter I would advice you to post the trigger here on the hive.

Write: [ hidden=Trigger][ trigger] (without the spaces)
Now go to your trigger and select the name (above "Events"), right click and select "Copy as Text".
Paste it after what you just wrote (those tags) and then write [/hidden][/trigger]

(and instead of all those Integer A's and B's, I would advice for each integer Variable - Do multiple Actions, but I guess it's too late for that and it won't really matter).

Could you send one of the maps you pasted it in to me?
I'd like to test some things for myself, I think it's easier then when I have to tell you things the entire time :/

 

[I34w90_238j]

I have attached the map to my first post. It can be opened with World Editor Unlimited, but I can make a map with that multiboard which can be opened with ordinary WE.
And I attached to my post also a large picture - screenshot of the trigger, because the trigger is so long that it's hard to write it in

• tag as text.
• The multiboard I'm making is an inventory. But the trigger has a problem - it runs only first 19 actions and then doesn't work.

 

[Dr Super Good]

You are htting the opt limit for WC3 due to GUIs crappy way of handeling multiboards with unnescescary itteration.
Put some triggersleepactions after every few actions with minimal delay (wait actions in GUI) or rewrite the trigger in JASS to reduce the ammount of itteration which occurs (which is easy to do as GUI actions are stupid and loop when not needed).

Basically, WC3 can only execute so much code at once without taking a break.

 

[ap0calypse]

I'll test the map in a moment.

And I attached to my post also a large picture - screenshot of the trigger, because the trigger is so long that it's hard to write it in

• tag as text.[/quote]
• It's a [b]lot[/b] easier than a screenshot of the trigger, all you need to do is write the tags and copy/paste the trigger, it's also easier for me to read... I don't see any disadvantages.
• [quote]Basically, WC3 can only execute so much code at once without taking a break. [/quote]
• Hm, didn't know that, the multiboard actions must be a lot worse than other actions, since I've made longer triggers that did work :/
• (can the Integer A/B's have something to do with it, since they're BJ's?)

 

[I34w90_238j]

Yep, it has to do with loops, that make Warcraft GUI execute functions inside loops. So functions inside loop are done many many times, and I hit the limit of functions done by Warcraft in a single moment.

Thank you Dr Super Good, you are Superman.