[General] where is the limit?

[Dr. Boom]

Moin moin =)

Yes that's what I want to know, if there is any limit anyway...

When you make a spell with triggers GUI or vJass, you use a loop time of 0.03 seconds or 0.04 seconds.

In this very short time the actions should happen. Now I want to now, is there a limit how much actions, calculations and so on I can put in the loop until Wc3 says "Omg I can't handle more of it!"?

Also in a map, where are many spells and all cast at the same time, with looong loop actions, the game must calculate values, set variables and and and ...

So is there a limit in this case? Because I don't think, the game can handle unlimited values, variables, actions, settings and so on

Edit: But also, there aren't the loop actions only, the globals .. the init settings and so on

Greetings - Thanks - Peace
Dr. Boom

 

[Maker]

There's no real answer to this question.

But for computers, 0,03 seconds is a very long time. All modern PCs should handle WC3 without a hitch.

Modern CPUs can handle tens of thousands of millions instructions per second.

 

[WaterKnight]

There's a thread operation limit. A thread is an execution sequence of code independent to other threads. So when you execute a trigger, when it is fired by an event or timer they will each get an individual thread. A thread can do up to 300k micro operations (see here), there's also a catalogue at the end of the first post. A call of TriggerSleepAction can refresh the counter, or you start another thread.

How many actions overall you can execute depends on your computer. Maybe Wc3 only gets a maximum of memory assigned but you'd have to exaggerate it and it would be already completly lagging for a long time.

For amounts of written code, I have not found a limit yet but you cannot play maps above 8mb via Battle.net. I only know that there is a max of about 25k variables, still you could use game caches/hashtables/other objects to export further values.

 

[Dr. Boom]

Yes that was what I though about. Of course for modern computers 0.03 can be a long time ( or should be a long time ) but Warcraft 3 itself.

Hmm but after reading your threads, I think everyone don't need to think about it, where the limit is because to reach the limit at these points, you have write a LOT of code ^^

Greetings and Peace
Dr. Boom

 

[Maker]

Oh yeah, I once run into the operation limit when generating a code that changed all tuiles in a map to another type.

I wondered why the code just seemed to quit half-way through the map, half of the tiles were not changed. I turned out I reached the limit, and wait indeed solve the issue.

 

[Anachron]

You can't do more then 9000 operators in a thread.
You can however force it (so another thread is executed right after it) with vJass:

call func.execute()

(Execute creates a new thread)