feat(docs): add new argument parser system

Author: Cyberdolfi

docs/docs/usage.md

@@ -4,49 +4,38 @@ sidebar_position: 3
 
 # Usage Overview
 
-ServerRawler is a powerful tool for scanning Minecraft servers, designed for efficiency and flexibility. This section provides a comprehensive guide on how to operate ServerRawler, from starting the crawler to understanding its command-line arguments and interpreting its output.
-
-## Starting ServerRawler
-
-Once ServerRawler is installed and configured, you can initiate its operations. Navigate to the project's root directory in your terminal.
-
-If you prefer to use a custom configuration file, look at the [--config](./usage/arguments/scan) argument.
+This page gives you an overview about all commands and arguments of ServerRawler in the terminal.
+For detailed information about each command and argument, click on the links to navigate to their documentation pages.
 
 ## Command Line Arguments
 
-ServerRawler's behavior can be customized using a variety of command-line arguments. Each argument provides granular control over logging, scanning, IP generation, and more. Click on any argument below for detailed information and examples.
-
 :::tip
-For a quick overview of all available commands directly in your terminal, run `ServerRawler --help`.
+For a quick overview of all available commands directly in your terminal, run `./ServerRawler --help`.
 :::
 
 ### General Arguments
 
-* [**`--log`**](./usage/arguments/log): Set the threshold for console output.
-* [**`--no-database`**](./usage/arguments/no-database): Prevent data from being saved to the database.
-* [**`--max-network-tasks`**](./usage/arguments/max-network-tasks): Define the maximum concurrent network operations.
-* [**`--config`**](./usage/arguments/config): Specify a custom configuration file.
-
-### Utility & Debugging Arguments
-
-* [**`--ping`**](./usage/arguments/ping): Perform a Server List Ping (SLP) check.
-* [**`--query`**](./usage/arguments/query): Retrieve detailed server info via Query protocol.
-* [**`--join`**](./usage/arguments/join): Simulate a player login for authentication/whitelist checks.
-* [**`--convert-image`**](./usage/arguments/convert-image): Convert Base64 strings to image files.
-* [**`--generate-ips`**](./usage/arguments/generate-ips): Generate random IPv4 addresses and save them to a file.
-* [**`--cidr`**](./usage/arguments/cidr): Configure an IP range for generation or scanning.
+- [**`--log`**](./usage/arguments/log): Set the threshold for console output.
+- [**`--no-database`**](./usage/arguments/no-database): Prevent data from being saved to the database.
+- [**`--config`**](./usage/arguments/config): Specify a custom configuration file.
+- [**`--cidr`**](./usage/arguments/cidr): Configure an IP range for IP generation.
 
-### Scanning & Crawling Arguments
+### Commands
 
-* [**`--crawl`**](./usage/arguments/crawl): Start a continuous crawling loop for discovering servers.
-* [**`--scan`**](./usage/arguments/scan): Scan IP addresses from a text file.
+- [**`ping`**](./usage/commands/ping): Perform a Server List Ping (SLP) check.
+- [**`query`**](./usage/commands/query): Retrieve detailed server info via Query protocol.
+- [**`join`**](./usage/commands/join): Simulate a player login for authentication/whitelist checks.
+- [**`convert-img`**](./usage/commands/convert-image): Convert Base64 strings to image files.
+- [**`generate`**](./usage/commands/generate-ips): Generate random IPv4 addresses and save them to a file.
+- [**`crawl`**](./usage/commands/crawl): Start a continuous crawling loop for discovering servers.
+- [**`scan`**](./usage/commands/scan): Scan IP addresses from a text file.
 
 ## Output
 
 ServerRawler provides real-time feedback through console logs, indicating its progress, any discovered servers, and errors encountered.
 
-* Successfully discovered server data, if database saving is enabled, will be stored in your configured PostgreSQL database.
-* Logs are color-coded to easily distinguish between information, warnings, errors, and successes.
+- Successfully discovered server data, if database saving is enabled, will be stored in your configured PostgreSQL database.
+- Logs are color-coded to easily distinguish between information, warnings, errors, and successes.
 
 ## Usage Examples
 

docs/docs/usage/arguments/cidr.md

@@ -1,35 +1,40 @@
 ---
-sidebar_position: 9
+title: --cidr - Argument
 ---
 
-# `--cidr`
+# `--cidr` - Argument
 
-**Long**: `--cidr`
+- **Long**: `--cidr`
 
