no message
git-svn-id: svn://svn.code.sf.net/p/actiongame/code/trunk/ac@671 e016b1c5-ed68-44aa-a2f7-31cac88cffde
This commit is contained in:
+18
-7
@@ -28,22 +28,33 @@
|
||||
<h2>Readme</h2>
|
||||
|
||||
<p>
|
||||
This readme consists of these sections:
|
||||
Basic sections:
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="docs/getstarted.html">get started</a> - <b>before you play</b>, basics, instructions on running the game</li>
|
||||
<li><a href="docs/game.html">game</a> - information about gameplay, modes, weapons, etc</li>
|
||||
<li><a href="docs/config.html">configuration</a> - commandline-options, settings, scripting</li>
|
||||
<li><a href="docs/misc.html">misc</a> - a few configuration tricks</li>
|
||||
<li><a href="docs/server.html">server</a> - set up your own server, administration</li>
|
||||
<li><a href="docs/history.html">history</a> - changes on this game</li>
|
||||
|
||||
</ul>
|
||||
|
||||
<p>
|
||||
This document will not provide detailed information on the cube engine itself, check out the
|
||||
<a href="http://www.cubeengine.com/readme.html" target="_blank">cube docs</a>,
|
||||
the <a href="http://sauerbraten.org/README.html" target="_blank">sauerbraten/cube2 docs</a> and the following files for further information:
|
||||
Advanced sections:
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li><a href="docs/config.html">config</a> - commandline-options, general config commands, scripting</li>
|
||||
<li><a href="docs/gamecommands.html">game commands</a> - reference of game related commands</li>
|
||||
|
||||
<li><a href="http://cubeengine.com/docs/editing.html" target="_blank">editing</a> - map making tutorial from cubeengine.com</li>
|
||||
<li><a href="docs/editref.html">edit reference</a> - reference of map editing commands</li>
|
||||
<li><a href="docs/history.html">history</a> - changes on this game</li>
|
||||
<li><a href="docs/misc.html">misc</a> - a few configuration tricks</li>
|
||||
</ul>
|
||||
|
||||
|
||||
<p>
|
||||
Check out the following files for further information:
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
|
||||
@@ -0,0 +1,425 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title>ActionCube README</title>
|
||||
<meta http-equiv="content-type" content="application/xhtml+xml;charset=utf-8" />
|
||||
<link rel="stylesheet" href="docs.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div align="center">
|
||||
|
||||
<div id="header">Rabid Viper Productions</div>
|
||||
<div id="main">
|
||||
|
||||
<h2>Configuration</h2>
|
||||
|
||||
|
||||
<a name="commandline"></a>
|
||||
<h3>Command-Line Options</h3>
|
||||
|
||||
<p>
|
||||
-d runs a dedicated server
|
||||
</p>
|
||||
<p>
|
||||
Default is a non-dedicated server with only a single client. Dedicated
|
||||
servers run in the shell only (no graphics), with increased priority yet use very
|
||||
little cpu time & memory, so you can run one in the background, or at the same
|
||||
time with a client if you want to host a game.
|
||||
Server port is fixed at 28763,
|
||||
with 28764 being used for the server info requests (both UDP).
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-wX</span> sets desired screen width to X, default is <span class="code">-w640</span>
|
||||
<br />
|
||||
<span class="code">-hY</span> sets desired screen height to Y, default is <span class="code">-h480</span>
|
||||
<br />
|
||||
<span class="code">-t</span> runs windowed
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-uN</span> sets the server upstream bandwidth to N bytes per second. only set
|
||||
this parameter if you know what you are doing, specifying a wrong value is worse
|
||||
than not specifying it at all.
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-nN</span> sets the server description, for people pinging the server. usually
|
||||
does not need to be set if you have a descriptive domain name already, but if you
|
||||
set it, keep it short as it may otherwise be truncated, i.e. -nBobsInstagibServer
|
||||
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-iIP</span> sets the server ip to IP. this option is only useful for people
|
||||
running on machines with multiple network interfaces.
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-mM</span> sets the master server to use for either server (registering) and
|
||||
client (updating) to M. M is the base url of the master server and has to end in
|
||||
a / and without a http:// prefix, the default is wouter.fov120.com/cube/masterserver/.
|
||||
If you want your server to be private and not report to the masterserver, use -mlocalhost.
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-pPASS</span> sets the server password to PASS. Only clients that use the command
|
||||
"password PASS" will be able to connect.
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-cN</span> sets the maximum number of players that can play on this server
|
||||
to N (default 4). If more players try to connect they will get a "server full" message.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
<span class="code">-xM</span> sets the master password.
|
||||
</p>
|
||||
<p>
|
||||
<span class="code">-rC</span> sets the maprotation file, e.g. <span class="code">-rconfig/maprot.cfg</span>
|
||||
</p>
|
||||
|
||||
|
||||
<a name="generalconsolecommands"></a>
|
||||
<h3>General console commands and configuration</h3>
|
||||
|
||||
<div class="code">
|
||||
bind K A
|
||||
</div>
|
||||
|
||||
binds key K to commands A (see console language below for what you can put in A). To find out what key names and their default bindings are, look at data/keymap.cfg, then add bind commands to your autoexec.cfg.
|
||||
|
||||
<div class="code">
|
||||
alias N A
|
||||
</div>
|
||||
|
||||
binds name N to commands A, after which you can use N as a shortcut for A. You may re-bind N as often as you like, and bind N again within the execution of A etc.
|
||||
|
||||
<div class="code">
|
||||
quit
|
||||
</div>
|
||||
|
||||
quits without asking.
|
||||
|
||||
<div class="code">
|
||||
forward / backward / left / right
|
||||
</div>
|
||||
|
||||
move you in said direction (defaults to cursor keys).
|
||||
|
||||
<div class="code">
|
||||
attack
|
||||
</div>
|
||||
|
||||
fires the current weapon. default = left mouse
|
||||
|
||||
<div class="code">
|
||||
jump
|
||||
</div>
|
||||
|
||||
triggers a jump. default key space & right mouse.
|
||||
|
||||
<div class="code">
|
||||
invmouse B
|
||||
</div>
|
||||
|
||||
sets mouse to "flight sim" mode if B is not 0
|
||||
|
||||
<div class="code">
|
||||
sensitivity S
|
||||
</div>
|
||||
|
||||
sets mouse sensitivity (see autoexec.cfg). with sensitivityscale you can specify a number that the sensitivity is divided by.
|
||||
|
||||
<div class="code">
|
||||
fov N
|
||||
</div>
|
||||
|
||||
sets your FOV to 10..120.
|
||||
|
||||
<div class="code">
|
||||
minmillis N
|
||||
</div>
|
||||
|
||||
Sets the minimum number of milliseconds a frame should take. This is for very fast machines that run Cube at hundreds of fps. Default is 5, i.e. try to stay close to 200fps. This command is not exact, i.e. the precise delay it generates depends on OS and other factors... experiment with your ideal setting. To turn it off, simply set it to 0.
|
||||
|
||||
<div class="code">
|
||||
fog N
|
||||
</div>
|
||||
|
||||
sets fog distance to N (default currently 160). You can do this for tweaking the visual effect of the fog, or if you are on a slow machine, setting the fog to a low value can also be a very effective way to increase fps (if you are geometry limited). Try out different values on big maps / maps which give you low fps.
|
||||
|
||||
<div class="code">
|
||||
fogcolour C
|
||||
</div>
|
||||
|
||||
Sets fog and clearing colour to C, the default being 0x8099B3. This and the fog variable can be set in the map specific .cfg file.
|
||||
|
||||
<div class="code">
|
||||
dynlight R
|
||||
</div>
|
||||
|
||||
determines wether dynamic shadows & lights are rendered, providedjust incase they slow your fps down too much. With radius you can specify the radius of a dynamic light (default 16), smaller to maybe gain some speed (0 is off entirely), or bigger to see the effect of dynamic shadows more dramatically (try shooting it past some pillars that have a dark area on the other side... or use the "gamespeed" variable).
|
||||
|
||||
<div class="code">
|
||||
lighterror E
|
||||
</div>
|
||||
|
||||
Allows you to finetune the amount of "error" the mipmapper/stripifier allow themselves for changing lightlevels. Set to 1 for maximum light quality at the expense of fps, set to some high value to gain fps but with messier lighting (only helps if you are geometry limited). Default = 8. If you change this during play, you have to do a "recalc" to see the effect.
|
||||
|
||||
<div class="code">
|
||||
watersubdiv N
|
||||
</div>
|
||||
|
||||
determines the subdivision of the water surface in maps, which can greatly affect fps on slow machines. Must be a power of 2: 4 is the default, 8 is recommended for people on slow machines, 2 is nice for fast machines, and 1 is quite OTT. See "waterlevel" (edit reference) on how to add water to your own levels.
|
||||
|
||||
<div class="code">
|
||||
maxparticles N
|
||||
</div>
|
||||
|
||||
Sets the maximum number of particles rendered at any one time. If more particles are generated than this number, the oldest ones are culled, so you can safely set this number relatively low without loss of information. default 1000.
|
||||
|
||||
<div class="code">
|
||||
screenshot
|
||||
</div>
|
||||
|
||||
writes out "screenshots/screenshotN.bmp", where N is the number of milliseconds since cube was launched (default key = F12).
|
||||
|
||||
<div class="code">
|
||||
musicvol n<br />
|
||||
soundvol n
|
||||
</div>
|
||||
|
||||
sets the music/sound volume from 0 to 255
|
||||
|
||||
<div class="code">
|
||||
soundbufferlen n
|
||||
</div>
|
||||
|
||||
(default 512) tweak this if you experience stuttering or lagging sound
|
||||
|
||||
<div class="code">
|
||||
gamma n
|
||||
</div>
|
||||
|
||||
sets the hardware gamma value to n percent (default 100). May not work if your card/driver doesn't support it.
|
||||
|
||||
<div class="code">
|
||||
hidestats b
|
||||
</div>
|
||||
|
||||
turns on/off display of fps/rendering stats on the HUD (default = 1).
|
||||
|
||||
<div class="code">
|
||||
maxroll n
|
||||
</div>
|
||||
|
||||
sets the maximum value your display will roll on strafing (0..20, default = 3)
|
||||
|
||||
<div class="code">
|
||||
crosshairsize n
|
||||
</div>
|
||||
|
||||
sets the size of your crosshair, 0 being off (default = 3)
|
||||
|
||||
<div class="code">
|
||||
crosshairfx b
|
||||
</div>
|
||||
|
||||
turns on or of crosshair effects (default 1). when on, the crosshair will go grey when the weapon is reloading, orange when health <= 50, or red when <=25.
|
||||
|
||||
<div class="code">
|
||||
exec C
|
||||
</div>
|
||||
|
||||
executes all commands in config file C.
|
||||
|
||||
<div class="code">
|
||||
newmenu N
|
||||
</div>
|
||||
|
||||
creates a new menu with name N. All following menuitem commands will apply to this menu
|
||||
|
||||
<div class="code">
|
||||
menuitem N A<br />
|
||||
menuitem A
|
||||
</div>
|
||||
|
||||
creates a new menuitem with description N and action A. if you only specify 1, then it will be used for both the description and the action. See data/menus.cfg for examples.
|
||||
|
||||
<div class="code">
|
||||
showmenu N
|
||||
</div>
|
||||
|
||||
displays the menu with name N previously defined, and allows the user to pick an item with the cursor keys. Upon pressing return, the associated action will be executed. pressing ESC will cancel the menu.
|
||||
|
||||
<div class="code">
|
||||
history N
|
||||
</div>
|
||||
|
||||
Executes the Nth command in the command line history. For example, binding "history 0" to a key allows you to quickly repeat the last command typed in (useful for placing many identical entities etc.)
|
||||
|
||||
<div class="code">
|
||||
keymap K N A
|
||||
</div>
|
||||
|
||||
sets up the keymap for key code K with name N and default action A. You should never have to use this command manually, use "bind" instead.
|
||||
|
||||
<div class="code">
|
||||
lightscale N
|
||||
</div>
|
||||
|
||||
used to finetune the "overbright lighting" rendering feature when enabled: lower numbers make the scene brighter, default = 4. After changing this value, you need to use "recalc" to see the differences.
|
||||
|
||||
<div class="code">
|
||||
particlesize P
|
||||
</div>
|
||||
|
||||
<p>
|
||||
scales all particles by percentage P.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
To use overbright lighting, your card needs to support the "EXT_texture_env_combine" extension (Nvidia from TNT1 and upwards, ATI from rage128/radeon and upwards, but not on voodoos afaik). Overbright lighting uses a different lighting model (lights that overlap "add" rather use the biggest of the two, and lightsources have an exponential rather than linear model), so lighting may look different depending on how the mapper placed the lights. Maps should be made with additive/exponential lighting in mind, however, because soon everyone will have a card that supports this extension.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
Do not confuse "lightscale" with "gamma", they have different effects. It is best to leave "lightscale" at the default and tune gamma to get the right brightness level for your situation, but you can tune the other way around if you find the saturation level of a certain gamma level more important. changing the lightscale will have an effect on the distribution of lightsources (higher lightscale will make them more like spotlights). Generally, gamma needs to be lower compared to older cube releases.
|
||||
</p>
|
||||
|
||||
<h3>Console Language</h3>
|
||||
|
||||
<p>
|
||||
Cube's console language is similar to console languages of other games (e.g. Quake), but is a bit more powerful in
|
||||
that it is almost a full programming language.
|
||||
</p>
|
||||
|
||||
<p>
|
||||
What is similar to quake is the basic command structure: commands consist of the command itself, followed by any
|
||||
number of arguments seperated by whitespace. you can use "" to quote strings with whitespace in them (such as the
|
||||
actions in bind/alias), and whereever a command is required you can also use ; to sequence multiple commands in one.
|
||||
</p>
|
||||
<p>
|
||||
What is new compared to quake is that you can evaluate aliases and expressions. You can substitute the value of an
|
||||
alias as an argument by prefixing it with a "$" sign, i.e.: <span class="code">echo The current value of x is $x</span>
|
||||
You can even substitute
|
||||
the values of console variables this way, i.e $fov gives the current fov. Some aliases are set automatically, for
|
||||
example $arg1 to $argN are set if you supply arguments when you execute an alias.
|
||||
</p>
|
||||
<p>
|
||||
There are two alternative ways to "" to quote a string: () and []. They work in the same way as "", with the difference
|
||||
that they can be nested infinitely, and that they may contain linefeeds (useful for larger scripts). () is different
|
||||
from [] in that it evaluates the commands contained in it _before_ it evaluates the surrounding command, and substitutes
|
||||
the results. () bracketed strings are called expressions, and combined with some commands made especially for
|
||||
"programming", you have a minimal language:
|
||||
</p>
|
||||
|
||||
<div class="code">
|
||||
+ A B<br />
|
||||
- A B<br />
|
||||
* A B<br />
|
||||
div A B<br />
|
||||
mod A B<br />
|
||||
</div>
|
||||
|
||||
(add, substract, multiply, divide, modulo): these all work like the integer operators from other languages. <br />
|
||||
Example: <span class="code">echo x squared is (* $x $x)</span>
|
||||
|
||||
<div class="code">
|
||||
= A B<br />
|
||||
< A B<br />
|
||||
> A B<br />
|
||||
strcmp A B<br />
|
||||
</div>
|
||||
|
||||
(equals, lessthan, greaterthan, stringcompare): comparison operators that return 1 for true and 0 for false.
|
||||
|
||||
<div class="code">
|
||||
if cond true false
|
||||
</div>
|
||||
|
||||
executes the true or false part depending on wether cond is "0" or something else. <br />
|
||||
Example: <span class="code">if (< $x 10) [ echo x is $x ] [ echo x is too big ]</span>
|
||||
|
||||
<div class="code">
|
||||
loop N body
|
||||
</div>
|
||||
|
||||
evaluates body N times, and sets the alias "i" from 0 to N-1 for every iteration. <br />
|
||||
Example: <span class="code">loop 10 [ echo $i ]</span>
|
||||
|
||||
<div class="code">
|
||||
while cond body
|
||||
</div>
|
||||
|
||||
evaluates body while cond evaluates to true. Note that cond here has to have [], otherwise it would only be evaluated once.<br />
|
||||
Example (same as the loop): <span class="code">alias i 0; while [ (< $i 10) ] [ echo $i; alias i (+ $i 1) ]</span>
|
||||
|
||||
<div class="code">
|
||||
concat S...
|
||||
</div>
|
||||
|
||||
concatenates all the arguments into alias "s"
|
||||
|
||||
<div class="code">
|
||||
concatword S...
|
||||
</div>
|
||||
|
||||
same as concat but without spaces between the elements.
|
||||
|
||||
<div class="code">
|
||||
at S N
|
||||
</div>
|
||||
|
||||
grabs the Nth word out of string S and puts it into alias "s"
|
||||
|
||||
<div class="code">
|
||||
onrelease A
|
||||
</div>
|
||||
|
||||
only executes A if the command is executed on the release of a key/button (must be in an action in a bind or an alias in a bind).
|
||||
|
||||
<div class="code">
|
||||
sleep N C
|
||||
</div>
|
||||
|
||||
executes command C after N milliseconds have passed. only one command can be sleeping at any one time. gets reset at map load.
|
||||
|
||||
<div class="code">
|
||||
(millis)
|
||||
</div>
|
||||
|
||||
returns the number of milliseconds since engine start.
|
||||
|
||||
variables that are only really useful when used as value:
|
||||
|
||||
<div class="code">
|
||||
$editing
|
||||
</div>
|
||||
|
||||
true when in edit mode
|
||||
|
||||
<div class="code">
|
||||
$flrceil
|
||||
</div>
|
||||
|
||||
<p>
|
||||
0 when the player looks at the floor, and 2 when looking at the ceiling.
|
||||
</p>
|
||||
|
||||
<h3>How The Cube Engine Works</h3>
|
||||
|
||||
<p>
|
||||
The cube engine is simplicity itself. The whole map consists of a large 2D array of "cubes", each with a floor and ceiling height, textures (for floor/ceiling/wall) and other properties. These cubes are grouped 2x2 at a time recursively into a "quad tree", which is used hold bigger cubes which can be rendered faster. For those who have edited doom, this is very similar to having a lot of square sectors but at overlapping sizes. This is results in a map that can have no room over room (yet), and is pretty cubic, except for the odd slope/slant here and there.
|
||||
</p>
|
||||
<p>
|
||||
The floor size of a single unit (single cube) is similar to about 16x16 units in games such as doom & quake, so a staircase step is usually 1 unit, a wall 8 units high etc.
|
||||
</p>
|
||||
<p>
|
||||
Cube renders this world by first determining which cubes are visible using a "dynamic occlusion culling" algorithm and frustrum culling. You can see the effect of this when you switch to edit mode (E), and then fly out above a map: you'll see parts of the map dropping away as you move. The remaining cubes are then rendered in their most efficient size (i.e. cube will render a mixture of 1x1 2x2 4x4 etc. size cubes, depending on wether they have the same properties: height, texturing etc.).
|
||||
</p>
|
||||
<p>
|
||||
If you are on a fast machine, or you are playing a simple/small map, cube will simply render all of these visible cubes (this is indicated by LOD at its maximum of 250 on the hud). Cube can however make complex maps run fast even on slower computers by a technique called LOD: this will render cubes that are further away using bigger approximations (2x2 and up), even the properties of the constituent cubes don't match exactly. This reduces the amount of polys to be rendered tremendously, and thus allows even slow machines to have a consistent frame rate (cube will adapt the LOD figure every frame to aim for the fps you specify). The downside is of course that if the approximations are visible closeup, this can lead to ugly graphical glitches (this is called "popup" because it changes as you move). So in the end the choice is up to you: good fps or constant visual quality (most engines only cater for the latter).
|
||||
</p>
|
||||
|
||||
</div>
|
||||
<div id="footer"><a href="../README.html">← BACK TO MAIN SITE</a></div>
|
||||
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -0,0 +1,396 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title>ActionCube README</title>
|
||||
<meta http-equiv="content-type" content="application/xhtml+xml;charset=utf-8" />
|
||||
<link rel="stylesheet" href="docs.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div align="center">
|
||||
|
||||
<div id="header">Rabid Viper Productions</div>
|
||||
<div id="main">
|
||||
|
||||
<h2>Map Editing Reference</h2>
|
||||
|
||||
<div class="code">
|
||||
edittoggle
|
||||
</div>
|
||||
|
||||
switches between map edit mode and normal (default key = e). In map edit mode you can select bits of the map by clicking or dragging your crosshair on the floor or ceiling (using the "attack" command, normally MOUSE1), then use the commands below to modify the selection. While in edit mode, physics & collision don't apply (noclip), and key repeat is ON. Note that if you fly outside the map, cube still renders the world as if you were standing on the floor directly below the camera.
|
||||
|
||||
<div class="code">
|
||||
edittex T D
|
||||
</div>
|
||||
|
||||
Changes the texture on current selection by browsing through a list of textures directly shown on the cubes. T is an integer denoting the type (floor = 0, lower or wall = 1, ceiling = 2, upper wall = 3), D is the direction you want to cycle the textures in (1 = forwards, -1 = backwards). Default keys are the six keys above the cursor keys, which each 2 of them cycle one type (and numpad 7/4 for upper).
|
||||
|
||||
The way this works is slightly strange at first, but allows for very fast texture assignment. All textures are in 3 individual lists for each type (both wall kinds treated the same), and each time a texture is used, it is moved to the top of the list. So after a bit of editing, all your most frequently used textures will come first when pressing these keys, and the most recently used texture is set immediately when you press the forward key for the type. These lists are saved with the map. make a selection (including wall bits) and press these keys to get a feel for what they do.
|
||||
|
||||
<div class="code">
|
||||
editheight T D
|
||||
</div>
|
||||
|
||||
T is the type as above (floors & ceilings only), and D is the delta value to move it in. Default keys are [ and ] for floor level, and o/p for ceiling.
|
||||
|
||||
<div class="code">
|
||||
solid B
|
||||
</div>
|
||||
|
||||
makes the current selection all solid (i.e. wall) if B is true (non-zero), or all non-solid if it is false (0). This operation retains floor/ceiling heights/textures while swapping between the two. Default keys f and g respectively.
|
||||
|
||||
<div class="code">
|
||||
equalize T
|
||||
</div>
|
||||
|
||||
levels the floor/ceiling of the selection (T as above). default keys , and .
|
||||
|
||||
<div class="code">
|
||||
heightfield T
|
||||
</div>
|
||||
|
||||
marks the current selection as a heightfield, with T being floor or ceiling, as above. A surface marked as heightfield will use the vdelta values (see below) of its 4 corners to create a sloped surface. To mark a heightfield as normal again (ignoring vdelta values, set or not) use "solid 0". Default keys are h (floor) and i (ceiling).
|
||||
|
||||
Heightfields should be made the exact size that is needed, not more not less. The most important reason for this is that cube automatically generates "caps" (side-faces for heightfields) only on the borders of the heighfield. This also means if you have 2 independant heightfields accidentally touch eachother, you will not get correct caps. Also, a heighfield is slightly slower to render than a non-heighfield floor or ceiling. Last but not least, a heightfield should have all the same baseheight (i.e. the height determined by a normal editheight operation) to get correct results.
|
||||
|
||||
<div class="code">
|
||||
vdelta N
|
||||
</div>
|
||||
|
||||
changes the vdelta value of the current selection by N. Note that unlike all other editing functions, this function doesn't affect a cube, but its top-left vertex (market by the dot in the editing cursor). So to edit a N * M heightfield, you will likely have to edit the vdelta of (N+1) * (M+1) cubes, i.e. you have to select 1 row and 1 column more in the opposite direction of the red dot to affect all the vertices of a heightfield of a given size (try it, it makes sense :)
|
||||
|
||||
A floor delta offsets vertices to beneath the level set by editheight (and a ceil delta to above). Delta offsets have a precision of a quarter of a unit, however you should use non-unitsize vertices only to touch other such vertices. Default keys are 8 and 9 to decrease/increase the vdelta.
|
||||
|
||||
<div class="code">
|
||||
corner
|
||||
</div>
|
||||
|
||||
# makes the current selection into a "corner". Currently there is only one type of corner (a 45 degree one), only works on a single unit (cube) at a time. It can be positioned: next to 2 solid walls
|
||||
# in the middle of 2 higher floorlevels and 2 lower ones forming a diagonal (and similar with ceiling)
|
||||
|
||||
In both cases, the corner will orient itself automatically depending on its neighbours, behaviour with other configurations than the 2 above is unspecified. Since the latter configuration generates possibly 2 floor and 2 ceiling levels, up to 4 textures are used: for example for the 2 floors the higher one will of the cube itself, and the lower one of a neighbouring low cube. Default key = k you can make bigger corners at once by pressing "corner" on grid aligned 2x2/4x4/8x8 selections, with equal size solid blocks next to them.
|
||||
|
||||
<div class="code">
|
||||
undo
|
||||
</div>
|
||||
|
||||
multi-level undo of any of the changes caused by the above operations (default key = u).
|
||||
|
||||
<div class="code">
|
||||
undomegs N
|
||||
</div>
|
||||
|
||||
sets the number of megabytes used for the undo buffer (default 1). undo's work for any size areas, so the amount of undo steps per megabyte is more for small areas than for big ones (a megabyte fits 280 undo steps on a 16x16 area, but only 4 steps on a 128x128 area).
|
||||
|
||||
<div class="code">
|
||||
copy
|
||||
|
||||
paste
|
||||
</div>
|
||||
|
||||
copy copies the current selection into a buffer. to paste it back requires a same size selection at the destination location. If it is not the same size the selection will be resized automatically prior to the paste operation (with the red dot as anchor), which is easier for large selections. (default keys are c and v respectively).
|
||||
|
||||
<div class="code">
|
||||
replace
|
||||
</div>
|
||||
|
||||
repeats your last texture edit thruout the map. The way it works is intuitive: simply edit any texture anywhere, then using "replace" will replace all textures thruout the map in the same way (taking into account wether it was a floor/wall/ceil/upper too). if the there was more than one "old" texture in your selection, the one nearest to the red dot is used. This operation can't be undone.
|
||||
|
||||
<div class="code">
|
||||
newent type value1 value2 value3 value4
|
||||
</div>
|
||||
|
||||
<p>
|
||||
adds a new entity where (x,y) is determined by the current selection (the red dot corner) and z by the camera height, of said type. Type is a string giving the type of entity, such as "light", and may optionally take values (depending on the entity):
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
<div class="code">
|
||||
"light" radius brightness<br />
|
||||
"light" radius r g b
|
||||
</div>
|
||||
|
||||
radius in units (1..32), optionally brightness (1..255) for a white light, or coloured light (each component 1..255). Default key l creates a new light (cylindrical) of radius 16, brightness 255 (white).
|
||||
</li>
|
||||
|
||||
|
||||
<li>
|
||||
<div class="code">
|
||||
"playerstart"
|
||||
</div>
|
||||
|
||||
Spawn spot, yaw is taken from the current camera yaw.
|
||||
</li>
|
||||
<li>
|
||||
<div class="code">
|
||||
"shells", "bullets", "rockets", "riflerounds", "health",
|
||||
"healthboost", "greenarmour", "yellowarmour", "quaddamage"
|
||||
</div>
|
||||
|
||||
A variety of pickup-able items, see here.
|
||||
</li>
|
||||
<li>
|
||||
<div class="code">
|
||||
"teleport" N
|
||||
"teledest" N
|
||||
</div>
|
||||
|
||||
creates a teleport connection, teleports are linked to a teledest with the same N (of which there should be exactly one). N can be 0..255. The teledest uses the current camera yaw.
|
||||
</li>
|
||||
<li>
|
||||
<div class="code">
|
||||
"mapmodel" N Z T
|
||||
</div>
|
||||
|
||||
A map model, i.e. an object rendered as md2 which you collide against but has no behaviour/movement. N determines which mapmodel you want, which is defined by the "mapmodel" command, see below. yaw of the model is taken from the current camera yaw (snapped to 15 degree increments). Z determines extra elevation above the default (usually the ground). T is the map texture to use (see data/default_map_settings.cfg for the number), if left as 0 then the skin.jpg in the model directory is used (if present). Mapmodels are more expensive than normal map geometry, do not use insane amounts of them to replace normal geometry.
|
||||
</li>
|
||||
<li>
|
||||
<div class="code">
|
||||
"monster" N
|
||||
</div>
|
||||
|
||||
A monster, currently N = 0..4 (see gameplay docs). Monster entities will be spawned when in classic single player mode, and will attack you when you come into view. yaw is taken from the current camera yaw.
|
||||
</li>
|
||||
<li>
|
||||
<div class="code">
|
||||
"trigger" N T O
|
||||
</div>
|
||||
|
||||
<p>
|
||||
A trigger of type T affecting all cubes with tag N when triggered in game (see "edittag" on how to set tags on cubes). Triggers are rendered as a carrot which, when "eaten", trigger an event (only once). The following trigger types are available:
|
||||
</p>
|
||||
|
||||
<ul>
|
||||
<li>
|
||||
0: On being triggered, sets all target cubes to SPACE. This has the effect of instantly opening doors or other geometry. You edit these "doors" as SPACE, i.e. you determine what the "door" looks like when opened, they are then set to SOLID automatically when playing (map start / edit toggle). Current "doors" open instantly. "rumble" sound alerts the player something has opened.
|
||||
</li>
|
||||
<li>
|
||||
1: invisible: same as 0 but without the carrot. since the trigger radius is fairly small, be sure to place them in tiny hallways and other areas you are sure the player will pass through.
|
||||
</li>
|
||||
<li>
|
||||
2: end of map marker. ends the map and triggers the intermission. carrot spins wildly.
|
||||
</li>
|
||||
<li>
|
||||
3: same as 1, but makes no rumble sound.
|
||||
</li>
|
||||
<li>
|
||||
4: same as 0, but with switch model instead of carrot (O is orientation, 0..3)
|
||||
</li>
|
||||
<li>
|
||||
5: same as 0, but with lever model instead of carrot (O is orientation, 0..3)
|
||||
</li>
|
||||
</ul>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>
|
||||
Scripting: each trigger automatically executes the alias "level_trigger_N" where N is the trigger number. This means you can add any scripting you can do through the available commands, by simply putting aliases of this kind in the level .cfg file. For example, to print a message when the user hits trigger 1:
|
||||
</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>
|
||||
alias level_trigger_1 "echo A door opened nearby"
|
||||
</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>
|
||||
"jumppad" Z Y X
|
||||
</p>
|
||||
</li>
|
||||
|
||||
<li>
|
||||
<p>
|
||||
A jumppad entity which gives you a physics push in the direction specified. For example "jumppad 30 5" makes you bounce up quite a bit and also pushes you forward a bit (so it is easier to land on a higher platform). This entity does not render anything, you are responsible for creating something that looks logical below this entity :)
|
||||
</p>
|
||||
|
||||
</li>
|
||||
|
||||
</ul>
|
||||
|
||||
Entities are shown in editmode by blue sparklies, and the closest one is indicated on the HUD.
|
||||
|
||||
<div class="code">
|
||||
delent
|
||||
</div>
|
||||
|
||||
deletes the entity closest to the player (default key x)
|
||||
|
||||
<div class="code">
|
||||
entproperty P A
|
||||
</div>
|
||||
|
||||
changes property P (0..3) of the closest entity by amount A. For example "entproperty 0 2" when executed near a lightsource would increase its radius by 2.
|
||||
|
||||
<div class="code">
|
||||
clearents type
|
||||
</div>
|
||||
|
||||
deletes all entities of said type.
|
||||
|
||||
<div class="code">
|
||||
recalc
|
||||
</div>
|
||||
|
||||
recomputes all there is to recompute about a map, currently only lighting. Default key = r
|
||||
|
||||
<div class="code">
|
||||
map name
|
||||
</div>
|
||||
|
||||
loads up map "name" in the gamemode set previously by "mode". A map given as "blah" refers to "packages/base/blah.cgz", "mypackage/blah" refers to "packages/mypackage/blah.cgz". The menu has a set of maps that can be loaded. See also map in the gameplay docs.
|
||||
|
||||
At every map load, "data/default_map_settings.cfg" is loaded which sets up all texture definitions etc. Everything defined in there can be overridden per package or per map by creating a "package.cfg" or "mapname.cfg" which contains whatever you want to do differently from the default. It can also set up triggers scripts per map etc.
|
||||
|
||||
When the map finishes it will load the next map when one is defined, otherwise reloads the current map. You can define what map follows a particular map by making an alias like (in the map script): alias nextmap_blah1 blah2 (loads "blah2" after "blah1").
|
||||
|
||||
<div class="code">
|
||||
savemap name
|
||||
</div>
|
||||
|
||||
saves the current map, using the same naming scheme as "map". makes a versioned backup (mapname_N.BAK) if a map by that name already exists, so you can never lose a map. If you leave out the "name" argument, it is saved under the current map name.
|
||||
|
||||
where you store a map depends on the complexity of what you are creating: if its a single map (maybe with its own .cfg) then the "base" package is the best place. If its multiple maps or a map with new media (textures etc.) its better to store it in its own package (a directory under "packages"), which makes distributing it less messy.
|
||||
|
||||
<div class="code">
|
||||
newmap size
|
||||
</div>
|
||||
|
||||
creates a new map of 2^size cubes. 6 is small, 7 medium, 8 large. You can go up to 12 but theres not a lot of point in that :)
|
||||
|
||||
<div class="code">
|
||||
mapenlarge
|
||||
</div>
|
||||
|
||||
if you accidentally made your map too small, this command will make it 1 power of two bigger. So if you created a 6 size map (64x64 units) it will become a 7 map (128x128), with your old map in the middle (from 32-96) and the new areas solid.
|
||||
|
||||
<div class="code">
|
||||
mapmsg "Title by Author"
|
||||
</div>
|
||||
|
||||
sets the map msg, which will be displayed when the map loads. Either use the above format, or simply "by Author" if the map has no particular title (always displayed after the map load msg).
|
||||
|
||||
<div class="code">
|
||||
waterlevel H
|
||||
</div>
|
||||
|
||||
sets the global water level in your map to H (an empty map has levels 0-16), which will render every cube that has a lower floor than H with a nice wavy water alpha texture, and applies water physics to any entity located below it. Performance notes: water is rendered for a whole square encapsulating all visible water areas in the map (try flying above the map in edit mode to see how). So the most efficient water is a single body of water, or multiple water areas that are mostly not visible from eachother. Players can influence how accurate the water is rendered using the "watersubdiv" command (config).
|
||||
|
||||
<div class="code">
|
||||
fullbright B
|
||||
</div>
|
||||
|
||||
sets all light values to fullbright (1 = on, 0 = off), so you don't need to edit the map in the dark. Will be reset when you issue a recalc. Only works in edit mode.
|
||||
|
||||
<div class="code">
|
||||
showmip
|
||||
</div>
|
||||
|
||||
Toggles between showing what parts of the scenery are rendered using what size cubes, and outputs some stats too. This can give mappers hints as to what architecture to align / textures to change etc.
|
||||
|
||||
<div class="code">
|
||||
toggleocull
|
||||
</div>
|
||||
|
||||
turns occlusion culling on & off. the reason you may want to turn it off is to get an overview of your map from above, without having all occluded bits stripped out.
|
||||
|
||||
<div class="code">
|
||||
texturereset
|
||||
</div>
|
||||
|
||||
sets the texture slot to 0 for the subsequent "texture" commands
|
||||
|
||||
<div class="code">
|
||||
texture subnum filename
|
||||
</div>
|
||||
|
||||
binds the texture indicated in filename to the current texture slot, then increments the slot number. This is for use in texture.cfg files only. subnum allows secondary textures to be specified for a single texture slot, for use in shaders and other features (unused for now, should be set to 0 to indicate primary texture).
|
||||
|
||||
<div class="code">
|
||||
slope xdelta ydelta
|
||||
</div>
|
||||
|
||||
makes a slope out of the current selection (make it a heighfield first). xdelta and ydelta are the steps that specify the slope with the red vertex as left-top, i.e. "slope 1 2" will make a slope that increases just 1 step from left to right, and is slightly steeper from top to bottom. "slope -6 0" decreases steeply from left to right, and does not slope at all from top to bottom. Note that like the vdelta command, an increasing vdelta goes further away from the player, regardless of floor or ceiling.
|
||||
|
||||
<div class="code">
|
||||
arch sidedelta
|
||||
</div>
|
||||
|
||||
makes an arch out of the current selection (first make it a heightfield of some sort). Will make the arch in the long direction, i.e when you have 6x2 cubes selected, the arch will span 7 vertices. optionally, sidedelta specifies the delta to add to the outer rows of vertices in the other direction, i.e. give the impression of an arch that bends 2 ways (try "arch 2" on an selection of atleast 2 thick to see the effect). Not all arch sizes are necessarily available, see data/prefabs.cfg.
|
||||
|
||||
<div class="code">
|
||||
archvertex span vertex delta
|
||||
</div>
|
||||
|
||||
defines a vertex delta for a specific arch span prefab, used by the "arch" command. See data/prefabs.cfg for an example on usage.
|
||||
|
||||
<div class="code">
|
||||
perlin scale seed cubesize
|
||||
</div>
|
||||
|
||||
generates a perlin noise landscape in the current selection. scale determines the frequency of the features, default = 10. seed sets the random seed, keep this the same if you want to create multiple perlin areas which fit with eachother, or use different numbers if you want alternative random generations. cubesize says how many cubes to generate a surface for at once, not used for now.
|
||||
|
||||
<div class="code">
|
||||
select x y xs ys
|
||||
</div>
|
||||
|
||||
selects the given area, as if dragged with the mouse. Useful for making complex geometry-generating scripts. The current dimensions of the selection (either created by the user or this command) are in the variables selx, sely, selxs and selys and can also be read/modified. Coordinates are as follows: after a "newmap 6" the top-left corner (the one where the red dot points) are (8,8), the opposite corner is (56,56) (or (120,120) on a "newmap 7" etc.).
|
||||
|
||||
<div class="code">
|
||||
edittag N
|
||||
</div>
|
||||
|
||||
sets the tag value (1..255) for the current selection (0 means no tag). Tags are used to determine what cubes to modify when a certain tag is triggered (see "newent trigger"). If a cube has a tag associated with it, gridlines show up in red.
|
||||
|
||||
<div class="code">
|
||||
trigger N T
|
||||
</div>
|
||||
|
||||
triggers trigger N of type T, as if the player had picked up the equivalent "trigger" entity (see above).
|
||||
|
||||
<div class="code">
|
||||
music name
|
||||
</div>
|
||||
|
||||
plays song "name" (with "packages" as base dir). This command is best used from map cfg files or triggers.
|
||||
|
||||
<div class="code">
|
||||
N = registersound name
|
||||
</div>
|
||||
|
||||
registers sound "name" with cube (see for example data/sounds.cfg). This command returns the sound number N, which is assigned from 0 onwards, and which can be used with "sound" command below. if the sound was already registered, its existing index is returned. registersound does not actually load the sound, this is done on first play.
|
||||
|
||||
<div class="code">
|
||||
sound N
|
||||
</div>
|
||||
|
||||
plays sound N, see data/sounds.cfg for default sounds, and use registersound to register your own. for example, sound 0 and sound (registersound "aard/jump") both play the standard jump sound.
|
||||
|
||||
<div class="code">
|
||||
mapmodelreset
|
||||
</div>
|
||||
|
||||
resets the mapmodel slots/indices to 0. Each subsequent mapmodel command increases it again. see default_map_settings.cfg for an example
|
||||
|
||||
<div class="code">
|
||||
mapmodel R H Z S N
|
||||
</div>
|
||||
|
||||
registers a mapmodel that can be placed in maps using newent mapmodel (see newent). N is the name, R is the square radius, H the height, Z the initial Z-offset above ground, and S the snap value in 16ths of a cube unit (0 meaning no snap). All of these values are used for collision as well as rendering. Specifying a snap can be useful for architectural mapmodels, as the md2 format doesn't provide exact vertex coordinates. Example: mapmodel 4 2 4 2 this map model is 8x8x2 in size (x,y,z), by default hovers 4 units above ground, and has all coordinates snapped to the nearest even number. See data/models.cfg.
|
||||
|
||||
<div class="code">
|
||||
scalelights RP IP
|
||||
</div>
|
||||
|
||||
Scales all lights in the map. Radius is scaled by perceptage RP and intensity by IP. Useful if you have a map which is too dark or bright but you want to keep the light entities where they are.
|
||||
|
||||
</div>
|
||||
<div id="footer"><a href="../README.html">← BACK TO MAIN SITE</a></div>
|
||||
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
@@ -310,6 +310,7 @@
|
||||
</tr>
|
||||
</table>
|
||||
|
||||
<a name="gamemodes"></a>
|
||||
<h3>Gamemodes</h3>
|
||||
|
||||
ActionCube offers seven different game modes. You can vote for one of them using the menu: Press ESC and navigate to <i>Multiplayer ⇒ Vote</i>.
|
||||
|
||||
@@ -0,0 +1,188 @@
|
||||
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
|
||||
<html xmlns="http://www.w3.org/1999/xhtml" lang="en" xml:lang="en">
|
||||
<head>
|
||||
<title>ActionCube README</title>
|
||||
<meta http-equiv="content-type" content="application/xhtml+xml;charset=utf-8" />
|
||||
<link rel="stylesheet" href="docs.css" />
|
||||
</head>
|
||||
<body>
|
||||
|
||||
<div align="center">
|
||||
|
||||
<div id="header">Rabid Viper Productions</div>
|
||||
<div id="main">
|
||||
|
||||
<h2>Game Related Commands</h2>
|
||||
|
||||
<div class="code">
|
||||
map M
|
||||
</div>
|
||||
|
||||
loads a map. if connected to a multiplayer server, votes to load this map (others will have to type "map M" as well to agree with loading this map). To vote for a map with a specific mode, set the mode before you issue the map command (see multiplayer menu). See also map in the editref.
|
||||
|
||||
<div class="code">
|
||||
name yourname
|
||||
</div>
|
||||
|
||||
used for multiplayer
|
||||
|
||||
<div class="code">
|
||||
say text...
|
||||
</div>
|
||||
|
||||
outputs text to all players, as if you typed it
|
||||
|
||||
<div class="code">
|
||||
echo text...
|
||||
</div>
|
||||
|
||||
outputs text
|
||||
|
||||
<div class="code">
|
||||
saycommand P...
|
||||
</div>
|
||||
|
||||
this puts a prompt on screen where you can type stuff into, which will capture all keystrokes until you press return (or esc to cancel). You may press tab to autocomplete commands/aliases/variables, and up/down keys to browse the command history. If what you typed started with a "/", the rest of it will be executed as a command, otherwise its something you "say" to all players. default key = t. If P is prefix to insert to the buffer, (default key ` inserts a /).
|
||||
|
||||
<div class="code">
|
||||
connect serverip
|
||||
</div>
|
||||
|
||||
connects to a server, e.g. "connect fov120.com". There is no serverbrowser nor paste yet, so you are adviced to paste ips into a suitable bind into your autoexec.cfg for the moment.
|
||||
|
||||
<div class="code">
|
||||
disconnect
|
||||
</div>
|
||||
|
||||
leaves server
|
||||
|
||||
<div class="code">
|
||||
rate N
|
||||
</div>
|
||||
|
||||
sets your clients maximum downstream bandwidth to N bytes per second. Leaving it at 0 (the default) means the server will dynamically try to do the best thing, this is recommended for players who don't have a clue what their bandwidth is (setting your rate unoptimally is worse than not setting it all). Modem players (56k) could try rate 4000 and tweak from there, dsl players can try rate 6000-10000. Note that the more players on a server, the more critical the effect of your rate. If you are tweak addicted, you can try playing with the variables throttle_decel (how quickly to start dropping packets when your connection becomes bandwidth limited) throttle_accel (how quickly to recover once bandwidth becomes available again) and throttle_interval (how quickly to reestimate the situation). Change the defaults at your own risk.
|
||||
|
||||
<div class="code">
|
||||
team teamname
|
||||
</div>
|
||||
|
||||
determines who are your teammates in any team game mode (truncated to 4 characters, case sensitive).
|
||||
|
||||
<div class="code">
|
||||
showscores
|
||||
</div>
|
||||
|
||||
showscores turns display of scores (name/frags/network) on and -showscores turns it off. Default key is tab.
|
||||
|
||||
<div class="code">
|
||||
conskip N
|
||||
</div>
|
||||
|
||||
allows you to browse through the console history, by offsetting the console output by N. Default key keypad - scrolls into the history (conskip 1) and keypad + resets the history (conskip -1000).
|
||||
|
||||
<div class="code">
|
||||
weapon a
|
||||
</div>
|
||||
|
||||
fixme...
|
||||
|
||||
<div class="code">
|
||||
gamespeed P
|
||||
</div>
|
||||
|
||||
sets the gamespeed in percent, i.e. 50 is playing in slowmotion at half the speed. does not work in multiplayer. for entertainment purposes only :)
|
||||
|
||||
<div class="code">
|
||||
mode N
|
||||
</div>
|
||||
|
||||
set gameplay mode to N for the next game played (next map load). N can be one of the values inside rounds brackets specified
|
||||
in the <a href="game.html#gamemodes">game section</a>.
|
||||
|
||||
<div class="code">
|
||||
skill N
|
||||
</div>
|
||||
|
||||
Sets the skill level (1-10) for single player modes. Default = 3. Affects number of monsters in DMSP mode, and general monster AI in all SP modes.
|
||||
|
||||
<div class="code">
|
||||
sendmap<br />
|
||||
getmap
|
||||
</div>
|
||||
|
||||
|
||||
These two commands allow you to send other players maps they may not have while in multiplayer mode, and easily keep maps in sync while doing coop edit. "sendmap" reloads the current map you are on, then uploads it to the server and sends every other player a message about it. Other players can then simply type "getmap" to receive the current map, which is written to their local disk then reloaded. A second variant "sendmap name" is available which is particularly useful for coop editing, which first does a "savemap name" before performing the actual "sendmap". Thus in both cases you must already be on the map you want to send before issuing the command! (in some multiplayer that requires voting). Also note that "getmap" operates on the last map send by some other player, whatever it is.
|
||||
|
||||
<div class="code">
|
||||
servermenu
|
||||
</div>
|
||||
|
||||
displays the server menu. The server menu contains the last N servers you connected to, sorted by ping (servers are pinged automatically when bringing up this menu). Just select one to connect again. If you connect to a server by typing "connect" manually, the server gets added here automatically. You can also add servers to "servers.cfg" manually.
|
||||
|
||||
<div class="code">
|
||||
updatefrommaster
|
||||
</div>
|
||||
|
||||
contacts the masterserver and adds any new servers to the server list (written to servers.cfg on exit). (see also multiplayer menu).
|
||||
|
||||
<div class="code">
|
||||
savegame F
|
||||
</div>
|
||||
|
||||
Saves the current state of game (map, state of entities, monsters, triggers, and your player) to a savegame file named F (these are placed in the "savegames" directory). Default key F8 is "savegame quicksave". Works only in classic singleplayer mode.
|
||||
|
||||
<div class="code">
|
||||
loadgame F
|
||||
</div>
|
||||
|
||||
restores a previously saved game named F. Default key F9 is "loadgame quicksave". You cannot load savegames from different versions of the map, different versions of cube, or different cpu architectures.
|
||||
|
||||
<div class="code">
|
||||
record N
|
||||
</div>
|
||||
|
||||
Starts recording of a demo. This works for any multiplayer mode, including the default "ffa" mode you are in when you load up a map locally. The file is saved to demos/N.cdgz.
|
||||
|
||||
<div class="code">
|
||||
stop
|
||||
</div>
|
||||
|
||||
Stops any demo recording or playback.
|
||||
|
||||
<div class="code">
|
||||
demo N
|
||||
</div>
|
||||
|
||||
Plays back the demo recorded under name N. Playback is interpolated for the player whose perspective you view (not changeable). Not all parts of the game may work correctly under demo play, this is an experimental feature. If you find anything not functioning that greatly hampers your enjoyment of watching demos, let me know. See below for additional commands to use with demos.
|
||||
|
||||
<div class="code">
|
||||
demoplaybackspeed P
|
||||
</div>
|
||||
|
||||
Very experimental, may cause more problems than normal play. Set before playing a demo, P is a percentage, i.e. 200 will play back at twice the speed.
|
||||
|
||||
<div class="code">
|
||||
demodelaymsec D
|
||||
</div>
|
||||
|
||||
Only touch if you know what you are doing: changes the delay in msec with which the demo is played back to allow for interpolation. Default is 100, if you decrease it you will most likely just get choppier (it will obstruct the spline interpolation) for an unnoticable bit less lag. Increase it if you notice choppyness in playback, should not be needed in general, but may help if you insist on playing back demos at very low demoplaybackspeed.
|
||||
|
||||
<div class="code">
|
||||
demotracking B
|
||||
</div>
|
||||
|
||||
When demotracking is on (B = 1), the camera will create a red particle every frame where it moves, creating a trail. This can be used to inspect someone's movement in a game. It will only show the last N particles according to the maxparticles variable, which you may want to increase to 10000. The particles will remain even after you stop the demo, so you can use edit mode to look at it from all angles.
|
||||
|
||||
<div class="code">
|
||||
password P
|
||||
</div>
|
||||
|
||||
Set the password to P, so you can join servers that are password protected. See the -p command line option.
|
||||
|
||||
</div>
|
||||
<div id="footer"><a href="../README.html">← BACK TO MAIN SITE</a></div>
|
||||
|
||||
</div>
|
||||
|
||||
</body>
|
||||
</html>
|
||||
Reference in New Issue
Block a user