@@ -535,0 +538,4 @@
+    fn fmt(&self, f: &mut Formatter<'_>) -> std::fmt::Result {
+        write!(f, "{:?} {:?} {:?} {:?} {:?}", self.module, self.command, self.alias, self.help, self.required_roles)
+    }
+}

@@ -1228,2 +1263,3 @@
         ).await;
-        
+
+        dbg!("after");

@@ -1226,3 +1260,4 @@
+        // So execbody waits for itself to finish.
         (self_ar.read().await.exec_body)(
             self_ar.read().await.parent_params.clone()
         ).await;

@@ -16,2 +16,4 @@
 casual_logger = "0.6.5"
 chrono = "0.4.35"
+tokio-console = "0.1.10"
+console-subscriber = "0.2.0"

@@ -78,0 +80,4 @@
+                let out = Some(r.read().await.channel.clone());
+
+                // => 03.30 - This isn't reached because of the Deadlock
+                dbg!(">> Just after Potential Deadlock Lock");

@@ -1230,0 +1293,4 @@
+        {
+            let guard2 = self_ar.read().await;
+            (guard2.exec_body)(parent_params).await;
+            drop(guard2);

@@ -52,2 +52,3 @@
 
-    pub async fn get_channel(&self) -> Option<Channel> {
+    // pub async fn get_channel(&self) -> Option<Channel> {
+    pub fn get_channel(&self) -> Option<Channel> {

@@ -63,0 +70,4 @@
+        thread 'tokio-runtime-worker' panicked at src\core\bot_actions.rs:66:38:
+Cannot block the current thread from within a runtime. This happens because a function attempted to block the current thread while the thread is being used to drive asynchronous tasks.
+         */
+        let curr_act_lock = curr_act.blocking_read();

@@ -634,0 +648,4 @@
+    // exec_body : fn(ExecBodyParams),
+    exec_body : fn(Arc<RwLock<ExecBodyParams>>),
+    // pub parent_params : ExecBodyParams ,
+    pub parent_params : Arc<RwLock<ExecBodyParams>> ,

@@ -1109,0 +1157,4 @@
+                        drop(guard1);
+                    });
+
+                    loopbodyspawn.await.unwrap();

@@ -1152,6 +1209,8 @@ impl Routine {
 
             }
 
+            dbg!("SUCCESS! Routinecompleted");

@@ -253,0 +282,4 @@
+            // [ ] !! ISSUE : With this fix though, the custom fn is no longer 
+            //    async. This is an issue because chat module is async
+            //   - There should be no need to change chat , as async allows
+            //       us to multitask with messages