READ BEFORE CREATING A NEW ISSUE/PR #28
Description
If the script doesn't work, the memory addresses are more than likely outdated. Do not create a new issue complaining and do not reach out to me on social media about this.
My CS:GO repositories are meant to serve as an introduction to pymem and to help you understand the basic concepts surrounding external memory manipulation. They are not meant for you to go skid up matchmaking even worse than it already is. I can't control what you do with these repositories so the least I can do is require you to update them yourself to make them work. All issues and pull requests regarding memory addresses will be deleted without notice.
With that in mind, I will not being accepting pull requests whose only contents are updating the variables to the latest memory addresses. It will enable cheating with a low bar to entry, pollute the commit history, and pollute the contributors list with people who have not actually done anything except copy and paste the latest values from elsewhere. I will also not be accepting the umpteenth skiddy web client pulling the latest values from another repository. If you want persistence so badly, create a PR with pattern scanning (which is a feature of pymem) and I'll be more than happy to accept that.
I will accept issues for game updates like 921462f when the glow structure update broke the script.