g_start_weapon_laser

0 = never provide the weapon, 1 = always provide the weapon, -1 = game mode default


I have 'g_start_weapon_laser 1' on my Race server, but it doesn't spawn players with a laser. Is this a bug or a feature?

I tried setting it through rcon as well. nada.

it works fine for me set from the menu. for dedicated server try -1 or modifying the configs in the pk3.

Many race maps settemp g_start_weapon_laser 0 in their mapinfo. You cannot override that from your server config.

Wow, surprisingly more than I expected.

Code: Select all

$ for file in $(ls *.pk3); do unzip $file *.mapinfo; done
$ cd maps
$ grep "g_start_weapon_laser" *.mapinfo
cb_race1_v1r1.mapinfo:settemp_for_type all g_start_weapon_laser 0
cel_hell_v1r4.mapinfo:settemp_for_type all g_start_weapon_laser 0
dibrun.mapinfo:settemp_for_type all g_start_weapon_laser 0
dibrun2.mapinfo:settemp_for_type all g_start_weapon_laser 0
hagarrun.mapinfo:settemp_for_type all g_start_weapon_laser 0
nexrun1-remix_b2.mapinfo:settemp_for_type all g_start_weapon_laser 0
nexrun1.mapinfo:settemp_for_type all g_start_weapon_laser 0
nexrun1_fun.mapinfo:settemp_for_type all g_start_weapon_laser 0
nexrun2_v1r2.mapinfo:settemp_for_type all g_start_weapon_laser 0
slopez.mapinfo:settemp_for_type all g_start_weapon_laser 0
space_race_b2.mapinfo:settemp_for_type all g_start_weapon_laser 0
test00.mapinfo:settemp_for_type all g_start_weapon_laser 0
test02_v1r2.mapinfo:settemp_for_type all g_start_weapon_laser 0
the_turn.mapinfo:settemp_for_type all g_start_weapon_laser 0
vert_rc1.mapinfo:settemp_for_type all g_start_weapon_laser 0

I don't want to override the mapper's wishes, I just though the server was bugging.

Thanks for the tips.

Since we are on the subject.

I assume within a mapinfo anything g_ can be altered for that particular map? I want to set laser force to 150 rather than 400 for my assault map to make the laser useless for jumping, but still a usable weapon.

yes you can use mapinfo.cfg or map.qc to set individual settings for that particular map.

you can put it in .mapinfo not in mapinfo.cfg. cfgs were deprecated iirc. ive never heard of map.qc either.

<bsp name>.mapinfo << is the proper name

yea. and i don't think nex allows/uses map.qc