-Configures an IP range in CIDR (Classless Inter-Domain Routing) format to restrict the scope of IP generation (`--generate-ips`) or crawling (`--crawl`) operations. This allows focusing on specific networks or segments.
+## Description
 
-:::info
-CIDR notation specifies an IP address and a prefix length, indicating the number of bits in the IP address that represent the network prefix. For example, `192.168.1.0/24` covers all IP addresses from `192.168.1.0` to `192.168.1.255`.
+Configures an IP range in CIDR (Classless Inter-Domain Routing) format to restrict the scope of IP generation oprations. This allows focusing on specific networks or segments.
+
+:::info[What is CIDR?]
+CIDR (Classless Inter-Domain Routing) is a method for allocating IP addresses and routing Internet Protocol packets. It replaces the older system based on classes A, B, and C. CIDR notation is a compact representation of an IP address and its associated network mask. It consists of an IP address, followed by a slash (`/`), and then a number that indicates the length of the network prefix in bits. For example, `192.168.1.0/24` covers all IP addresses from `192.168.1.0` to `192.168.1.255`.
 :::
 
 ## Usage
 
 ```bash
-ServerRawler --cidr <IP_RANGE>
+./ServerRawler <Command> --cidr <IP_RANGE>
 ```
 
-*   `<IP_RANGE>`: The IP range in CIDR format (e.g., `192.168.1.0/24`, `10.0.0.0/8`).
+- `<Command>`: Any command that uses IP generation
+  - [`generate`](/usage/commands/generate.md)
+  - [`crawl`](/usage/commands/crawl.md)
+- `<IP_RANGE>`: The IP range in CIDR format (e.g., `192.168.1.0/24`, `10.0.0.0/8`).
 
 ## Examples
 
-To generate random IPs exclusively within the `172.16.0.0/16` range:
+To generate random IPs exclusively within the `1.1.1.0/16` range:
 
 ```bash
-ServerRawler --generate-ips private_network.txt 1000 --cidr 172.16.0.0/16
+./ServerRawler generate cloudflare_network.txt 1000 --cidr 1.1.1.0/16
 ```
 
 To start a crawling loop that only targets servers within the `8.8.8.0/29` range:
 
 ```bash
-ServerRawler --crawl --cidr 8.8.8.0/29
+./ServerRawler crawl --cidr 8.8.8.0/29
 ```

docs/docs/usage/arguments/config.md

@@ -1,38 +1,41 @@
 ---
-sidebar_position: 12
+title: --config - Argument
 ---
 
-# `--config`
+# `--config` - Argument
 
-**Short**: `-c`
+- **Short**: `-c`  
+- **Long**: `--config`
 
-**Long**: `--config`
+## Description
 
-Specifies the path to a custom configuration file (e.g., `config.toml`). This allows users to manage settings such as database connections and crawler parameters separately from environment variables or default settings.
+Specifies the path to custom configuration files for ServerRawler. This allows you to use your own configuration settings instead of the config/ folder in the root directory of your project. (Where you run ServerRawler from)
 
-:::info
-Using a dedicated configuration file is recommended for managing complex deployments or specific operational profiles.
+:::warning[Important]
+The path you specify with the `--config` argument is the directory where the folder `config` is located, not the path to the configuration files itself.
+For example, if your configuration files are located in `path/to/your/custom_config_folder/config`, you should specify `--config path/to/your/custom_config_folder` as the argument.
 :::
 
 ## Usage
 
 ```bash
-ServerRawler --config <PATH_TO_CONFIG_FILE>
-ServerRawler -c <PATH_TO_CONFIG_FILE>
+ServerRawler --config <PATH_TO_CONFIG_FOLDER>
+ServerRawler -c <PATH_TO_CONFIG_FOLDER>
 ```
 
-* `<PATH_TO_CONFIG_FILE>`: The absolute or relative path to your `config.toml` file.
+- `<PATH_TO_CONFIG_FOLDER>`: The absolute or relative path to your custom configuration folder.
+
 
 ## Examples
 
-To run ServerRawler using a configuration file named `my_custom_config.toml` located in the current directory:
+To run ServerRawler using a custom configuration folder located at `my_custom_config_folder` in the current directory:
 
 ```bash
-ServerRawler --config my_custom_config.toml
+./ServerRawler --config my_custom_config_folder
 ```
 
-To run ServerRawler with a configuration file located at a specific absolute path:
+To run ServerRawler with a configuration folder located at a specific absolute path:
 
 ```bash
-ServerRawler -c /etc/serverrawler/production.toml
+./ServerRawler -c /etc/serverrawler/production_config_folder
 ```