Added ReadMe´s

README.md

@@ -0,0 +1,83 @@
+# DISCOCK
+
+DISCOCK is the most advanced Discord Browser Generator.
+
+It is capable of generating Unlocked Tokens for free by Using AI.
+DISCOCK is currently undetected by Discord because its Human Emulation.
+
+You will have to use HQ Proxies/IPs to get unlocked tokens.
+
+## Features
+
+- TokenGenerator on discord.com/register
+- TokenGenerator on discord.com
+- Captcha Tester on hcaptcha.com
+
+## Proxies
+
+
+## Installation
+
+### Installing DISCOCK with Python
+
+```bash
+  git clone https://github.com/Vinyzu/DISCOCK DISCOCK
+  cd DISCOCK
+  pip install -r requirements.txt
+  playwright install
+  python main.py
+```
+
+### Further Requirements
+
+- Windows
+
+- [Git](https://git-scm.com/downloads) (To install Mjolnir)
+- [Pip](https://pip.pypa.io/en/stable/installation/) (To install Mjolnir)
+
+## Using
+
+Type     | Recommended Usage              |
+ :------- | :------------------------- |
+| `Token Generator` | Generating HQ token (sometimes) locked the classic way |
+| `Unclaimed Generator` | Generating Unclaimed, HQ (mostly) unlocked tokens  |
+| `Captcha Tester` | Testing the CaptchaAI on hCaptcha.com |
+
+##### Usages will be updated when Discord fixxes Modes
+
+## Contributing
+
+Contributions are always welcome!
+
+See [Contributing](https://github.com/Vinyzu/DISCOCK/blob/main/contributing.md) for ways to get started.
+
+
+## To the Skids
+
+Hello, skid. I know its in your nature to laboriously copy and paste this project and sell it as yours. And i can´t 100% prevent that. However, legally you aren´t allowed to share your skidded Mjolnir other than the source code. And i know that you give a fuck about Licenses and Copyright, but if you gonna use this code as yours and don´t mark me as the original author, i can assure you that you won´t have a good time selling this ;d.
+
+## Copyright and License
+© [Vinyzu](https://github.com/Vinyzu/)
+
+[GNU GPL](https://choosealicense.com/licenses/gpl-3.0/)
+
+(Commercial Usage is allowed, but source, license and copyright has to made available. Mjolnir does not provide and Liability or Warranty)
+
+## Authors
+
+- [@Vinyzu](https://github.com/Vinyzu)
+
+`If you appreciate this Repository, I would love to see you star and share this. It took a lot of effort and time to code all of those features and i originally planned to sell this project, so I´m "wasting" money for everyone´s fun ;:D.`
+
+
+
+[![mjolnir-discord](https://img.shields.io/badge/Mjolnir_Discord-000?style=for-the-badge&logo=discord&logoColor=white)](https://discord.gg/NurPCR25uX)
+[![my-discord](https://img.shields.io/badge/My_Discord-000?style=for-the-badge&logo=google-chat&logoColor=blue)](https://discordapp.com/users/935224495126487150)
+[![buy-me-a-coffee](https://img.shields.io/badge/Buy_Me_A_Coffee-000?style=for-the-badge&logo=ko-fi&logoColor=brown)](https://ko-fi.com/vinyzu)
+
+
+
+![Version](https://img.shields.io/badge/DISCOCK-v1.0.0-blue)
+![License](https://img.shields.io/badge/License-GNU%20GPL-green)
+![Python](https://img.shields.io/badge/Python-v3.x-lightgrey)
+![Platforms](https://img.shields.io/badge/Platform-win--32%20%7C%20win--64-lightgrey)

changelog.md

@@ -0,0 +1,8 @@
+# Changelog
+
+Every new change will be logged
+
+## v1.0
+```
++ First Commit
+```

contributing.md

@@ -0,0 +1,29 @@
+Contributing
+============
+If you want to contribute to a project and make it better, your help is very welcome. Contributing is also a great way to learn more about social coding on Github, new technologies and and their ecosystems and how to make constructive, helpful bug reports, feature requests and the noblest of all contributions: a good, clean pull request.
+
+### How to make a clean pull request
+
+Look for a project's contribution instructions. If there are any, follow them.
+
+- Create a personal fork of the project on Github.
+- Clone the fork on your local machine. Your remote repo on Github is called `origin`.
+- Add the original repository as a remote called `upstream`.
+- If you created your fork a while ago be sure to pull upstream changes into your local repository.
+- Create a new branch to work on! Branch from `develop` if it exists, else from `master`.
+- Implement/fix your feature, comment your code.
+- Follow the code style of the project, including indentation.
+- If the project has tests run them!
+- Write or adapt tests as needed.
+- Add or change the documentation as needed.
+- Squash your commits into a single commit with git's [interactive rebase](https://help.github.com/articles/interactive-rebase). Create a new branch if necessary.
+- Push your branch to your fork on Github, the remote `origin`.
+- From your fork open a pull request in the correct branch. Target the project's `develop` branch if there is one, else go for `master`!
+- …
+- If the maintainer requests further changes just push them to your branch. The PR will be updated automatically.
+- Once the pull request is approved and merged you can pull the changes from `upstream` to your local repo and delete
+your extra branch(es).
+
+And last but not least: Always write your commit messages in the present tense. Your commit message should describe what the commit, when applied, does to the code – not what you did to the code.
+
+`Source: https://github.com/MarcDiethelm/contributing`