The new impulses don't appear to be working with the cl_weaponpriority command. Am I doing something wrong here? Can anyone else verify / provide me a fix?

Code: Select all

bind c "impulse 210; bestweapon 5 4 8"            // electro, mortar, hagar
set cl_weaponpriority0 "234 233 237 242 231"      // electro, mortar, hagar

bind v "impulse 211; bestweapon 4 5 8"             // mortar, electro, hagar
set cl_weaponpriority1 "233 234 237 242 243 231"   // mortar, electro, hagar

bind e "impulse 230"                          // laser

bind f "impulse 212; bestweapon 7 3 1"            // nex, mg, laser
set cl_weaponpriority2 "236 232 230 242 231"      // nex, mg, laser

bind q "impulse 213; bestweapon 9 4 8"             // rocket, mortar, hagar
set cl_weaponpriority3 "238 233 237 243 231"       // rocket, mortar, hagar

bind r "impulse 214; bestweapon 3 6 5 8"         // mg, crylink, electro, hagar
set cl_weaponpriority4 "233 235 234 237 243 231"    // mg, crylink, electro, hagar

bind t "impulse 215; bestweapon 6 3 5 8"         // crylink, mg, electro, hagar
set cl_weaponpriority5 "235 232 234 237 242 243 231"// crylink, mg, electro, hagar


It's been confirmed. The new impulses do not work with this command.

the weaponpriority cvars contain weapon numbers, not impulses. However, as these numbers don't overlap, I could safely add support for the impulses too.

Weapon 1 is laser, and is on impulse 230. Any weapon is on impulse weaponnumber+229.

You misunderstand a lot of things. Impulse 1 to 9 and impulse 14 are NOT deprecated, but are used for the number keys. Some weapons share a number key. The new HUD indicates the distribution on the number keys.

divVerent wrote:Some weapons share a number key.

Here in lies my misunderstanding. If I'm trying to order weapons in a specific way but the # is shared, I cannot do this. In fact IIRC, the command wasn't including the SVN weapons at all using the weapon numbers. I then assumed weapon impulses were being used.

Thank you for clarifying.