Sorry about that. I've not got the source to this as my hard drive blew up a few months back. I originally wrote this to be able to control PAM miners remotely and Keks then implemented that functionality into PAM.

This is broken as of 1.194, probably because of the changes to the API. If you could fix this, it would be much appreciated. :)

I’ve only tested with regular antennas. I know laser antennas are a completely different object type so it won’t work with them. Unsure about modded antennas. If they behave exactly like normal antennas then it might work. Let me know 🙂

do you know if this script will work with modded antennas or laser antennas?

Let me know how it goes. The relay piece is the only piece I've not been able to do that much testing on, though the 2-sec rebroadcast prevention seems to work nicely.

I'm planning a drone base in the center of my 5 installations (home base, plus HullTec's four factories, for survival RP gaming). This will make it easy for me to send the drone swarmt to whichever quadrant is under attack, then search the area by patrolling established waypoints.

Using another mod for in-game scripting, I may even be able to automate sending them out and when they come home, for when I'm not there to mash the buttons myself. I *may* even be able to automate sending mining drones out with PAM, so all I'd be doing is scouting ore locations and adding their GPS to the list of sites to be mined. Lol. The key there is your script's ability to rebroadcast without repeating the broadcast. I'm kind of excited to try that out, now :)

Glad you like it!

I've mainly used it with PAM and with SPUGs autodocking script along with Kolts command consoles to act as buttons. The RPBARS script is entirely generic though - all its really doing is relaying a set of params to another programmable block on the receiving grid.

Any other script that receives params can be used with it.

This... is awesome! Timestamps and acknowledgements are so cool. I wonder if there's any way to give this audio "radio chatter" to go with it lol. Do you have other examples of this in use, or YouTube vids of that? I see the value for mining, but it should work with other things, too, right? As for mining, is using this with PAM just a way to have a single interface for sending commands out? By itself, that's worth it if I'm using other command scripts, but I'm wondering if it adds to PAM's functionality too :) ^5 on a great script!

v2.0.0 - Big improvements

WILL NOT WORK WITH V1 - UPDATE ALL PROGRAMMABLE BLOCKS TO THIS VERSION AND UPDATE ALL BUTTONS TO NEW MESSAGE FORMAT


- Restructured the message for easier parsing. Now uses ':' to seperate each segment of the message - see updated docs below.
- Added script version check (see output in receiver for info if versions mismatch)
-Added Timestamp to message. Messages older than 2 seconds are ignored.
- Made BroadcastAntenna setting optional - script will find the best antenna it can on your grid if not provided.
- Added relay capability

@D4rkSh4d0w That's great to hear, thank you.

As for a debug option, if you look in the programmable blocks detail area (bottom right of the terminal) there should be some output there after you transmit.

Also, on the receiving programmable block there should be some output too, after it receives a message.

On each grid you may also add an LCD with a tag in the name. To do this, in that grid's programmable block, in the custom data field add ...

StatusLcd=<name of yor LCD>

<name of yor LCD> can be a partial name or a tag like other scripts use (i.e. [rpbars-debug] )

Once you've added that, recompile the script and it will write it's output to the LCD instead of the programmable block detail area.

I'm still getting to grips with LCD's and it's not perfect yet, which is why I didn't put it in the documentation. Also be aware that the implementation of the LCD(s) that the script uses may change in coming versions as I figure them out more.

Hi Kyr,

thx for the quick answer. That i call an awesome support!

As it turns out, i found the "custom data" button, after staring at it for like 5 min. XD
My bad, I'm running low on coffee.

Transmitting is working now. Now i just need my PAM to go home.

I've seen that u also commented on the octopus bot, together with PAM, SPUG you are creating the missing piece with RPBARS.

Thank you so much for your great work! I LOVE it so far!

Best,
D4rk

Btw: Is there DEBUG Text panel option?

@D4rkSh4d0w There's no need for a configuration section in the script. You shouldn't need to edit anything in the script its self.

On the Programmable Block that you load the script into on the "sender" end, I assume that this would be on your base or capital ship. That base or capital ship will need an antenna that can broadcast.

In the Programmable Block, click on "Custom Data" and put something like the following...

BroadcastAntenna=<your antenna name here>

Replace "<your antenna name here>" with the full, exact name of the antenna on your base/capital ship.


I'm already working on the next version which will automatically use any antenna's that are set to broadcast and will relegate this setting to being an optional override in future.

The aim is to minimise the configuration needed while still keeping the script powerful and flexible,

Very promissing! :D After hours after hours i found your script, that covers much more then a simple sender/receiver with timers.

How ever, i tried to set it up and got stuck rly soon.
It is not clear what u declare as "custom data of the pb" where the BroadcastAntenna, etc needs to be declared. Since there is not crtl-f in se, its rly painfull to sort through your script.

Would it be possibel to implement a "configuration section" at the beggining of the script where the basic naming could be done?

Best regards,
D4rk