1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
Running an Intensity Engine server
==================================
intensity_server.sh
-------------------
Usage:
intensity_server.sh OLD_LOG_FILENAME HOME_DIR
OLD_LOG_FILENAME is the filename to which output was previously logged.
This is uploaded to the master server on the first run after a crash
(see run_server_forever.sh).
HOME_DIR is the directory for transient files, that are not
part of the main installation. The settings.cfg file goes there,
as do downloaded assets. If not specified, HOME_DIR is equal
to ~/.intensityengine_server on Linux and an appropriate
subdirectory (typically under DOCUMENTS/ etc.) with the name
intensityengine_server in Windows.
run_server_forever.sh
---------------------
Usage:
run_server_forever.sh HOME_DIR LOG_FILE
HOME_DIR is passed to intensity_server.sh, see above for use.
LOG_FILE is the logfile to use, relative to the current directory
(not HOME_DIR - add HOME_DIR/ to the filename if you want it to
be there). Server output will go to that file, and will be saved
in LOG_FILE.old when the server restarts.
run_server_forever.sh is a Bash script that will run the server in
a continuous loop. This is useful as if the server crashes, on
its next run it will place itself in 'standby mode' (during which
it won't load maps until manually repurposed - because perhaps the
last map causes the crash), and it uploads the crash log to the
master server.
Running a local server
======================
If a server instance is started without an instance_id, it places itself
in 'local mode'. In this mode it will only accept a login from the
same machine. That single client can then edit the map using commands
not possible in multiplayer, like heightmap editing.
To start the map on the server, in the server console do
set_map('?', MAP_ASSET_ID)
The first parameter is the activity ID, which is unimportant in local
connections (anything will work there). The second should be the asset
ID of the map you want to load (you can find this by looking on the
master server for the asset - select 'Edit' on that asset, and it
will show the asset details, including the asset ID. It will also
appear in the config.cfg file of the client, if you last uploaded to that asset,
by name 'last_uploaded_map_asset').
To connect using the client, first login to the master. Then select
'local connection...' from the menu,
or do '/' to start entering a command, and enter
/connect 127.0.0.1 28787
If you changed the port from 28787, enter the correct port. If
you changed the port, you will need to connect manually using
the /connect command instead of the menu option.
Note that clients should connect *after* calling set_map.
|