4.4 KiB
Usage
Kawari is designed to be easy to run, with the goal of being accessible to anyone who wants to run a local server for themselves.
Note: Persisted data (logins, characters, etc) is not stable or secure. Treat all data as disposable.
Copyright Notice
Kawari requires that you have an active subscription, and are in possession of a legitimate copy of the game. Kawari is not related or affiliated to SqEx, and by using it you are in explicit violation of the User Agreement (Limitation 2.4.)
Prerequisites
- Windows or Linux
- Copy of the game updated to the supported game version (see README)
- Oodle Network Compression (can be obtained from here)
Download Artifact
Windows and Linux artifacts are built on every commit, under Github Actions. You will have to download the Oodle Network .dll (Windows) or .so (Linux) yourself however.
Building
Build Kawari with cargo build.
For the World server to function, Kawari needs to be built with --features oodle. Place the .so (Linux) or .lib (Windows) into the oodle directory when building. The library must be named "oodle-network-shared".
Setup
Afterwards, create a config.yaml in the current directory. Currently the minimal config you need to run most services looks like this:
game_location: pathtogamedir
More configuration options can be found in config.rs, such as changing the ports services run on. Finally, run Kawari with the helper script:
$ ./run.sh
Reverse proxy setup
Kawari is useless if it's not behind a domain or other address accessible to a launcher. Even something like Caddy is good enough, and we provide an example setup in the root of the repository.
$ caddy run
This Caddyfile hosts several domains, most notably ffxiv.localhost, on port 80. If you get a "permission denied" error starting Caddy, you must either start Caddy with elevated privileges or set the CAP_NET_BIND_SERVICE capability. See here for more information on how to do this.
Logging in
Astra
Astra is the only launcher known to fully implement the login process, and it requires compiling the unreleased master branch. If you don't know what any of that means, then wait for a new release of Astra before trying Kawari.
- Enable "Developer Settings" under "General".
- Under "Developer Settings", enter the addresses of your servers in the section indicated below. If you used the default Caddy setup, tapping the "Set to localhost" button will fill these fields for you with the correct addresses.
- In "Game Server" and "Game Server Port", set it to "127.0.0.1" and "7000" respectively. This is the address and port of your Lobby server.
Any username and password combination will work, as there is no actual login database yet. In the client, make sure to select the Aether data center.
Manual
Advanced users can specify required command line arguments directly to the game executable. This skips most of the Kawari login process and should only be used if you know what you're doing. Right now, the lobby server does not check for authentication, but in the future you must complete the login process manually to get a valid session ID.
In this example, lobby number 4 will replace the Aether data center, but the other data centers will still try (and fail) to connect.
DEV.LobbyHost04=127.0.0.1DEV.LobbyPort04=7000DEV.TestSID=0(this must be a valid session ID in the future)
Some other launchers (like XIVLauncher) will allow you to specify these extra arguments, but they will still authenticate to the retail servers. You can still connect to Kawari with this way, but make sure to specify your own session ID, or your retail account's session ID will be sent to the lobby server!
Chat commands
Debug commands
These special debug commands start with ! and are custom to Kawari.
!setpos <x> <y> <z>: Teleport to the specified location!spawnactor: Spawn another actor for debugging!spawnnpc: Spawn an NPC for debugging
GM commands
These GM commands are implemented in the FFXIV protocol, but only some of them are implemented.
//gm teri <id>: Changes to the specified territory//gm weather <id>: Changes the weather