Created I/O System Changes (markdown)

I-O-System-Changes.md

@@ -0,0 +1,23 @@
+Mapbase actually makes some direct changes to the I/O system itself, particularly when it comes to how entities handle input parameters.
+
+---
+### Improved Conversion
+
+Inputs that take a specific type of parameter (e.g. SetValue on math_counter requires a number) often have to convert data to their desired type. It can get a little complicated if you're not a programmer, but this conversion process has been improved drastically.
+
+For example, if you tried to pass an empty parameter to a math_counter in an attempt to clear it, it will throw a "Bad input/output link" warning at the console. In Mapbase, the math_counter will register the empty parameter as blank and reset to 0.
+
+There was also apparently an issue where a number outputted by a math_counter could not be used in something that could take any text. That has been fixed as well.
+
+---
+### Miscellaneous
+
+This section covers a few miscellaneous changes that are a bit more niche and harder to understand if you don't know how this stuff works internally.
+
+#### FIELD_EHANDLE supports !activator, !caller, and !self
+Inputs that take a specific entity handle can now use !activator, !caller, or !self.
+
+#### FIELD_EHANDLE can find entities by classname
+Inputs that take a specific entity handle can now take a classname string and find an entity by its classname.
+
+#### e