• Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a faction for Warcraft 3 and enter Hive's 19th Techtree Contest: Co-Op Commanders! Click here to enter!
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 21st Texturing Contest: Upgrade is now concluded, time to vote for your favourite set of icons! Click here to vote!

Jass execution/operation limit

Status
Not open for further replies.
Level 19
Joined
Jun 13, 2016
Messages
587
No, it isn't. Before the 1.29 update, the execution limit was around 300,000 JASS bytecode operations flat, if I remember correctly. Note that it doesn't exactly correspond to operations in JASS, e.g. a function call is usually somewhere around 5 JASS bytecode ops, a variable assignment is somewhere around 2-3, etc.

Now the limit is 3,000,000, which is around ten times as it used to be.

It has nothing to do with the actual time it takes to execute the script, and there's actually a very good reason for it - if a thread "crashes", it needs to crash at the same point for all players if you want to avoid desyncs. If for some reason a thread crashes at different points, e.g. Player 1 thread crashes after a CreateUnit() call, and Player 2 thread crashes before that, they would desync.
 
Status
Not open for further replies.
Top