Zainstaluj Steam
zaloguj się
|
język
简体中文 (chiński uproszczony)
繁體中文 (chiński tradycyjny)
日本語 (japoński)
한국어 (koreański)
ไทย (tajski)
български (bułgarski)
Čeština (czeski)
Dansk (duński)
Deutsch (niemiecki)
English (angielski)
Español – España (hiszpański)
Español – Latinoamérica (hiszpański latynoamerykański)
Ελληνικά (grecki)
Français (francuski)
Italiano (włoski)
Bahasa Indonesia (indonezyjski)
Magyar (węgierski)
Nederlands (niderlandzki)
Norsk (norweski)
Português (portugalski – Portugalia)
Português – Brasil (portugalski brazylijski)
Română (rumuński)
Русский (rosyjski)
Suomi (fiński)
Svenska (szwedzki)
Türkçe (turecki)
Tiếng Việt (wietnamski)
Українська (ukraiński)
Zgłoś problem z tłumaczeniem
Eventually, I just assumed that there was a problem with delays, or long command sequences, because the first thing I used this for, was to change the radius of 2 lights during an alarm, worked fine. Welp, at least I learned how to rename blocks with scripts. That gives me lots of ideas. >:D
"Caught exception during execution of script: index was outside the bounds of the array"
I then have to manually change the name of the timer block back to -0, and recompile the script
http://gtm.steamproxy.vip/sharedfiles/filedetails/?id=566270789&searchtext=
Same example with different solution:
One text panel, one program block, and one timer, just one more text command for the script 'pause'. Script will go throught the sequence, and when it comes to the 'pause' line it only changes TB name to the right iteration number, but doesn't trigger it. Script is on hold until you manually ran it by yourself. Once you do it will continue from the point it stopped first time.
This solution is way more simple.