Added notes on is_confused and is_dragged, Hit.Confuse, corrected Hit.no_counter to Lua name, recommendation for Drag endlag and checking confusion/blind

Author: Alrysc

docs/updates/v2.1.md

@@ -48,11 +48,12 @@ If any mods have broken, ping me (Alrysc) on Discord and I'll see about patching
 * Battle.AlertSymbol.new is available
 * Access to Left_Shoulder and Right_Shoulder inputs
 * Hit.NoCounter hitflag, prevents attack from countering
+* Hit.Confuse hitflag, adds Confuse for 110 frames
 * All Entities can use battle_start_func and battle_end_func
 * Access to Character.can_attack
 * Access to Entity.set_counter_frame_range
-* Access to Entity. is_stunned, is_frozen, is_rooted, and is_blind
-
+* Access to Entity. is_stunned, is_frozen, is_rooted, is_blind, is_confused, and is_dragged
+* 
 ## Breaking Changes
 
 There is one breaking change, which affects very few mods. The vast majority of mods 
@@ -97,9 +98,9 @@ end
 For other examples using these functions, see [Custom Charge Times](#custom-charge-times).
 
 ## Recommended Mod Upgrades
-No mods should be broken by this update, but modders now have an opportunity to 
-add more to their mods. Some of these recommendations are to warn about behavioral 
-changes, but mod updates are not necessarily required.
+No mods should be broken by this update (except for mods that affected charge time), but 
+modders now have an opportunity to add more to their mods. Some of these recommendations 
+are to warn about behavioral changes, but mod updates are not necessarily required.
 
 Other recommendations are for new things that can be added to mods to either make 
 certain logic safer, or improve mods with new functionality.
@@ -193,12 +194,31 @@ button and queue the action multiple times, or could even press it while stunned
 action happen immediately when stun ends. Guarding the `card_action_event` with `can_attack` 
 and `is_moving` prevents this.
 
-#### Hit.no_counter
+#### Hit.NoCounter
 You can now make attacks that can never counterhit. In v2.0, this was able to be done using 
-the raw value of the enum (2048), but now the enum value is accessible using `Hit.no_counter`. 
+the raw value of the enum (2048), but now the enum value is accessible using `Hit.NoCounter`. 
 If you used `2048`, consider updating to use the enum value, which is guaranteed to always 
 work in the future.
 
+#### Check Confusion and Blind
+In the original games, enemies would often act differently than normal if they were blind 
+or confused. Modders can now check for these conditions with `Entity.is_confused` and 
+`Entity.is_blind`.
+
+According to K1rbyat1na, confused enemies in BN3/EXE3 acted the same as if they were rooted, 
+so their movements will not happen. But in later games, confused enemies act the same as 
+if they were blinded, which means, quoted:
+"
+1. They have a longer idle delay.
+2. They can't choose the correct tile for an attack and choose it randomly (e.g., StarMan using Star Arrow).
+3. They skip attacks that require moving to a specific tile (e.g., StarMan using Moon Dance).
+
+Some bosses have unique features in the Blind state. For example, Blinded Forte always excludes tiles 
+containing the player when using Shooting Buster so he never hits them.
+"
+
+You might consider following this for your mods to be closer to the source material.
+
 #### `battle_end_func` and `battle_start_func`
 All Entities can use the `battle_start_func` and `battle_end_func` now. This is most likely 
 to come up where modders have wanted to remove Spells from the Field when battle ends, or 
@@ -262,6 +282,13 @@ inflict Drag:
 2. Drag and Freeze are fully incompatible. If any attacks have Hit.Freeze and Hit.Drag, they 
    will never cause Freeze. If you have done this, consider removing Hit.Freeze.
 
+#### Drag Endlag
+The Drag status now properly keeps Entities from acting for over 20 frames after movement 
+stops. This is the Drag endlag, during which `Entity.is_moving` and `Entity.is_sliding` 
+will return false, which was not the case in v2.0.
+
+See [safer card_action_event](#safer-card_action_event).
+
 #### Movement Endlag
 In v2.0, all movement had at least one frame of endlag. Endlag of `frames(0)` and 
 `frames(1)` were identical. With v2.1, this is no longer the case.