| Setting up
Before you start to make a JRF, it helps if you know most of the console commands that will be needed. These are all listed in the Jumbot readme, but here they are for convenience: |
|||
| wp_edit (cvar): |
Setting this to 1 enables waypoint edit mode. If there is
a waypoint file for the level, it will be loaded in edit mode instead of used, and you can edit with the regular waypoint management
commands. After you finish using edit mode, use writewpfile to save the changes.
|
||
| wp_vis (cvar): | Causes all of the waypoints placed to have particle streams
on top of them. The particle colors are also different depending on the type
of waypoint. Regular waypoints are yellow, crouch waypoints are pink, jump
waypoints are red, and the last waypoint in a trail is multi-colored. The default for this cvar is 1 (enabled). Setting it to 2
will use the alternate display method to eliminate flickering, but it requires more CPU power.
|
||
| wp_autoplace (cvar): | Default is 1. Setting to 0 will disable attempts
to automatically place waypoints behind you when you're constructing a waypoint table to be saved to a JRF file.
|
||
| wp_jumpplace (cvar): | Default is 1. Setting to 0 will disable automatic
adding of a jump-waypoint each time you jump.
|
||
| makewp (command): | This will add a waypoint at your current location, it
is used while constructing a waypoint file for a level (see below).
|
||
| makewpj (command): | This will add a jump waypoint at your current location.
Each time the bot comes to a jump waypoint it will jump.
|
||
| makewpe (command): | This will add a special waypoint that the bot will only
move to when an object is below the point.
|
||
| makewp_l (command): | This will add a waypoint in the middle of a trail. Just
look at a waypoint (so that the waypoint is highlighted) while using this command and a waypoint will be inserted into the trail after that
waypoint at your current location. You can also add a number after the command to
manually inserted a waypoint after any given waypoint ("makewp_l 53", for example, would insert the waypoint after waypoint number 53 in the trail
if it existed, as waypoint number 54, and waypoint 54 would be pushed up to 55, and so on).
|
||
| makewpj_l (command): | This command is to makewp_l as makewpj is to makewp.
|
||
| makewpe_l (command): | This command is to makewp_l as makewpe is to makewp.
|
||
| makewp_snipe (command): | This command is to create a sniper waypoint. It
requires a special syntax. The syntax is: makewp_snipe <snipe_point#> <insert_after#> <crouch>
For example, the following would create a sniper point at your current location which points to waypoint number 200 and is inserted in an
existing trail after point 300, and the bot will crouch at this point while sniping:
makewp_snipe 200 300 1 Use 0 as the crouch flag if you want the bot to stand at this point
while sniping.
|
||
| remwp_l (command): | Works the same as makewp_l, except it's for removing waypoints instead of inserting new ones.
|
||
| remwp (command): | Removes the last placed waypoint.
|
||
| writewpfile (command): | Use this after you've finished placing waypoints
for a level to save the waypoint data to a file for later use.
|
||
|
|
|||
| As well as these,
the Jumbot readme contains some good points on JRF creation, so it really
is useful to read the waypoint section of it (at the bottom of the file).
The wp_autoplace cvar does work, but I think that the JRF will be better overall if it is disabled. Enable wp_jumpplace, and bind keys to remwp, makewp_l, and makewp. I have '/' as makewp, '.' as remwp, and ',' as makewp_l, which puts them in finger range as you are running around. Either set these things each time you start a no-JRF level or set them in 'jumbot.cfg'. If you have any questions, comments, or suggestions relating to this guide, post them on the forum or email me.
2: Making the
route (and how to make it work)
3: Harder stuff
(Like getting the bot to duck-jump)
4: Testing
(and troubleshooting)
|
|||