# Cosmic Cosmic is a server emulator for Global MapleStory (GMS) version 83.
Cosmic launched on March 2021. It is based on code from a long line of server emulators spanning over a decade - starting with OdinMS (2008) and ending with HeavenMS (2019).
This is mainly a Java based project, but there are also a bunch of scripts written in JavaScript.
Head developer and maintainer: Ponk.\ Contributors: a lot of people over the years, and hopefully more to come. Big thanks to everyone who has contributed so far!
Join the Discord server where most of the discussions take place: https://discord.gg/JU5aQapVZK
What we are working towards.
Explicitly excluded from the scope of the project.
You may contribute to the project in various ways, mainly through GitHub:
A GitHub Actions pipeline is set up to run the build automatically when a new pull request is opened or commits are pushed to an existing one. This ensures that the code compiles and all the tests pass.
Once a pull request is merged, a tag with the new version is automatically created.
Most GitHub activity is pushed to a Discord channel for visibility. This works by leveraging a webhook. The activity includes (but is not limited to): merged commits, created PRs, comments, and new tags.
The project follows the semantic versioning scheme using git tags.
Follow along as I go through the steps to play the game on your local computer from start to finish. I won't go into extreme detail, so if you don't have prior experience with Java or git, you might struggle.
We will set up the following:
You will start by installing the database server and client, and then run some scripts to prepare it for the server.
1-db_database.sql and ending with 4-db-admin.sql. In HeidiSQL: "File" -> "Run SQL File...".You will start by cloning the repository, then configure the database properties and lastly start the server.
net.server.Server.Below, I list other ways of running the server which are completely optional.
Support for Docker is also provided out of the box, as an alternative to running straight in the IDE. If you have Docker Desktop installed it's as easy as running docker compose up.
Making changes becomes a bit more tedious though as you have to rebuild the server image via docker compose up --build.
On the first launch, the database container will run the scripts which may take so long that the server fails to start. In that case, just wait until the database is done running the scripts and then retry (Ctrl+C and re-run the command).
Another option is to start the server from a terminal by running a jar file. You first need to build the jar file from source which requires Maven.
Building the jar file is as easy as running mvn clean package. The project is configured to produce a "fat" jar which contains all dependencies (by utilizing the maven-assembly-plugin). Note that the WZ XML files are not included in the jar.
To run the jar, a launch.bat file is provided for convenience. Simply double-click it and the server will start in a new terminal window.
Alternatively, run the jar file from the terminal. Just remember to provide the wz-path system property pointing to your wz directory.
You will start by installing the game with the old installer, then overwrite some WZ files with our custom ones, and lastly get the localhost executable in place.
Important note about localhost clients: these executables are red-flagged by antivirus tools as potentially malicious software. This happens due to the reverse engineering methods that were applied onto these software artifacts. The one provided here has been in use for years already and posed no harm so far, so it is assumed to be safe.
The client has started, and you're looking at the login screen.
At this point, you can log in to the admin account using the following credentials:
Or create a regular account by typing in your desired username & password and attempting to log in. This "automatic registration" feature lets you create new accounts to play around with. It is enabled by default (see config.yaml).
Create a new character as you normally would, and then select it to enter the game. Hooray, finally we're in!
If you log in to the "Admin" character, you'll notice that the character looks almost invisible. This is hide mode, which is enabled by default when you log in to a GM character. You won't be visible to normal players and no mobs will move if you're alone on the map. Toggle hide mode on or off by typing "@hide" in the in-game chat.
Hide is one of many commands available to players, type "@commands" to see the full list. Higher ranked GMs have access to more powerful commands.
That's it, have fun playing around in game!
Some slightly more advanced concepts that might be useful once you're up and running.
You don't have to host the server on your local machine to play. It's possible to host on a remote server such as a VPS or even a dedicated server.
I leave it to you to figure out the server hosting part, but once you have that running you'll need to edit the client exe to point to your remote server ip.
WZ files are the asset/data files required by the client and server. Typically, HaRepacker-resurrected is used to handle (view, edit, export) the .wz files.
The client can read the .wz files directly, but the server requires them in XML format. The server also does not make use of the sprites, which is the motivation for different kinds of exporting. HaRepacker allows you to export to "Private server", which is the .img files packaged in the .wz stripped of sprites and converted to XML. This takes much less disk space.
This server requires custom .wz files (unfortunately), as you may have noted during installation of the client. The intention is for these to be removed eventually and to solely run on vanilla .wz files.
Make sure to always export from the client .wz files to the server XML, and not the other way around.
Editing the client .wz without exporting to the server may lead to strange behavior.
For more information about the client and its features, see HeavenMS on GitHub.
Some notable features: