Descriptive issue. "HikariPool-1 - Starting" but never complete.

[lmshsqlc]

Is your feature request related to a problem? Please describe.

I'm always frustrated when I was trying to configure the Server according to ReadMe.md. I was going through the steps, installed and configured the MySQL Server password according to section "1 - Database".
Then configured config.yaml with root password.

Then I saw "Docker" implementation method, so I went "docker compose up --build". (It composes into 2 containers. db as a independent database I guess, and actual maplestory server that connects to db)
The docker compose took the MySQL root password in config.yaml into the container "maplestory", then the HikariPool-1 started but never completes(I guess it tried to connect with the Host's Password but not the db's).

Once I removed the root password in config.yaml (originally for IDE implementation), the Connection Pool successfully initialized.

So the Docker implementation includes MySQL Database itself and maplestory Server itself. Once someone go through the manual and configured the config.yaml with a root password from Host MySQL Server, the Password Config is brought into the docker container, while the docker db is not configured with the same password.

Describe the solution I'd like

A clear and concise description on the tutorial structure. Maybe take Docker Implementation section away from original server implementation procedures. Docker is easy, so someone won't be mislead.

[PeaceHolder]

Hello,

I’m running into a very similar issue when building and running Cosmic via Maven, not Docker.

When launching from my IDE (IntelliJ), the server connects to MySQL successfully. The config is clearly loaded and Hikari initializes normally.

However, when running the packaged JAR (mvn clean package → java -jar Cosmic.jar), MySQL consistently reports:

Access denied for user 'root'@'localhost' (using password: NO)

What’s confusing is that I temporarily hard-coded the password directly in DatabaseConnection.getConfig():

config.setPassword("password");

The runtime behavior did not change. It still logs (using password: NO).

This suggests that the DatabaseConnection code path being executed in the packaged JAR may differ from the one used when running via the IDE, or that some static initialization / configuration loading is happening earlier and overriding the value.

From debugging so far:

• YamlConfig loads config.yaml at class-initialization time
• IDE vs JAR execution clearly differ in behavior despite identical source

If anyone has insight into whether the Maven-built JAR might be using a different classpath or initialization order than IDE runs, I’d appreciate the guidance.