The Server panel runs the GoMMO server your project is linked to, so you can install a change and walk into it in the game without leaving Studio.
Server folder
Under Server folder, the panel shows the folder linked to the project. Link a folder… picks it: choose the folder that holds the game server's settings.ini. Open folder shows it in Explorer.
With a map open, the map loads the server's objects straight away, as linking on the inspector's Server tab does; otherwise they arrive with the next map you open. See Linking a server for what a link adds to the map editor.
The game server and the web server
The panel has a section for each: Game server and Web server. Each says which program it runs, the port it uses and where that port was read from. When the folder has no web server, the panel says so; DragonSoul has none.
- Start runs it from the server's own folder, in the background. Its output goes to a log in the project's
logsfolder. - Stop asks it to save and shut down. If it is still running after 35 seconds, Studio ends it.
- Start both and Stop both do the two at once.
- The status line says whether it is stopped, running (with its process number and how long for), stopping, or has exited and with what code.
- While the game server runs, the panel shows how many players are connected, every two seconds.
The web server runs your game's control panel for this PC only, always over plain HTTP, on the port GoMMO Manager's settings give it (8080 when they set none). While it runs, Open http://localhost:8080/ in the browser (with your port) opens it.
Which servers Studio starts and stops
Studio only ever stops a server it started itself, and closing Studio stops the servers it started.
Start checks only the linked server's own port. If something already answers on it, Start refuses and the panel says Already running (not started by Studio), so two servers never fight over one port. A server of the same game running from another folder on other ports does not count, and both can run side by side.
Stop reaches only the server in the linked folder, so another install of the same game on this PC keeps running. A server from a release older than this Studio listens only for the game's shared shutdown signal, which every server of that game on this PC also listens for. Stopping one of those stops every server of the same game on this PC, whichever folder it runs from.
Player counts
The count comes from the linked server itself:
- RF Online and DragonSoul answer on their launcher port: the game port plus one on every RF Online version, and the launcher port DragonSoul's
settings.inisets. - Gate to Heavens and World of Kung Fu answer on a fixed stats port on this PC, which every install of the game uses. So does DragonSoul when its launcher port is off.
Studio takes a count from a fixed port only when the program on it is the linked server. A second install of the same game on this PC cannot open that port, so its count shows as unknown and the panel names the program that holds the port. The same happens to a DragonSoul install whose launcher port another install already holds.
The logs
Open log opens the full log file, and the panel shows the last lines of each log as they arrive.
The game client
Open the client folder shows the client open in Studio in Explorer.
When the server folder belongs to a GoMMO developer checkout, which has a client launch script for each game, the panel shows Launch the client. It runs that script in a new window, pointed at the client open in Studio. A server from a release download has no such script: start the game with its own launcher, because each game hands its client the server address its own way.
Test in game
Test in game, in the top bar, the File menu and this panel, does the whole round trip in one click.
Above the button, choose what it installs:
- Only … the map or document in focus: the map you are editing, or the script, NPC dialog, texture or game data you have open.
- Whole project: every edited map, game data table, pack and file the project holds.
The project remembers the choice, separately from the Install dialog's. With a model or the world graph in focus there is nothing to test on its own, so it covers the whole project.
- It works out what Install would write. If anything would block the install, it stops there and says what, and nothing is written.
- If the install replaces client files while the game client is running, it stops and asks you to close the client first, because Windows will not let it replace files the client holds open.
- If the install changes files or records the game server reads only when it starts (game data tables, scripts, dialogs, settings), the server needs a restart: - a server Studio started is restarted after you answer Restart the game server?. The question reads the linked server's player count. With nobody connected it is a plain confirmation. With players on it, it says how many will be disconnected, and when Studio cannot read the count it warns that anyone on it is disconnected. Install and restart goes ahead; Cancel stops with nothing installed; - a server Studio did not start is never restarted. Test in game stops before installing and asks you to stop that server yourself; run it again and it starts the server for you.
- It installs, with the same backups as Install….
- It brings the server up to date. A server that needs it is stopped and started again, and a stopped server is started. On RF Online, a map's spawns, NPCs and portals go into the server's database, and a running server picks them up by itself within a few seconds, so it is not restarted for those.
- It waits up to two minutes for the server to answer, then launches the client the same way as Launch the client. Without a client launch script it opens the client folder for you to start the game with its own launcher.
Each step shows as a message and in the panel's Test in game list. Without a linked server, Test in game installs the client files and then opens the client folder for you to start the game.
Install, then restart
To do it by hand: Stop the server, Install… your project, and Start the server again.