Editing mirc/on events/on udpwrite

The '''ON UDPWRITE''' is an event which was added in mIRC with UDP, but never has been documented. The event was meant to be used as the {{mIRC|on sockwrite} event for TCP, however, something fucked up and the actual design ended up being that on sockwrite triggers for UDP socket if no error happened while on udpwrite will trigger if an error occured.

'''Note''': This behavior was changed for consistency and backward compatibility in mIRC 7.33:

-on udpwrite is no longer triggered.
-on sockwrite triggers for UDP socket regardless of the error state.

== Writting more ==

It is possible that the data hasn't sent successfuly, especially with UDP, you should be checking for error with {{mIRC|$sockerr} before trying to do anything, here is a list of the possible value for $sockerr in the on UDPWRITE event:

* '''0''' - The data has been written sucessfuly.
* '''3''' - Error occurred while trying to send the data, $sock().wsmsg will contain a more specific error message.

== Examples ==

<source lang="mirc">
on *:udpwrite:name:{
  if ($sockerr) { echo -s An error occured while trying to read data: $sock($sockname).wsmsg | return }
}
</source>

== Compatibility ==
{{mIRC compatibility|5.5}}

== See Also ==
* {{mIRC|List of on events|mIRC events}}
* {{mIRC|/sockwrite}}
* {{mIRC|/sockclose}}
* {{mIRC|/sockread}}
* {{mIRC|/sockaccept}}
* {{mIRC|/sockpause}}
* {{mIRC|$sock}}
* {{mIRC|$sockbr}}
* {{mIRC|$sockerr}}

[[Category:MIRC on events|sockread]]
@@ Line 1: / Line 1: @@
-{{mirc title|On Udpwrite - Events}}
+The '''ON UDPWRITE''' is an event which was added in mIRC with UDP, but never has been documented. The event was meant to be used as the {{mIRC|on sockwrite} event for TCP, however, something fucked up and the actual design ended up being that on sockwrite triggers for UDP socket if no error happened while on udpwrite will trigger if an error occured.
-The '''ON UDPWRITE''' is an event which was added in mIRC with UDP, but never has been documented. The event was meant to be used as the {{mIRC|on sockwrite}} event for TCP, however the actual design ended up being that:
-* on sockwrite triggers for UDP socket if no error happened
-* on udpwrite will trigger if an error occurred.
+'''Note''': This behavior was changed for consistency and backward compatibility in mIRC 7.33:
-'''Note:''' This behavior was changed for consistency and backward compatibility in mIRC 7.33:
+-on udpwrite is no longer triggered.
-* on udpwrite is no longer triggered.
+-on sockwrite triggers for UDP socket regardless of the error state.
-* on sockwrite triggers for UDP socket regardless of the error state.
+== Writting more ==
-== Writing more ==
+It is possible that the data hasn't sent successfuly, especially with UDP, you should be checking for error with {{mIRC|$sockerr} before trying to do anything, here is a list of the possible value for $sockerr in the on UDPWRITE event:
-It is possible that the data hasn't sent successfuly, especially with UDP, you should be checking for error with {{mIRC|$sockerr}} before trying to do anything, here is a list of the possible value for $sockerr in the on UDPWRITE event:
 * '''0''' - The data has been written sucessfuly.
@@ Line 27: / Line 23: @@
 == Compatibility ==
 {{mIRC compatibility|5.5}}
-Removed: mIRC v7.33
-Removed On:27/05/2014
 == See Also ==
@@ Line 43: / Line 35: @@
 * {{mIRC|$sockerr}}
-[[Category:mIRC on events|udpwrite]]
+[[Category:MIRC on events|sockread]]