Rednet.send - Revision history

Bomb Bloke: Works with types other than strings.

2015-06-14T13:51:33Z

Works with types other than strings.

Bomb Bloke at 09:28, 17 June 2014

2014-06-17T09:28:14Z

Bomb Bloke: CC 1.6 update adds protocols

2014-06-06T06:33:31Z

CC 1.6 update adds protocols

Apemanzilla at 18:38, 4 June 2014

2014-06-04T18:38:48Z

Bomb Bloke: Bah, wasn't done editing before. Anyway: somewhat more of a re-write.

2014-02-24T01:18:36Z

Bah, wasn't done editing before. Anyway: somewhat more of a re-write.

Bomb Bloke: "WaitUntilPortOpen" is not currently a valid parameter; suspect it was pre-1.5 behaviour?

2014-02-24T01:00:25Z

"WaitUntilPortOpen" is not currently a valid parameter; suspect it was pre-1.5 behaviour?

Cranium: fixing links

2013-07-18T11:42:13Z

fixing links

Cranium: Changing int to number

2013-07-18T11:35:05Z

Changing int to number

Lyqyd: Int linking fix.

2012-11-30T18:30:58Z

Int linking fix.

AfterLifeLochie: Missed one! :P

2012-11-30T13:48:58Z

Missed one! :P

