Absolutely--it's possible to crash the Map Init event by exceeding the operations limit. If this happens, the rest of the Map Init thread that is needed by the game is never run which may result in things unexpectedly not being as anticipated from the editor.
The operation limit has been increased to great extents, if I remember, it was even before patch 1.30. But yes, you can crash the thread, although it now requires a shit ton of operations, which is highly unlikely unless you're a crazy person hanging around with 100000 map initialization triggers scattered around,
This is able to happen because all Map Init triggers occur as part of the same thread (sequentially after each other), so while any one trigger may not hit the OP limit, all of them together could easily do so.
but who the fuck does that? People usually use
-
Trigger - Trigger Name <gen> (ignoring conditions)
to organize a bunch of actions.
But... you know what, yeah i've seen some people using map init in some triggers other than in a single one.
This part is the only part where you're wrong, you can have 1 map init trigger that runs several other triggers on it, and they can be very long as long as each of them doesn't surpass the oplimit, which is needless to say by this way practically impossible to. But why is that so? Because Trigger - run trigger name (checking conditions/ignoring conditions); ExecuteFunc, Pick Every Unit, waits, timers and a few other things make a new thread, thus reseting the operation limit.
Trigger operation limits?
Operation limit
Escaping the Operation Limit
[vJASS] - Does .evaluate() prevent from OpLimit?
No. This is functionally the same as having one massive trigger if you are using the Map Init event. If you are using Elapsed Game-Time like I suggest then you can make an order to things by choosing what time it executes. There is no downside to this.
Using Elapsed Game-Time, yes, there is one. Slight lag spike in game when executed, assuming the trigger is massive, just once though.
I admit I had made the mistake of not explaining everything initially, but the operation limit didn't even cross my mind (been slacking). Yet I couldn't let
@Pyrogasm have the last laugh!!!