The ammo system allows mappers to control how many shots the player can fire from weapons that use ammo. All defrag weapons, the RJ rocket launcher, the sticky bomb launcher, and concs can be controlled with separate ammo types. The default state for the player is infinite ammo, but the player’s ammo can be changed with player IO inputs and entities. Additionally, an ammo limit can be set that doesn’t allow the player to have more than a certain amount.
...This guide covers how to use collectibles in Momentum Mod. Collectibles are a tool that lets mappers create non-linear, staged maps.
To follow this guide you should:
Collectibles are any entity that the player must interact with to continue in the map. They can be thought of like pickups, but any entity can be a collectible, so long as the player can interact with it to “collect” it. The entity filter_momentum_collectibles is used to control entities based on how many collectibles the player has gathered.
Note: This guide assumes that you have a basic working knowledge of the hammer editor and the tools used.
Before you start to create your ramps in hammer, there are a few factors you should consider:
These characteristics of your ramps will inevitably be refined through testing, but it is a good idea to start off with a plan for how you want the surf to feel. Look at different surf maps that you enjoy and try to get an idea of how exactly you want yours to pan out.
...Two powerups are implemented: Haste and Damage Boost. They can be given or removed with these inputs:
SetHaste (time in seconds)
SetDamageBoost (time in seconds)
If time = 0, the effect will be removed. If time < 0, then the effect will last indefinitely until removed.
There are also powerup entities: momentum_powerup_haste and momentum_powerup_damage_boost. They both take a ResetTime key like the weapon spawner entity. The haste powerup takes a HasteTime key, and the damage boost powerup takes a DamageBoostTime key. They are both specified in seconds the same way as the inputs.
Momentum Mod ships with a customized build of Hammer (named “Strata Hammer”) which includes some, but not all of Hammer++’s features. Our development has been geared more towards stability than new features, with a focus on porting to Qt for cross platform UI and bug fixing. While Strata Hammer should be perfectly usable (and we appreciate testers), it will be a while until Hammer++ features like accurate lighting preview are fully implemented. If you prefer using Hammer++, that is completely reasonable and this guide should get you set up.
...This guide gives an overview of all the steps required to officially port a map into Momentum Mod. There are multiple tools available that accomplish the same things, so it is up to the map porter to decide what works best for them. The general process for porting maps is the following:
In order to use the in-game zoning tools, sv_cheats must be enabled. When cheats are enabled, a button on the tab menu will be displayed that lets you edit the zones. The mom_zone_edit 1 command can also be used to display the zone editor menu:
This page covers Momentum’s implementation of Parallax-Corrected Cubemaps, created with a combination of custom entities and materials.
Thanks to Brian Charles for his work on this feature.
More technical information can be found on the Valve Developer Wiki Page.
To make use of this page, you should:
momentum.fgd in your Hammer configurationIn Hammer, Parallax-Corrected Cubemaps need two entities to function correctly:
...Before you start, you should know that maps with simple geometry work best for porting. Complex geometry can cause invalid solids which will need to be manually remade, and some textures will need to be realigned.
Prerequisites:
Most Team Fortress Classic skill maps can be found on the TFC Refugees forum here: https://www.tfcrefugees.com/resources/categories/conc.4/
Maps downloaded from this forum always include any relevant custom content not packed into the map itself. Additionally many maps have descriptions and author info text documents included.
Of the files downloaded, the BSP is the actual map file, and the WAD contains the textures used in the map. In most cases custom textures will be embedded into the BSP itself.
Before you start, you should know that maps with simple geometry work best for porting. Complex geometry can cause invalid solids as vertices tend to shift around if they are off grid, and you will be forced to recreate a lot of the brushes manually. Patches and props cannot be ported across either, so choose maps without those or you will have to spend a lot of time manually replacing them in Hammer.
...If a zone region’s location has a map teleport destination entity, we highly prefer that it is used (rather than a custom arbitrary region destination coordinate) so the spot corresponds to a map teleport destination.
Make sure each region teleport destination is inside the region.
Avoid overlapping or touching regions for the same zone which could just be one region.
Make sure points are placed precisely and aligned well with geometry.
...