@@ Line 2: / Line 2: @@
 {{Function
 |name=rednet.send
-|args={{type|number}} receiverID, {{type|string}} message, [<nowiki/>{{type|string}} protocol]
+|args={{type|number}} receiverID, {{type|any}} message, [<nowiki/>{{type|string}} protocol]
 |returns={{Type|boolean}} success code. True if a message has been sent (note - "sent", as opposed to "received" or even "was receivable"), false if not.
 |api=rednet
 |addon=ComputerCraft
-|desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific [[os.getComputerID|ID]] (compare [[rednet.broadcast|rednet.broadcast()]], which aims to target everything in range). At least one such modem must first be "[[Rednet.open|opened]]" before sending is possible. Assuming the target was in range and also had a correctly opened modem, it may then use [[rednet.receive|rednet.receive()]] to collect the message.<br><br>
+|desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific [[os.getComputerID|ID]] (compare [[rednet.broadcast|rednet.broadcast()]], which aims to target everything in range). At least one such modem must first be "[[Rednet.open|opened]]" before sending is possible. Assuming the target was in range and also had a correctly opened modem, it may then use [[rednet.receive|rednet.receive()]] to collect the message.
-Messages are transmitted on a channel number equal to the target system's ID, with a suggested "reply" channel equal to the sending system's ID. Be aware that if other users are in range of your [[Wireless Modem|wireless]] network, or cabled into your [[Wired Modem|wired]] network, knowing / guessing your target ID number will allow them to [[Modem.open|manually open]] that channel on their own systems in order to receive your messages. As of ComputerCraft 1.6, all rednet messages are additionally sent on channel 65533 (allowing the [[Repeat|repeat script]] to easily detect them).<br><br>
+Most data types can be sent, but functions / coroutines are converted to nil. In the past tables were also converted to nil, and required the use of [[textutils.serialize]]() to transmit - they can now be sent directly ''(exact build which changed things is unknown, but CC 1.53 works and 1.5 does not)''.
-ComputerCraft 1.6 also introduces "[[Rednet (API)#Protocols|protocol]]" - simple string names indicating what the message is about. Receiving systems may filter messages according to their protocols, thereby automatically ignoring incoming messages which don't specify an identical string. It's also possible to [[rednet.lookup|lookup]] which systems in the area are interested in certain protocols, hence making it easier to determine where given messages should be sent in the first place.<br><br>
+Messages are transmitted on a channel number equal to the target system's ID, with a suggested "reply" channel equal to the sending system's ID. Be aware that if other users are in range of your [[Wireless Modem|wireless]] network, or cabled into your [[Wired Modem|wired]] network, knowing / guessing your target ID number will allow them to [[Modem.open|manually open]] that channel on their own systems in order to receive your messages. As of ComputerCraft 1.6, all rednet messages are additionally sent on channel 65533 (allowing the [[Repeat|repeat script]] to easily detect them).
-Messages are typically strings, however later versions of ComputerCraft ''(which?)'' may alternatively send tables instead. Those users still on older versions may find [[Textutils.serialize|textutils.serialize()]] useful when wanting to transmit tables.
+ComputerCraft 1.6 also introduces "[[Rednet (API)#Protocols|protocol]]" - simple string names indicating what the message is about. Receiving systems may filter messages according to their protocols, thereby automatically ignoring incoming messages which don't specify an identical string. It's also possible to [[rednet.lookup|lookup]] which systems in the area are interested in certain protocols, hence making it easier to determine where given messages should be sent in the first place.
 |examples=
 {{Example

@@ Line 8: / Line 8: @@
 |desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific [[os.getComputerID|ID]] (compare [[rednet.broadcast|rednet.broadcast()]], which aims to target everything in range). At least one such modem must first be "[[Rednet.open|opened]]" before sending is possible. Assuming the target was in range and also had a correctly opened modem, it may then use [[rednet.receive|rednet.receive()]] to collect the message.<br><br>
-Messages are transmitted on a channel number equal to the target system's ID, with a suggested "reply" channel equal to the sending system's ID. Be aware that if other users are in range of your [[Wireless Modem|wireless]] network, or cabled into your [[Wired Modem|wired]] network, knowing / guessing your target ID number will allow them to [[Modem.open|manually open]] that channel on their own systems in order to receive your messages. As of ComputerCraft 1.6, all rednet messages are additionally sent on channel 65533 (allowing the [[Repeat (program)|repeat script]] to easily detect them).<br><br>
+Messages are transmitted on a channel number equal to the target system's ID, with a suggested "reply" channel equal to the sending system's ID. Be aware that if other users are in range of your [[Wireless Modem|wireless]] network, or cabled into your [[Wired Modem|wired]] network, knowing / guessing your target ID number will allow them to [[Modem.open|manually open]] that channel on their own systems in order to receive your messages. As of ComputerCraft 1.6, all rednet messages are additionally sent on channel 65533 (allowing the [[Repeat|repeat script]] to easily detect them).<br><br>
 ComputerCraft 1.6 also introduces "[[Rednet (API)#Protocols|protocol]]" - simple string names indicating what the message is about. Receiving systems may filter messages according to their protocols, thereby automatically ignoring incoming messages which don't specify an identical string. It's also possible to [[rednet.lookup|lookup]] which systems in the area are interested in certain protocols, hence making it easier to determine where given messages should be sent in the first place.<br><br>

@@ Line 2: / Line 2: @@
 {{Function
 |name=rednet.send
-|args={{type|number}} receiverID, {{type|string}} message
+|args={{type|number}} receiverID, {{type|string}} message, [<nowiki/>{{type|string}} protocol]
 |returns={{Type|boolean}} success code. True if a message has been sent (note - "sent", as opposed to "received" or even "was receivable"), false if not.
 |api=rednet
 |addon=ComputerCraft
-|desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific ID. At least one such modem must first be "opened" with eg [[Rednet.open|rednet.open()]] before sending is possible. Assuming the target was in range and also had a correctly opened modem, that can then use [[rednet.receive|rednet.receive()]] to collect the message. See also [[rednet.broadcast|rednet.broadcast()]].
+|desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific [[os.getComputerID|ID]] (compare [[rednet.broadcast|rednet.broadcast()]], which aims to target everything in range). At least one such modem must first be "[[Rednet.open|opened]]" before sending is possible. Assuming the target was in range and also had a correctly opened modem, it may then use [[rednet.receive|rednet.receive()]] to collect the message.<br><br>
-Note that any systems in range (ie, connected to your [[Wired Modem]] network cable runs or close enough to your [[Wireless Modem]]s) are capable of receiving the message if their owners have some idea what ID you're targeting - they need only use [[Modem.open|modem.open()]] to manually open the corresponding channel(s) you're using on their systems, and they have full access to your communications. Use of [[Rednet.open|rednet.open()]] only opens certain channels (selected automatically) - ''this is a "convenience" feature, not a "security" feature.''
+Messages are transmitted on a channel number equal to the target system's ID, with a suggested "reply" channel equal to the sending system's ID. Be aware that if other users are in range of your [[Wireless Modem|wireless]] network, or cabled into your [[Wired Modem|wired]] network, knowing / guessing your target ID number will allow them to [[Modem.open|manually open]] that channel on their own systems in order to receive your messages. As of ComputerCraft 1.6, all rednet messages are additionally sent on channel 65533 (allowing the [[Repeat (program)|repeat script]] to easily detect them).<br><br>
-Messages are typically strings, however later versions of ComputerCraft ''(which?)'' may alternatively send tables instead. Those on older versions may find [[Textutils.serialize|textutils.serialize()]] useful when wanting to transmit tables.
+ComputerCraft 1.6 also introduces "[[Rednet (API)#Protocols|protocol]]" - simple string names indicating what the message is about. Receiving systems may filter messages according to their protocols, thereby automatically ignoring incoming messages which don't specify an identical string. It's also possible to [[rednet.lookup|lookup]] which systems in the area are interested in certain protocols, hence making it easier to determine where given messages should be sent in the first place.<br><br>
-To get the ID of a given system, refer to [[os.computerID|os.computerID()]].
+Messages are typically strings, however later versions of ComputerCraft ''(which?)'' may alternatively send tables instead. Those users still on older versions may find [[Textutils.serialize|textutils.serialize()]] useful when wanting to transmit tables.
 |examples=
 {{Example
@@ Line 18: / Line 18: @@
 |code=rednet.send(22,"ComputerCraft")
 }}
 }}
 [[Category:API_Functions]]

@@ Line 3: / Line 3: @@
 |name=rednet.send
 |args={{type|number}} receiverID, {{type|string}} message
-|returns=[[boolean_(type)|boolean]] success code. True if a message has been sent (note - "sent", as opposed to "received" or even "was receivable"), false if not.
+|returns={{Type|boolean}} success code. True if a message has been sent (note - "sent", as opposed to "received" or even "was receivable"), false if not.
 |api=rednet
 |addon=ComputerCraft

@@ Line 6: / Line 6: @@
 |api=rednet
 |addon=ComputerCraft
-|desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific ID. At least one such modem must first be "opened" with eg [[Rednet.open|rednet.open()]] before sending is possible. Assuming the target was in range and also had a correctly opened modem, it can then use [[rednet.receive|rednet.receive()]] to collect the message. See also [[rednet.broadcast|rednet.broadcast()]].<br><br>
+|desc=Allows a [[computer]] / [[turtle]] with an attached [[modem]] to send a message intended for a system with a specific ID. At least one such modem must first be "opened" with eg [[Rednet.open|rednet.open()]] before sending is possible. Assuming the target was in range and also had a correctly opened modem, that can then use [[rednet.receive|rednet.receive()]] to collect the message. See also [[rednet.broadcast|rednet.broadcast()]].
-Note that any systems in range are capable of receiving the message if their owners have some idea what ID you're targeting - they need only use [[Modem.open|modem.open()]]
+Note that any systems in range (ie, connected to your [[Wired Modem]] network cable runs or close enough to your [[Wireless Modem]]s) are capable of receiving the message if their owners have some idea what ID you're targeting - they need only use [[Modem.open|modem.open()]] to manually open the corresponding channel(s) you're using on their systems, and they have full access to your communications. Use of [[Rednet.open|rednet.open()]] only opens certain channels (selected automatically) - ''this is a "convenience" feature, not a "security" feature.''
 To get the ID of a given system, refer to [[os.computerID|os.computerID()]].