安装 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(越南语)
Українська(乌克兰语)
报告翻译问题









At least we find out that it works with simple commands, maybe sometimes it can be useful.
I think what's going on with the timer is as you said, the timer runs each slot at a time, but because it's so fast we can't notice. In reality the script is run 3 separate times, there's no multitasking involved, although it looks like there is. I guess it as to do with the game mechanics and not with the script itself.
I made a new platform to replicate and see if I made anything wrong and it worked again so I think you can implement this as a way of multitasking your script.
Keep up the god work, I can't wait for the V2.0 and to use the "else if" statements :-D
Thank you Rich, I'll be adding this to the Guide for V2.0.
Code blocks:
@Spot01{
OnOff Spotlight01
}
@Spot02{
OnOff Spotlight02
}
@Spot03{
OnOff Spotlight03
}
Arguments inside the actions timer,
LCD Display(Spot01)
LCD Display(Spot02)
LCD Display(Spot03)
Later I wil check if theres anything wrong with my coding and let you know.