Added the final set of fixes

Author: AlexBx

bugfixes/type1/burstabuse.rst

@@ -0,0 +1,21 @@
+.. index:: Exploit; Burst abuse is fixed
+
+===========
+Burst Abuse
+===========
+
+If a unit with a multiple burst weapon (:tag:`Burst` > :value:`1`) destroys its
+target or is assigned a new target before it has fired all shots, the game
+resets the burst counter, but does not also restart reloading. The result is
+that the unit can attack the next target immediately, with a fresh set of
+bursts.
+
+Given that the delay between bursts is usually shorter than the reload time,
+this gives an unfair advantage. Given that manually changing targets or issuing
+a Stop command also resets the burst counter, this can be exploited.
+
+:game:`Ares` fixes this by not resetting the burst counter.
+
+.. note:: This might be changed in the future to also restart reloading.
+
+.. versionadded:: 3.0

bugfixes/type1/guardapproachtarget.rst

@@ -0,0 +1,16 @@
+.. index:: Behavior; Anti-air units like IFVs will not chase aircraft in Guard
+
+==============================================
+Units in Guard Mission Will not Chase Aircraft
+==============================================
+
+Units in Guard mission might leave their position to chase after enemy aircraft.
+The IFV of the vanilla game is notorious for this kind of behavior, breaking
+formation and leaving the area it should defend against air attacks undefended,
+often easily lured into an ambush itself.
+
+This behavior is fixed in :game:`Ares` and units on Guard mission will no longer
+leave their position to pursue aircraft when the aircraft goes out of range.
+Mind that this fix only applies to Guard missions, not Area Guard missions.
+
+.. versionadded:: 3.0

bugfixes/type1/infantrydeploy.rst

@@ -0,0 +1,16 @@
+.. index:: Glitches; Infantry jamming when using area attack
+
+======================
+Infantry Deploy Glitch
+======================
+
+Under certain circumstances, :tag:`Deployer=yes` infantry units with an
+:tag:`UndeployDelay` greater than or equal to zero get jammed. This for instance
+made the Yuri Clone helplessly hover in air for half a minute after using its
+Area Fire deploy attack.
+
+Due to a hole in the state machine for that mission, the game would fall back to
+what appears to be the default handling to make such holes obvious. :game:`Ares`
+plugs that hole.
+
+.. versionadded:: 3.0

bugfixes/type2/freeunit.rst

@@ -0,0 +1,13 @@
+.. index:: Free Unit; Support for units other than Harvesters
+
+=========================
+Free Unit Initial Mission
+=========================
+
+Refinieries usually come with free Harvester units, which are automatically
+assigned the Harvest mission. The game does the latter even if the Free Unit is
+no Harvester.
+
+:game:`Ares` sets non-Harvesters on an Area Guard mission. 
+
+.. versionadded:: 3.0

bugfixes/type2/toolongidnames.rst

@@ -0,0 +1,19 @@
+.. index:: Debugging; Warning if a too long ID is used
+
+==================================
+Warning When a Too Long ID is Used
+==================================
+
+If the game tries to instantiate a type with an ID longer than 24 characters,
+:game:`Ares` will show a dialog pointing out the ID used. This happens if a type
+list includes a too long ID directly, or for example, if the game automatically
+adds a too long type ID it encountered to the list while parsing an INI section.
+This always indicates a bug, and this always is a bug present in a modded INI
+or map file.
+
+.. note:: This feature does not catch too long IDs present in INI sections that
+  are not automatically added to the type list while parsing. Searching for the
+  exact ID will just fail. Only if the tag is read by :game:`Ares`, a warning
+  will be emitted in the debug log.
+
+.. versionadded:: 3.0