Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
My edit of the code:
string[]q={"LCD1_ALL_CMS_Nova_Cargo","LCD2_ALL_CMS_Nova_Cargo"};
Original example of the code when loaded in the PG:
string[]q={"LCD1_ALL_container1","LCD2_ALL_container2"};
How do i go about setting this up.
#CREATEITEMGROUP_{ITEMGROUPNAME}_{ITEM1}_{ITEM2}_{ITEM3}_{ITEM4}_{ITEM5}_EOL
Players could then use the regular command LCD2_{ITEMGROUPNAME}_container2 to display *exactly* what they want.
Does that sound doable?
One of the simplest scripts to set up that I've seen is "ExcavOS"; it's super easy to implement with just the parameters to enter in custom data.
This could perhaps serve as inspiration for the setup part.
- Handling groups, not just individual containers
- Spamming the inventory to multiple screens
- Color customization options (less important, but would be nice)
string[]q={"LCD1_ALL_container1","LCD2_ALL_container2"};
If you don't have any of the ones listed here, the script throws an error. Either delete the screens you don't have (for example, I didn't have an LCD2) or double check the names of the screens.
As a suggestion for the author, why not put that string in the custom data of the program block, much easier to edit. Bonus if it can go in the custom data of the LCD so I can configure displays when I build them without having to run back.