Red Faction Wiki - Recent changes [en]

Red Faction Modding Tutorials

Goober — Tue, 28 Apr 2026 19:45:01 GMT

End User Guides

← Older revision		Revision as of 19:45, 28 April 2026
Line 70:		Line 70:
	*[[Installing Clientside Mods (RF1)]]		*[[Installing Clientside Mods (RF1)]]
	*[[Installing Custom Levels (RF1)]]		*[[Installing Custom Levels (RF1)]]
			*[[Launching Alpine Faction Bots]]

	[[Category: Red Faction]]		[[Category: Red Faction]]
	[[Category: RF1 Editing]]		[[Category: RF1 Editing]]

Launching Alpine Faction Bots

Goober — Tue, 28 Apr 2026 19:44:30 GMT

← Older revision		Revision as of 19:44, 28 April 2026
Line 1:		Line 1:
	{{RF1Tutorial\|Goober}}		{{RF1Tutorial\|Goober}}
	This step-by-step guide will walk you through setting up '''headless bots''' on a '''Red Faction 1''' [[https://alpinefaction.com Alpine Faction]] v1.3 dedicated server. Headless bots are Alpine Faction clients running with no rendering or sound, controlled remotely by the dedicated server. Because they connect like real players, the server gets bots that move, fight, and use the network exactly as a human would - without the dedicated server having to simulate them locally.		This step-by-step guide will walk you through setting up '''headless bots''' on a '''Red Faction 1''' [https://alpinefaction.com Alpine Faction] v1.3 dedicated server. Headless bots are Alpine Faction clients running with no rendering or sound, controlled remotely by the dedicated server. Because they connect like real players, the server gets bots that move, fight, and use the network exactly as a human would - without the dedicated server having to simulate them locally.

	'''NOTE:''' This guide assumes you have already set up an Alpine Faction dedicated server. If you have not, please see:		'''NOTE:''' This guide assumes you have already set up an Alpine Faction dedicated server. If you have not, please see:

Launching Alpine Faction Bots

Goober — Tue, 28 Apr 2026 19:44:21 GMT

Created page with "{{RF1Tutorial|Goober}} This step-by-step guide will walk you through setting up '''headless bots''' on a '''Red Faction 1''' https://alpinefaction.com Alpine Faction v1.3 dedicated server. Headless bots are Alpine Faction clients running with no rendering or sound, controlled remotely by the dedicated server. Because they connect like real players, the server gets bots that move, fight, and use the network exactly as a human would - without the dedicated server havin..."

New page

{{RF1Tutorial|Goober}}
This step-by-step guide will walk you through setting up '''headless bots''' on a '''Red Faction 1''' [[https://alpinefaction.com Alpine Faction]] v1.3 dedicated server. Headless bots are Alpine Faction clients running with no rendering or sound, controlled remotely by the dedicated server. Because they connect like real players, the server gets bots that move, fight, and use the network exactly as a human would - without the dedicated server having to simulate them locally.

'''NOTE:''' This guide assumes you have already set up an Alpine Faction dedicated server. If you have not, please see:
*[[Setting up an Alpine Faction Dedicated Server (RF1)]]

==Overview==
* The dedicated server does '''not''' run the bots locally. Instead, each bot is a separate Alpine Faction process running on a computer that can reach the server.
* Each bot client connects to the server using the normal multiplayer connection flow, but is identified as a bot via a '''shared secret''' it sends in its join request.
* The dedicated server controls each bot by sending it a profile (personality, skill, name, character) and steering its behaviour over the network.
* By default, headless bots run with no rendering and no sound, so resource usage per bot is low.

To run any number of headless bots, you need:
# A dedicated server configured with a '''bot shared secret''' (and optionally one or more '''bot profiles''').
# One Alpine Faction client process per bot, launched with the matching secret and the server's address.

==Step 1: Configure the dedicated server==
Open your dedicated server's ADS config file (the one you pass to '''AlpineFactionLauncher.exe''' with '''-ads''').

Add a '''bot_shared_secret''' to the top-level (root) section. This is any 32-bit unsigned integer; treat it like a password - clients that don't send the matching secret will be rejected as bot clients.
<pre>
bot_shared_secret = 1234567890
</pre>

'''IMPORTANT:''' The shared secret value must be greater than 0. A value of 0 disables bot authentication entirely.

'''IMPORTANT:''' The number of bots that will be filled in is capped by your server's '''ideal_player_count'''. If you want N bots, make sure '''ideal_player_count''' is at least N. Bots beyond that count will be rejected on join.

==Step 2: (Optional) Create bot profiles==
You can leave the rest of the config alone - bots that connect with no profiles configured will use sensible defaults (the '''balanced''' personality and the '''average''' skill preset, with a randomized name and character).

For more variety, you can define one or more bot profile ADS files and reference them from your server config. Each connecting bot is assigned a profile slot in round-robin fashion.

===Step 2a: Write a profile file===
Create a new file, e.g. '''bots/aggressive_alice.toml''', next to your dedicated server config:
<pre>
# Identity (both optional - leave empty to randomize from the default identity pool)
player_name = "Alice"
mp_character = "miner1"

# Behavioural preset (see "Available presets" below)
personality_preset = "aggressive"
skill_preset = "hard"

# Optional: tweak individual personality fields
[personality_overrides]
# Many fields are available. This guide will be expanded later to contain them.

# Optional: tweak individual skill fields
[skill_overrides]
# Many fields are available. This guide will be expanded later to contain them.

# Optional: enable specific quirks
[quirks]
# Many fields are available. This guide will be expanded later to contain them.
</pre>

===Step 2b: Reference profiles from the server config===
In your main ADS server config, add a '''bot_profiles''' array listing the relative paths to each profile file:
<pre>
bot_profiles = [
"bots/aggressive_alice.toml",
"bots/sniper_bob.toml",
"bots/balanced_charlie.toml",
]
</pre>

Paths are resolved relative to the directory containing your server's ADS config.

===Available presets===
'''Personality presets:''' '''balanced''', '''aggressive''', '''defensive''', '''tactician''', '''berserker''', '''objective''', '''sniper''', '''guerrilla''', '''collector''', '''brawler''', '''destroyer'''

'''Skill presets:''' '''beginner''', '''easy''', '''average''', '''hard''', '''expert''', '''nightmare'''

If a profile omits '''personality_preset''' it defaults to '''balanced'''. If it omits '''skill_preset''' it defaults to '''average'''.

==Step 3: Start the dedicated server==
Launch your dedicated server normally:
<pre>
AlpineFactionLauncher.exe -ads my_server.toml -port PORT
</pre>

Watch the server console output. You should see lines like:
<pre>
Bot shared secret: 1234567890
Loading bot profile: .../bots/aggressive_alice.toml
Bot player name: Alice
Bot personality preset: aggressive
Bot skill preset: hard
</pre>

If you don't see your bot configuration applied, double-check your ADS file for syntax errors and confirm the file paths in '''bot_profiles''' resolve correctly.

==Step 4: Launch a headless bot client==
For each bot you want, start a separate '''AlpineFactionLauncher.exe''' process with these arguments:
<pre>
AlpineFactionLauncher.exe -url rf://IP:PORT -bot 1234567890
</pre>

The arguments are:
*'''-url rf://IP:PORT''' - The address of your server. Use '''rf://127.0.0.1:7755''' if the bot is running on the same machine as the server (replace '''7755''' with whatever port your server uses).
*'''-bot <secret>''' - Enables headless bot mode. The number must match the '''bot_shared_secret''' from your server config exactly.
*'''-noquit''' (optional) - Prevents the bot process from quitting automatically when it disconnects.

When the bot is accepted, you'll see it appear in the server's player list (with the name from its assigned profile, or a randomized default name if no profiles are configured).

===Running multiple bots===
To run more than one bot, simply launch '''AlpineFactionLauncher.exe''' multiple times with the same '''-bot''' arguments. Each invocation creates a separate process.

Each bot will be assigned the next available profile slot (round-robin), and bots beyond your server's '''ideal_player_count''' will be rejected.

==Additional information==
===Debug rendering===
If you want to '''see''' what a bot is doing - for development, debugging, or just curiosity - replace '''-bot''' with '''-debugbot''':
<pre>
AlpineFactionLauncher.exe -url rf://127.0.0.1:7755 -debugbot 1234567890
</pre>

This launches a normal rendered Alpine Faction window controlled by the server, with bot debug overlays enabled. Use it sparingly - it's much heavier than a headless bot.

===Without a shared secret===
If you don't set '''bot_shared_secret''' on your server, '''-bot'''/'''-debugbot''' clients will not be accepted as bots.

===Bot count limit===
The server will reject incoming bots once the connected bot count reaches '''ideal_player_count'''. Bot slots also free up automatically when bots disconnect. To run a server with more bots, raise '''ideal_player_count''' in your server rules.

===Still need help?===
* If you run into issues setting up headless bots, it's best to join the [https://discord.gg/factionfiles Red Faction Community Discord] for some assistance.

[[Category: Red Faction]]
[[Category: Tutorials]]

RF Client Versions

Goober — Wed, 22 Apr 2026 12:41:26 GMT

Community-Made Clients

← Older revision		Revision as of 12:41, 22 April 2026
(One intermediate revision by the same user not shown)
Line 49:		Line 49:
	* Includes everything offered by [[#Dash Faction\|Dash Faction]] plus many additional modern features and bug fixes (see [https://alpinefaction.com Alpine Faction Website] for more information)		* Includes everything offered by [[#Dash Faction\|Dash Faction]] plus many additional modern features and bug fixes (see [https://alpinefaction.com Alpine Faction Website] for more information)
	* Optionally [[Link_Alpine_Faction_to_a_FactionFiles_Account\|integrates with a FactionFiles account]] to offer additional features, including achievements and in-game multiplayer map ratings.		* Optionally [[Link_Alpine_Faction_to_a_FactionFiles_Account\|integrates with a FactionFiles account]] to offer additional features, including achievements and in-game multiplayer map ratings.
	* Major version releases (as of April ~~2025~~):		* Major version releases (as of April 2026):
	** v1.0.0 Maple (and previously v0.0.4_beta)		** v1.0.0 Maple (and previously v0.0.4_beta)
	** v1.1.0 Tamarack (and previously v1.1.0_beta1 and v1.1.0_rc1)		** v1.1.0 Tamarack (and previously v1.1.0_beta1 and v1.1.0_rc1)
	** v1.2.0 Willow (and previously v1.2.0_beta1 and v1.2.0_rc1)		** v1.2.0 Willow (and previously v1.2.0_beta1 and v1.2.0_rc1; subsequently v1.2.1 and v1.2.2)
			** v1.3.0 Bakeapple (and previously v1.3.0_beta1, v1.3.0_beta2, and v1.3.0_beta3)

	====Dash Faction====		====Dash Faction====
Line 67:		Line 68:
	** v1.4.0 (and subsequently v1.4.1 and v1.4.2)		** v1.4.0 (and subsequently v1.4.1 and v1.4.2)
	** v1.5.0 (and previously v1.5.0-rc1 and v1.5.0-rc2)		** v1.5.0 (and previously v1.5.0-rc1 and v1.5.0-rc2)
	** v1.6.0 (and previously v1.6.0-beta and v1.6.0-rc1, subsequently v1.6.1-rc1 and v1.6.1)		** v1.6.0 (and previously v1.6.0-beta and v1.6.0-rc1; subsequently v1.6.1-rc1 and v1.6.1)
	** v1.7.0 (and previously v1.7.0-beta and v1.7.0-rc1)		** v1.7.0 (and previously v1.7.0-beta and v1.7.0-rc1)
	** v1.8.0 (and previously v1.8.0-rc1)		** v1.8.0 (and previously v1.8.0-rc1)

Alpine Faction Release Highlights

Goober — Wed, 22 Apr 2026 02:59:27 GMT

← Older revision		Revision as of 02:59, 22 April 2026
Line 14:		Line 14:

	==Alpine Faction 1.3.0==		==Alpine Faction 1.3.0==
	* ~~Release coming soon~~		* Released 22 Apr 2026
	===Graphics===		===Graphics===
	* Direct3D 11 Renderer is now recommended. High level list of D3D11 renderer improvements:		* Direct3D 11 Renderer is now recommended. High level list of D3D11 renderer improvements:

Alpine Faction News Feed

Goober — Wed, 22 Apr 2026 02:30:38 GMT

← Older revision		Revision as of 02:30, 22 April 2026
Line 1:		Line 1:
	- Alpine Faction 1.2.2 released: ~~Jan 4~~, '26		- Alpine Faction 1.3.0 released: Apr 22, '26
	- RF Game Night 183: Apr 25, '26		- RF Game Night 183: Apr 25, '26
			- RF Game Night 184: May 9, '26

Sopot's Citadel

Greyestfox — Fri, 17 Apr 2026 19:48:23 GMT

Battle Armour: text above image said In The Rain. I used the UK English spelling. You're welcome. :)

← Older revision		Revision as of 19:48, 17 April 2026
Line 52:		Line 52:
	==Battle Armour==		==Battle Armour==
	{{Infobox RF1SPMap		{{Infobox RF1SPMap
	\|levelname = ~~In The Rain~~		\|levelname = Battle Armour
	\|image = [[Image:Battle Armour Level.png\|300px]]		\|image = [[Image:Battle Armour Level.png\|300px]]
	\|filename = L05S4.rfl		\|filename = L05S4.rfl

Alpine Faction Release Highlights

Goober — Fri, 17 Apr 2026 14:31:11 GMT

Mod / Map Development

← Older revision		Revision as of 14:31, 17 April 2026
(4 intermediate revisions by the same user not shown)
Line 12:		Line 12:

	This page only has what I feel are the most important aspects of each release. For a full changelog at any given time, visit [https://github.com/GooberRF/alpinefaction/blob/master/docs/CHANGELOG.md CHANGELOG.md] on the Alpine Faction repository.		This page only has what I feel are the most important aspects of each release. For a full changelog at any given time, visit [https://github.com/GooberRF/alpinefaction/blob/master/docs/CHANGELOG.md CHANGELOG.md] on the Alpine Faction repository.

			==Alpine Faction 1.3.0==
			* Release coming soon
			===Graphics===
			* Direct3D 11 Renderer is now recommended. High level list of D3D11 renderer improvements:
			** Add GPU accelerated realtime per-pixel lighting for meshes
			** Add full mesh shadows for entities, corpses, and items
			** Support for the gamma video setting
			** Fix "P2T fix" not working properly
			** Fix impact decals not rendering correctly at distance
			** Fix hard cutoff lines on fullbright gradient alpha textures
			** Fix mirror and security monitor textures not being properly self-illuminated
			===General===
			* Revamp FactionFiles link client functionality to be much more user friendly
			* Add speedometer to HUD
			* Add raw/modern (id Tech/Source-style) mouse input scaling
			* Fix first person weapon running animations
			===Multiplayer===
			* Add server-controlled advanced multiplayer bots
			** Add in-game waypoint file editor
			** Add FactionFiles autodownloader support for waypoint files in custom maps
			* Revamp FactionFiles autodownloader user interface when downloading new maps
			* Fix players being able to stand up into geometry when they should be forced to stay crouched
			* Add player outlines (D3D11 only)
			* Fix third person footsteps
			* Show server client information on server list
			* Split kill feed from chat box (enable with "ui_gamefeed" console command)
			* Many spectator mode improvements
			** Improved UX for toggling between spectator modes
			** Powerup icons, damage flash, crouch state, rail scanner, and first person weapon animation support in first person spectate
			** Hitsounds and kill feed in first person spectate now apply for the player being spectated
			===Dedicated Servers===
			* Add FactionFiles autodownloader support by default for all levels in server rotation (disable with "-nodl" switch)
			* Support rcon profiles (ACLs)
			===Mod / Map Development===
			* Expanded destruction capabilities available to developers
			** RF2-style (brush-based) geomod
			** Support for non-glass material breakable detail brushes
			** Dynamic debris generation from breakable detail brushes
			** Support breakable detail brushes using ngons
			* Add "Hold Open" setting to movers
			* New object types: Mesh, Corona, Note
			* Add support for Gas Regions (D3D11 only)
			* Many new events
			* Fix Decal alpha parameter (D3D11 only)
			* Mirror functions to level editor for brushes and groups
			* Convert brushes to meshes in-editor
			* Several new face/vertex mode operators
			* Support custom texture subcategories (subdirectories)
			* Support loading new textures/meshes (via tools menu - "Reload Textures", "Reload Meshes")
			* Fix UV Unwrap window breaking when launching a fullscreen D3D application
			* Fix autosave sometimes making brushes/objects teleport during a rotation
			* Do not fail to create level packfile (ie. 0KB vpp) when assets are missing
			* Include textures, meshes, and animations used in level automatically when creating level packfile
			* New Select Objects and Hide Objects windows with UX improvements
			* "To Mesh Object" button (in Select Objects) to convert clutter to mesh/corona
			* Fix mesh collision not properly updating when meshes are hidden/unhidden
			* Fix modern (ie. non-Legacy) movers sometimes maintaining momentum even after stopping/pausing
			* Raised stock limits
			** Lights on a single face: 64 -> 1024
			** Lights per level: 1100 -> 8192
			** Detail rooms: 256 -> 8192
			** Geo cache face list: 16384 -> 65536, batch count: 512 -> 1024, memory pool: 8MB -> 32MB

	==Alpine Faction 1.2.2==		==Alpine Faction 1.2.2==

Alpine Faction News Feed

Goober — Fri, 17 Apr 2026 13:39:53 GMT

← Older revision		Revision as of 13:39, 17 April 2026
Line 1:		Line 1:
	- Alpine Faction 1.2.2 released: Jan 4, '26		- Alpine Faction 1.2.2 released: Jan 4, '26
	- RF Game Night ~~182~~: Apr 11, '26		- RF Game Night 183: Apr 25, '26

RF1 Engine and Level Editor Limits

Goober — Tue, 14 Apr 2026 18:21:30 GMT

Map Limits

← Older revision		Revision as of 18:21, 14 April 2026
(One intermediate revision by the same user not shown)
Line 66:		Line 66:
	\| 96/128 (RF), 384/512 (AF/DF)		\| 96/128 (RF), 384/512 (AF/DF)
	\| Hard limit is absolute maximum number of decals. Soft limit is the limit after which decals begin to fade away. For decal objects placed in the editor, decals will stop being created after soft limit, and you risk level file corruption if you exceed hard limit.<br />For total number of decals, stock game has 96 soft limit, 128 hard limit. AF and DF have 384 soft limit, 512 hard limit.<br />Additional limits:<br />Total decals in a single room: 40/48 (RF), 96/127 (AF/DF)<br />Total weapon impact decals: 14/16 (RF), 48/64 (AF/DF)<br />Total GeoMod decals: 30/32 (RF), 96/127 (AF/DF)<br />Total decals on solids: 40/48 (RF), 96/127 (AF/DF)<br />In the default [[RED]] editor (non-Alpine), you'll get a pop-up warning when saving your level if it contains >64 decal objects. This was a hard limit for PS2 maps.		\| Hard limit is absolute maximum number of decals. Soft limit is the limit after which decals begin to fade away. For decal objects placed in the editor, decals will stop being created after soft limit, and you risk level file corruption if you exceed hard limit.<br />For total number of decals, stock game has 96 soft limit, 128 hard limit. AF and DF have 384 soft limit, 512 hard limit.<br />Additional limits:<br />Total decals in a single room: 40/48 (RF), 96/127 (AF/DF)<br />Total weapon impact decals: 14/16 (RF), 48/64 (AF/DF)<br />Total GeoMod decals: 30/32 (RF), 96/127 (AF/DF)<br />Total decals on solids: 40/48 (RF), 96/127 (AF/DF)<br />In the default [[RED]] editor (non-Alpine), you'll get a pop-up warning when saving your level if it contains >64 decal objects. This was a hard limit for PS2 maps.
			\|-
			\| Killable objects
			\| 3200
			\| Includes all destructible clutter and mesh objects. Only applies in multiplayer.
			\|-
	\|}		\|}