[Bug]: Potential Memory Leak / High Memory Usage on Startup

[GrandpaEJ]

Description:
Hello, I am using Goat-Bot-V2 (v1.5.35) on a Pterodactyl panel environment. I have noticed that the bot's memory usage quickly exceeds the allocated limit, suggesting a potential memory leak or inefficient resource management during startup/runtime.

Environment Details:

• Bot Version: 1.5.35
• Node.js Version: v22.22.1 (Pterodactyl Container)
• RAM Allocated: 512 MiB
• Operating System: Linux (Docker-based)

The Issue:
Even with minimal activity, the memory consumption spikes to 537.38 MiB, exceeding the 512 MiB limit. This causes the container to potentially crash or restart frequently due to Out Of Memory (OOM) errors.

Error/Log Snippet:

npm warn EBADENGINE Unsupported engine {
  package: 'goat-bot-v2@1.5.35',
  required: { node: '18.x', npm: '>=7.0.0' },
  current: { node: 'v22.22.1', npm: '11.12.0' }
}

Note: I am running Node v22 while the package recommends v18. Could this version mismatch be contributing to the heap growth?

Screenshots:

Steps to Reproduce:

1. Start the bot on a 512MB RAM container.
2. Observe the memory usage in the Pterodactyl dashboard.
3. The usage consistently stays above 500MB and grows until the limit is hit.

Expected Behavior:
The bot should ideally run within the 256MB-512MB range for basic operations without leaking memory.