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






I'm not sure whether you will need to tweak anything to use it other than to update the PBs on the grids.
It looks like it might have a bug related to ships that dock, but it seems like exactly what you're looking for.
Remotely duplicating the text of an LCD is interesting though; if no one else has already done it then maybe I'll poke at it and see if there's a robust way to do it that's simple to use.
I don't think adding code that would be 99% unused (especially given the intention of the script as a whole) is something I want to build in, since it's opposite the intention of the script.
That said, if I did add some sort of mechanism for alternate names, I would do it via the Custom Data. I'm considering moving the existing _minor_ options into the Custom Data already, because generally speaking I want configuration to be a separate from the script. That way if/when I update the script, no one has to go back and remember all the custom things they changed (which is one reason I end up running old versions of scripts for ages).
I appreciate the feedback though, it's something I'll keep in mind as a potential change if I do move the options into Custom Data.
Example:
[code]
string argument = "Base Defenses On/Off"; //This is what is being run
switch (argument)
{
case "ALERT": transmit("baseAlertTimerMain"); break;
case "GARAGE": transmit("mainGarageDoorTimerOpen 1"); break;
case "TROLL": transmit("SelfDestructTimer LOL"); break;
default: transmit(argument); break;
}
[/code]
The function would execute the default case and send the argument, witch is a timer name. If one of the cases were the argument, it would call the timer associated with that key.
It's more of an ease-of-access thing. You might want your timers to have unique, descriptive names that are nearly impossible to remember when it's not right in front of your face. This way, you can enter all the timers you want to use into the switch and copy it from PB to PB; all you need to remember is the shorthand cases
Maybe the other way to ask the question.
Why would you not just pass the timer block name, why would you want to use a different string when calling the PB run command?