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
Good luck with the script-renovation, flexibilty and ease of use should be the hallmark of scrips that has such outwards simplicity as this one, keep it up.
I still plan on doing some minor changes to the script, maybe add in a group option for those that like using groups, but I will make it so the tag goes inside the custom data block instead of filling the blocks name.
Have a small planet miner that I need to know when to stop mining with before it crashes and burns, since the thrusters can't hold it up with even the drills loaded. Worked like a charm before, but now it throws an exception as it can't type cast 'Sandbox.Game.Weapons.MyShipDrill" to 'Sandbox.ModAPI.Ingame.IMyCargoContainer', anything I can do? Can't really cram a container in there, it's really compact.
Also, not too keen on the renaming everything to 'cargo ore' and what not, like to have more helpful 'induvidual' names for containers. Block Groups always seemed like a more flexible way to tell scrips what they can fiddle with.