安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题






Thanks
I didn't know that one could save a reference with set first @unit... .
This is unknown to many industry logic programmers because they often call ubind @... 50 or 100 times to be sure that they have bound each unit at least once..
But how can you tell that you have the first unit of this type again?
As far as I know, the @unit object has no unique ID.
When you bind a unit with ubind, you can't distinguish it from another unit of the same type, can you?
Thanks a lot, kind regards,
Thomas
"jump 70 equal @unit null"
the the integrated editor should update the references?
op add @counter tmp 77
Then you must add 2 to the 77, making it 79, etc. Those instructions are like jump statements, but using math to choose where to jump.
I tryed added code after the check junp at unit null but the script don't work anymore as i add sensor code
can you help me? do you have a discord / mail