Game Mode stays in 1 shot kill

[7echno7im]

I have a server listed and I have about 100 maps (all DM maps) every so often it gets in to a 1 shot kill game more with only 1 weapon and the only resolution is to stop and start it again. I have a feeling it is the .mapcfg for one or more maps that when it loads, it doesn't ever come out of, but I may be wrong. Can anyone help me make sure it doesn't go in to this mode unless requested, and if requested it comes back out in whatever mode the map calls for?

I have added dm mode before my g_maplist but it still deosn't help.

If this is not possible can someone tell me what dm maps from the curl have this enabled? (http://141.2.16.3:7780/nex/maps/)

thank you very much in advance...

[Silica Gel: Do Not Eat]

I have the same problem after playing Evilminsta (dm_evilminsta) That's the new one cortez posted recently.

I just tried another minstagib map , And the same thing happened. The next standard map you choose also has minstagib enabled.

[Dokujisan]

I believe someone in IRC was asking about that last night and the conclusion was to create a mapcfg file for each map (with the same name as the mapcfg inside each pk3 file) and place it in the /data directory. That config gets executed when each map loads. It overrides the mapcfg inside each pk3 files, from what I understand.

[Mr.Carlyle]

Evilminsta, minstaaren, and nexm are the only ones I'm for sure on.

You can do what Doku suggested, but I'm not sure those maps will support weapons or items.

[Silica Gel: Do Not Eat]

I don't think the mutator_reset.cfg is executing
However the game_reset.cfg does
they are located in the data*.pk3
So I copied the mutator_reset.cfg and pasted it into the game_reset.cfg

It worked ok for me , so try the following

Create a text file called game_reset.cfg file in the nexuiz\data directory
And copy and paste the following into that file ans save it

//start copy
// we're starting a server, but if a map is already running, we have to
// reset any pre-existing configurations so that capture the flag for example
// won't stick around when the user starts a new dm map.

// clean up campaign stuff
alias _mutator_reset_0 ""
alias _mutator_reset_1 "exec mutator_reset.cfg"
_mutator_reset_$g_campaign

set g_tdm 0
set g_ctf 0
set g_domination 0
set g_runematch 0
set g_lms 0
set g_arena 0
set g_campaign 0
set g_keyhunt 0
set teamplay 0
set gamecfg 0
set g_cloaked 0
set g_footsteps 0
set g_grappling_hook 0
set g_instagib 0
set g_laserguided_missile 0
set g_midair 0
set g_minstagib 0
set g_nixnex 0
set g_nixnex_with_laser 0
set g_norecoil 0
set g_rocketarena 0
set g_vampire 0
set slowmo 1.0
set sv_gravity 800

set g_tdm_teams 2
set g_domination_default_teams 2
pausable 0

set g_respawn_mapsettings_delay 0
set g_respawn_mapsettings_waves 0

// prepare for loading a mapcfg
set timelimit 0
set fraglimit 0
set g_keyhunt_teams 0

set exit_cfg empty.cfg
//end copy

[divVerent]

Not really what one should do in this case.

If a mapcfg wants to change a setting that is meant to be able to stay usually (like Minstagib), it should do it like this:

set _backup_g_minstagib $g_minstagib
exit_cfg "mapname_exit.cfg"
g_minstagib 1
changelevel mapname

g_minstagib $_backup_g_minstagib

Because quite some maps do it wrong (especially the ones by 70mm13), I made the RBI server go a different route and let it rewrite the mapcfgs to strip out evil settings or make them harmless. This is my current report on maps that change settings it shouldn't:

WARNING: dm_70mm13_01 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_01 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_01 changes sv_gravity to 800
WARNING: dm_70mm13_01 changes sv_friction to 5
WARNING: dm_70mm13_01 changes sv_maxspeed to 400
WARNING: dm_70mm13_01 changes sv_accelerate to 5.5
WARNING: dm_70mm13_03 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_03 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_03 changes sv_gravity to 800
WARNING: dm_70mm13_03 changes sv_friction to 5
WARNING: dm_70mm13_03 changes sv_maxspeed to 400
WARNING: dm_70mm13_03 changes sv_accelerate to 5.5
WARNING: dm_70mm13_03 changes playerlimit to 9
WARNING: dm_70mm13_04 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_04 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_04 changes sv_gravity to 800
WARNING: dm_70mm13_04 changes sv_friction to 5
WARNING: dm_70mm13_04 changes sv_maxspeed to 400
WARNING: dm_70mm13_04 changes sv_accelerate to 5.5
WARNING: dm_70mm13_05 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_05 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_05 changes sv_gravity to 800
WARNING: dm_70mm13_05 changes sv_friction to 5
WARNING: dm_70mm13_05 changes sv_maxspeed to 400
WARNING: dm_70mm13_05 changes sv_accelerate to 5.5
WARNING: dm_70mm13_06 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_06 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_06 changes sv_gravity to 600
WARNING: dm_70mm13_06 changes sv_friction to 7
WARNING: dm_70mm13_06 changes sv_maxspeed to 500
WARNING: dm_70mm13_06 changes sv_accelerate to 7
WARNING: dm_70mm13_07 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_07 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_07 changes sv_gravity to 800
WARNING: dm_70mm13_07 changes sv_friction to 5
WARNING: dm_70mm13_07 changes sv_maxspeed to 400
WARNING: dm_70mm13_07 changes sv_accelerate to 5.5
WARNING: dm_70mm13_08 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_08 changes g_start_weapon_laser to 0
WARNING: dm_70mm13_08 changes sv_gravity to 800
WARNING: dm_70mm13_08 changes sv_friction to 5
WARNING: dm_70mm13_08 changes sv_maxspeed to 400
WARNING: dm_70mm13_08 changes sv_accelerate to 5.5
WARNING: dm_70mm13_10 changes g_balance_armor_limit to 150
WARNING: dm_70mm13_10 changes g_balance_armor_regen to 0
WARNING: dm_70mm13_10 changes g_balance_health_limit to 150
WARNING: dm_70mm13_10 changes g_balance_health_regen to 0
WARNING: dm_70mm13_10 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_10 changes g_start_weapon_shotgun to 1
WARNING: dm_70mm13_10 changes sv_gravity to 800
WARNING: dm_70mm13_10 changes sv_friction to 5
WARNING: dm_70mm13_10 changes sv_maxspeed to 400
WARNING: dm_70mm13_10 changes sv_accelerate to 5.5
WARNING: dm_70mm13_10 changes playerlimit to 9
WARNING: ctf_70mm13_10ctf changes g_balance_armor_limit to 150
WARNING: ctf_70mm13_10ctf changes g_balance_armor_regen to 0
WARNING: ctf_70mm13_10ctf changes g_balance_health_limit to 150
WARNING: ctf_70mm13_10ctf changes g_balance_health_regen to 0
WARNING: ctf_70mm13_10ctf changes g_start_weapon_laser to 1
WARNING: ctf_70mm13_10ctf changes g_start_weapon_shotgun to 1
WARNING: ctf_70mm13_10ctf changes sv_gravity to 800
WARNING: ctf_70mm13_10ctf changes sv_friction to 5
WARNING: ctf_70mm13_10ctf changes sv_maxspeed to 400
WARNING: ctf_70mm13_10ctf changes sv_accelerate to 5.5
WARNING: ctf_70mm13_10ctf changes g_ctf_flag_returntime to 5
WARNING: ctf_70mm13_10ctf changes g_ctf_flagscore_capture to 20
WARNING: ctf_70mm13_10ctf changes g_ctf_flagscore_capture_team to 0
WARNING: ctf_70mm13_10ctf changes g_ctf_flagscore_pickup to 1
WARNING: ctf_70mm13_10ctf changes g_ctf_flagscore_return to 5
WARNING: ctf_70mm13_10ctf changes g_ctf_flagscore_return_rogue to 10
WARNING: ctf_70mm13_10ctf changes maxplayers to 12
WARNING: ctf_70mm13_11 changes g_balance_armor_limit to 150
WARNING: ctf_70mm13_11 changes g_balance_armor_regen to 0
WARNING: ctf_70mm13_11 changes g_balance_health_limit to 150
WARNING: ctf_70mm13_11 changes g_balance_health_regen to 0
WARNING: ctf_70mm13_11 changes g_start_weapon_laser to 1
WARNING: ctf_70mm13_11 changes g_start_weapon_shotgun to 1
WARNING: ctf_70mm13_11 changes sv_gravity to 800
WARNING: ctf_70mm13_11 changes sv_friction to 5
WARNING: ctf_70mm13_11 changes sv_maxspeed to 400
WARNING: ctf_70mm13_11 changes sv_accelerate to 5.5
WARNING: ctf_70mm13_11 changes g_ctf_flag_returntime to 5
WARNING: ctf_70mm13_11 changes g_ctf_flagscore_capture to 20
WARNING: ctf_70mm13_11 changes g_ctf_flagscore_capture_team to 0
WARNING: ctf_70mm13_11 changes g_ctf_flagscore_pickup to 1
WARNING: ctf_70mm13_11 changes g_ctf_flagscore_return to 5
WARNING: ctf_70mm13_11 changes g_ctf_flagscore_return_rogue to 10
WARNING: ctf_70mm13_11 changes maxplayers to 12
WARNING: ctf_70mm13_12 changes g_balance_armor_limit to 150
WARNING: ctf_70mm13_12 changes g_balance_armor_regen to 0
WARNING: ctf_70mm13_12 changes g_balance_health_limit to 150
WARNING: ctf_70mm13_12 changes g_balance_health_regen to 0
WARNING: ctf_70mm13_12 changes g_start_weapon_laser to 1
WARNING: ctf_70mm13_12 changes g_start_weapon_shotgun to 1
WARNING: ctf_70mm13_12 changes sv_gravity to 800
WARNING: ctf_70mm13_12 changes sv_friction to 5
WARNING: ctf_70mm13_12 changes sv_maxspeed to 400
WARNING: ctf_70mm13_12 changes sv_accelerate to 5.5
WARNING: ctf_70mm13_12 changes g_ctf_flag_returntime to 5
WARNING: ctf_70mm13_12 changes g_ctf_flagscore_capture to 20
WARNING: ctf_70mm13_12 changes g_ctf_flagscore_capture_team to 0
WARNING: ctf_70mm13_12 changes g_ctf_flagscore_pickup to 1
WARNING: ctf_70mm13_12 changes g_ctf_flagscore_return to 5
WARNING: ctf_70mm13_12 changes g_ctf_flagscore_return_rogue to 10
WARNING: ctf_70mm13_12 changes maxplayers to 12
WARNING: dm_70mm13_9 changes g_balance_armor_limit to 100
WARNING: dm_70mm13_9 changes g_balance_armor_regen to 0
WARNING: dm_70mm13_9 changes g_balance_health_limit to 200
WARNING: dm_70mm13_9 changes g_balance_health_regen to 0
WARNING: dm_70mm13_9 changes g_start_weapon_laser to 1
WARNING: dm_70mm13_9 changes g_start_weapon_shotgun to 0
WARNING: dm_70mm13_9 changes sv_gravity to 800
WARNING: dm_70mm13_9 changes sv_friction to 5
WARNING: dm_70mm13_9 changes sv_maxspeed to 400
WARNING: dm_70mm13_9 changes sv_accelerate to 5.5
WARNING: dm_evilminsta changes g_minstagib to 1
WARNING: dm_minstarena changes g_minstagib to 1
WARNING: dm_suicidebooth-0.1 changes g_rocketarena to 1

So the full list of possibly dangerous maps are: anything by 70mm13 (please fix this!), evilminsta (please add exit_cfg or remove the g_minstagib), minstarena (also misses the exit_cfg), suidicebooth.

Some of the named maps surely use exit_cfg to fix this, but my script doesn't verify that - it checks for variables a mapcfg changes, ignores exit_cfg and inserts its own backup/restore mechanism; a mapcfg written by it looks like

Code: Select all

rbi_reset
set rbi_backup_g_balance_armor_limit $g_balance_armor_limit
set g_balance_armor_limit 150
set rbi_backup_g_balance_armor_regen $g_balance_armor_regen
set g_balance_armor_regen 0
set rbi_backup_g_balance_health_limit $g_balance_health_limit
set g_balance_health_limit 150
set rbi_backup_g_balance_health_regen $g_balance_health_regen
set g_balance_health_regen 0
set rbi_backup_g_start_weapon_laser $g_start_weapon_laser
set g_start_weapon_laser 1
set rbi_backup_g_start_weapon_shotgun $g_start_weapon_shotgun
set g_start_weapon_shotgun 1
set rbi_backup_sv_gravity $sv_gravity
set sv_gravity 800
set rbi_backup_sv_friction $sv_friction
set sv_friction 5
set rbi_backup_sv_maxspeed $sv_maxspeed
set sv_maxspeed 400
set rbi_backup_sv_accelerate $sv_accelerate
set sv_accelerate 5.5
set g_ctf 1
set rbi_backup_g_ctf_flag_returntime $g_ctf_flag_returntime
set g_ctf_flag_returntime 5
set rbi_backup_g_ctf_flagscore_capture $g_ctf_flagscore_capture
set g_ctf_flagscore_capture 20
set rbi_backup_g_ctf_flagscore_capture_team $g_ctf_flagscore_capture_team
set g_ctf_flagscore_capture_team 0
set rbi_backup_g_ctf_flagscore_pickup $g_ctf_flagscore_pickup
set g_ctf_flagscore_pickup 1
set rbi_backup_g_ctf_flagscore_return $g_ctf_flagscore_return
set g_ctf_flagscore_return 5
set rbi_backup_g_ctf_flagscore_return_rogue $g_ctf_flagscore_return_rogue
set g_ctf_flagscore_return_rogue 10
set fraglimit 200
set timelimit 60
set rbi_backup_maxplayers $maxplayers
set maxplayers 12
changelevel 70mm13_10ctf

alias rbi_reset "set g_balance_armor_limit $rbi_backup_g_balance_armor_limit ; set g_balance_armor_regen $rbi_backup_g_balance_armor_regen ; set g_balance_health_limit $rbi_backup_g_balance_health_limit ; set g_balance_health_regen $rbi_backup_g_balance_health_regen ; set g_start_weapon_laser $rbi_backup_g_start_weapon_laser ; set g_start_weapon_shotgun $rbi_backup_g_start_weapon_shotgun ; set sv_gravity $rbi_backup_sv_gravity ; set sv_friction $rbi_backup_sv_friction ; set sv_maxspeed $rbi_backup_sv_maxspeed ; set sv_accelerate $rbi_backup_sv_accelerate ; set g_ctf_flag_returntime $rbi_backup_g_ctf_flag_returntime ; set g_ctf_flagscore_capture $rbi_backup_g_ctf_flagscore_capture ; set g_ctf_flagscore_capture_team $rbi_backup_g_ctf_flagscore_capture_team ; set g_ctf_flagscore_pickup $rbi_backup_g_ctf_flagscore_pickup ; set g_ctf_flagscore_return $rbi_backup_g_ctf_flagscore_return ; set g_ctf_flagscore_return_rogue $rbi_backup_g_ctf_flagscore_return_rogue ; set maxplayers $rbi_backup_maxplayers ; "

This rbi_reset stuff is similar to exit_cfg, I actually could also put the "rbi_reset" call into the exit_cfg and make the script kill exit_cfg changes...

Anyway, mappers should never touch these settings. If a map is for Minstagib only, DO NOT PUT g_minstagib 1 IN THE MAPCFG! INSTEAD, TELL ADMINS TO ONLY RUN IT IN MINSTAGIB! Also, you can make your point more clear by putting some Nexes and cells on the map, but nothing else. If you really think you must change such stuff, use the exit_cfg system, as described above.

But - changing game_reset.cfg to also reset mutators is BAD, as it no longer allows you to run a Minstagib-only server!

[Ed]

WARNING: dm_suicidebooth-0.1 changes g_rocketarena to 1

Not that suicide booth is a serious map or anything...

I think in future there should be some better may of accomplishing this. Could we instead make Nexuiz so that on every map load, the defaults are reloaded? Then having map specific settings would be workable.

[divVerent]

But then these settings can't be set on a server. So... a clear no.

A real solution is planned for Nexuiz 3, and it would mean getting rid of mapcfg and replacing it by something less of an ugly hack. That way, it will also be able to temporary change cvars that get a guaranteed reset at the end of a game.

However, this will also mean that no old map pk3 will work without changes. On RBI, I will do that work for all maps that are there.

BTW, am I missing maps there? If any map there is missing or outdated, please tell me and I will update it. When 3.0 comes, I will repack and fix all map pk3s that are fixable.

[tZork]

But then these settings can't be set on a server. So... a clear no.

A real solution is planned for Nexuiz 3, and it would mean getting rid of mapcfg and replacing it by something less of an ugly hack. That way, it will also be able to temporary change cvars that get a guaranteed reset at the end of a game.

Thats some good news. Hopefully merging all thise damm mspcfg's and txt too? righ now it almost more work maintaining all the configs then it is to maintain the maps themselfs

However, this will also mean that no old map pk3 will work without changes. On RBI, I will do that work for all maps that are there.

BTW, am I missing maps there? If any map there is missing or outdated, please tell me and I will update it. When 3.0 comes, I will repack and fix all map pk3s that are fixable.

I cant say i see this as a big issue, its what? 1-2 text files per map. If the maps popular enougth this should be a non issue, if not then those maps may finaly slip into the void where they belong, like tznex01.

[Silica Gel: Do Not Eat]

But - changing game_reset.cfg to also reset mutators is BAD, as it no longer allows you to run a Minstagib-only server!

If I wanted an minstagib-only server I could set the server.cfg and game_reset.cfg to g_minstagib 1

Wouldn't that Work? I'm very lazy