A goofy man trying to learn how to make drivers 🙂

I'm in a bit of a bind. I created my own cheat for CS 2 that include things like esp aimbot, and the cheat itself works fine. However, I'd like to try out the game with Battlaye anti-cheat, but to do that, I need to create a driver. I've spent hours searching forums and YouTube for information, but I only have bits and pieces and don't know where to start. I know that communication needs to happen, but I'm not sure if it should be through shared memory or some other method. Also, what about Run-Time Patching and Stealthy Hooking? I don't fully understand how it all works yet, despite looking through the source code on GitHub for drivers. Does anyone have any tips or links to guides that could help me out?
In the short term: I would like to know more about where to look for information, where to start to understand the principle of operation, and what are the most important things to ensure that the driver is under BE's radar and not detected. Im not asking for done work, but i would be grateful for any help in learning.

There is a YT tutorial (YOUR FIRST KERNEL DRIVER (FULL GUIDE)) by somebody named cazz explaining and demoing how to use / write a kernel driver using IOCTL communication. From what I learned so far, you should stay away from IOCTL calls but it's a starting point.

So r00kie said it, its a like a 3 hour long video and he makes an IOCTL driver from scratch, and the guy is very knowledgeable and explains things in great detail along the way, even if that will not get you passed EAC, BattleEye, or any other Kernel Level A.C. worth its salt, you will start to really grasp the concepts and be able to dive in much further after watching. Whats also interesting is cazz makes his driver for cs2. So definitely worth the look, here is the vid, along with an even better one:

Your first Kernel Driver - By Cazzzzz --->>
[Only registered and activated users can see links. Click Here To Register...]

&

Making A Kernel Cheat - By Null ---->>
[Only registered and activated users can see links. Click Here To Register...]

I would also suggest to grab a book called Windows Internals. It was a big game changer in my coding journey to understand a lot of things which concerned me in the past.