Updated to make exceptions when receiving a command or message less likely. At least it should stop the script from crashing completely.

Updated for latest SE release to remove deprecation warnings. I'm not sure how backwards compatible the script is now, so if you're running an old version of SE for some reason, this version of the script may not work.

Also, it turns out that it's not too difficult for basic support of the new control seat LCDs. This is absolutely the most brain-dead support, so it will always use the very first surface it can.

Quality of life improvements and maybe a bug fix?

The documents for the IGC callback suggest that if there are pending messages in the communication system, then the receiver will be called for each of them (but only one per tick). It seems like that isn't actually what happens, so the PB now runs every tick and checks if there are pending messages. This helps in case it is receiving multiple messages in the same tick.

Also added some status information to show that it is running and how many messages it has sent or received.

Fixed bugs with sending LCD text with multiple lines
Fixed bugs with using channels when sending LCDs

So lcd:channelName::lcdName should be working properly now

- Added a configuration option to make the LCD receive require matching a LCD to display text and made that the default, but it can be configured to use the generic LCD.

- Make the lcd: copy a little more robust on the receiving side.

Now if there is a matching LCD on the receiving side, it will be updated instead of the generic LCD for "text:" messages.

- Added limited support for broadcasting a LCD panel

This still has a specific limitation that the destination programmable block will only write to a single LCD. Running the sending programmable block with lcd:<panel name> will cause it to transmit the text of the LCD panel <panel name>.

On the receiving side, if a LCD panel is set for receiving messages, it will have its content replaced with the received message.

- Support sending on alternate channel names

By default, all sending and receiving use the channel names as configured by the script or custom data.
But you can send on a specific channel with

text:<channel name>::Hello world
<channel name>::timerBlockName