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
groups=GridTerminalSystem.BlockGroups;
at the end of the "List blocks we will use" section. Anyone know a quick fix? I'm not too savvy with C#, and this little toolkit looks like the perfect weapon for taking care of pesky NPC ships.
The script is unlike other ones, it gives the user the ability to control most parts of a ship (Turning items on and off and using any function that they might have such as using turrets and switching targeting systems) The program does Not automatically turn off anything. it was initially intended to work around the owner system (e.g. even if you dont have access to the control panel, you can still run these modules and override their access) however due to the patch that stops scripts from being run on ships / stations that you don't own, it kind of defeats the purpose. however there are still a large amount of people that don't set owner access to their ships / stations so you can mess with their stuff anyway.
Too long didn't read:
The script doesn't do anything you don't want it to, you have full control over what it: turns off, turns on, toggles between etc. It will only turn things off if you want it to and vice versa.
Hmm, dunno. I think they get rid of ownership but I'm not too sure.
@[N45]Jason45PC
Sorry, I'm not sure on that one, you'll have to test it yourself unfortunatley, I only just found out about the ownership update earlier and havent been able to test stuff out yet.
Right, I've checked the changelog and yeah, you are right. I cant see there being any way around this unless people dont set ownership to their blocks. You would be suprised how many people dont set blocks to their own. I'll have another look just to make sure but as I mentioned I dont think there is going to be a workaround unfortunatley.
Okay, thanks. I'll look into it :D.
Really? That sucks... When you say with the recent update do you mean like real recent? Or the actual programmable block update? Because if you mean the programmable block update, I can confirm it does work on blocks that are owned by other people. I tested it out on many different peoples servers and each time if I had full access denied, I could run the scripts.
Thanks man :D, also Its funny you say that because this is what I originally had, but it provides a few problems: In most cases, for me at least, the programmable block GUI is laggy, so when I'm in the editor and click on a line, I can expect it to take at least 5 seconds before I can begin.
Another problem is that I thought people may not understand what to remove and end up removing the wrong things.
In some of the longer modules removing / adding the // on each line would take years and would make the virus less effective / efficient.
Thanks for the feedback though, it is appreciated.
This makes it easyer to use for someone with no Programming experience because they do not get confused by adding and removing different lines from the consol.
Hope my explenation is understandable. As I wrote befor you did some nice work there.