Mapping/Setting Up Survival Mode - Revision history

Erty: Added link to download a custom survival.fgd, as it's missing from the game files

2023-08-28T10:51:01Z

Added link to download a custom survival.fgd, as it's missing from the game files

← Older revision		Revision as of 12:51, 28 August 2023
Line 26:		Line 26:
	==Adding checkpoints with Map Editor(for custom maps)==		==Adding checkpoints with Map Editor(for custom maps)==

	To use the respawn point entity you must first add the survival.fgd file to the editor's configuration. This file can be found in ''\svencoop\scripts\maps\fgd''. Restart the editor and find ''point_checkpoint'' in the list.		To use the respawn point entity you must first add the survival.fgd[https://wiki.svencoop.com/images/b/b2/Survival.7z] file to the editor's configuration. This file can be found in ''\svencoop\scripts\maps\fgd''. Restart the editor and find ''point_checkpoint'' in the list.

	[[File:Hammer_800.png\|400px]]		[[File:Hammer_800.png\|400px]]

AdamR: AdamR moved page Setting Up Survival Mode to Mapping/Setting Up Survival Mode

2020-12-12T15:33:56Z

AdamR moved page Setting Up Survival Mode to Mapping/Setting Up Survival Mode

← Older revision		Revision as of 17:33, 12 December 2020
(No difference)

Hezus at 12:39, 25 March 2020

2020-03-25T12:39:36Z

← Older revision		Revision as of 14:39, 25 March 2020
Line 88:		Line 88:
	*mp_survival_startdelay - Delay (in seconds) before survival mode starts.		*mp_survival_startdelay - Delay (in seconds) before survival mode starts.
	*mp_survival_nextmap - Specifies the name of the next survival map in a series. This is useful if you have multiple maps in a series where Survival Mode settings should be carried across level changes.		*mp_survival_nextmap - Specifies the name of the next survival map in a series. This is useful if you have multiple maps in a series where Survival Mode settings should be carried across level changes.

			[[Category:Mapping]]
			[[Category:Tutorials]]

Hezus at 12:19, 25 March 2020

2020-03-25T12:19:14Z

← Older revision		Revision as of 14:19, 25 March 2020
Line 26:		Line 26:
	==Adding checkpoints with Map Editor(for custom maps)==		==Adding checkpoints with Map Editor(for custom maps)==

	~~If you're making a map and~~ you ~~have all of the source files, it is obviously a better idea to~~ add ~~checkpoint entities in~~ the ~~RMF~~ file ~~and compile the map with them than it would be~~ to ~~add checkpoints with Ripent after~~ the ~~map is already compiled. You really don~~'~~t need to load a special FGD to add a checkpoint to a map~~. ~~However, if you'd like to~~ be ~~able to select the entity from the dropdown list of entities, or to see a model preview of the entity~~ in ~~Hammer~~'~~s 3D view window, you~~'~~ll need to make an FGD or add an entry to~~ the ~~Sven Co-op FGD.~~		To use the respawn point entity you must first add the survival.fgd file to the editor's configuration. This file can be found in ''\svencoop\scripts\maps\fgd''. Restart the editor and find ''point_checkpoint'' in the list.

	~~The FGD entry that I use is as follows:~~

	:''~~@PointClass base(Targetname) studio("models/common/lambda.mdl") size(-8 -8 -8, 8 8 8) =~~ point_checkpoint ~~: "A respawn checkpoint" []'~~'

	~~If you don~~'~~t do this step, it will show up as a pink box~~ in ~~Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into~~ the ~~"Class" text entry box when creating the entity. No big deal. It will work the same~~.

	[[File:Hammer_800.png\|400px]]		[[File:Hammer_800.png\|400px]]

	All of the checkpoint entities in Sven Co-op's Half-Life maps are 48 units off of the ground, and will hover in the air at any height that you place them.		All of the checkpoint entities in Sven Co-op's Half-Life maps are 48 units off of the ground, and will hover in the air at any height that you place them.

	~~Now compile the map, and you're good to go.~~

	==Adding checkpoints with Ripent (for already-compiled maps)==		==Adding checkpoints with Ripent (for already-compiled maps)==

Hezus at 12:15, 25 March 2020

2020-03-25T12:15:54Z

← Older revision		Revision as of 14:15, 25 March 2020
Line 63:		Line 63:
	All you need to do now is insert "point_checkpoint" entities. First, though, you need to find coordinates where you'd like to add a checkpoint. Play through the map and find events where a lot of players might typically die. It is generally a good idea to place checkpoints after these events. When you reach a good checkpoint position, enter "status" into the console to get the coordinates where you're going to place the checkpoint.		All you need to do now is insert "point_checkpoint" entities. First, though, you need to find coordinates where you'd like to add a checkpoint. Play through the map and find events where a lot of players might typically die. It is generally a good idea to place checkpoints after these events. When you reach a good checkpoint position, enter "status" into the console to get the coordinates where you're going to place the checkpoint.

	[[File:Console 01 coordinates.png\|~~200px~~]]		[[File:Console 01 coordinates.png\|400px]]

	You can see the X-Y-Z coordinates of your position on the 'map' line. Scroll down to the bottom of the ENT file and add the following:		You can see the X-Y-Z coordinates of your position on the 'map' line. Scroll down to the bottom of the ENT file and add the following:
Line 83:		Line 83:
	Make sure the BSP is in the same folder as the ENT file, then drag and drop the ENT file into the import batch file.		Make sure the BSP is in the same folder as the ENT file, then drag and drop the ENT file into the import batch file.

	[[File:Bat import.png\|~~200px~~]]		[[File:Bat import.png\|400px]]

	The BSP file should now have a checkpoint entity at the coordinates specified in the ENT file. Load it up in-game to check.		The BSP file should now have a checkpoint entity at the coordinates specified in the ENT file. Load it up in-game to check.

Hezus at 12:15, 25 March 2020

2020-03-25T12:15:33Z

← Older revision		Revision as of 14:15, 25 March 2020
Line 22:		Line 22:
	With these scripts enabled, about 30 seconds after the map starts, respawning will be disabled and all players who die will be placed into 'observer mode' until a checkpoint is reached or all players are dead, at which point a vote will be called to either restart the map or change the level.		With these scripts enabled, about 30 seconds after the map starts, respawning will be disabled and all players who die will be placed into 'observer mode' until a checkpoint is reached or all players are dead, at which point a vote will be called to either restart the map or change the level.

	[[File:Cfg_01_runscript.png\|~~200px~~]]		[[File:Cfg_01_runscript.png\|400px]]

	==Adding checkpoints with Map Editor(for custom maps)==		==Adding checkpoints with Map Editor(for custom maps)==
Line 34:		Line 34:
	If you don't do this step, it will show up as a pink box in Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into the "Class" text entry box when creating the entity. No big deal. It will work the same.		If you don't do this step, it will show up as a pink box in Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into the "Class" text entry box when creating the entity. No big deal. It will work the same.

	[[File:Hammer_800.png\|~~200px~~]]		[[File:Hammer_800.png\|400px]]

	All of the checkpoint entities in Sven Co-op's Half-Life maps are 48 units off of the ground, and will hover in the air at any height that you place them.		All of the checkpoint entities in Sven Co-op's Half-Life maps are 48 units off of the ground, and will hover in the air at any height that you place them.
Line 53:		Line 53:
	Drag and drop the desired BSP file onto this batch file to export it to an ENT file. In this case, I'm adding checkpoints to svencoop1.bsp.		Drag and drop the desired BSP file onto this batch file to export it to an ENT file. In this case, I'm adding checkpoints to svencoop1.bsp.

	[[File:Bat_export.png\|~~200px~~]]		[[File:Bat_export.png\|400px]]

	Next, open the ENT file in a text editor.		Next, open the ENT file in a text editor.

	[[File:Entdata 01.png\|~~200px~~]]		[[File:Entdata 01.png\|400px]]

	The ENT file is literally a text list of every single entity in the map and all of their keyvalues. You can change any existing entity or add new ones. The only restriction is that you cannot add new brush models to a map that has already been compiled. You can only re-use brush models that are already in the map. But, since we're only adding checkpoints, that doesn't matter to us.		The ENT file is literally a text list of every single entity in the map and all of their keyvalues. You can change any existing entity or add new ones. The only restriction is that you cannot add new brush models to a map that has already been compiled. You can only re-use brush models that are already in the map. But, since we're only adding checkpoints, that doesn't matter to us.
Line 74:		Line 74:
	Where [X] [Y] [Z] are the coordinates, without the [] brackets.		Where [X] [Y] [Z] are the coordinates, without the [] brackets.

	[[File:Entdata 02.png\|~~200px~~]]		[[File:Entdata 02.png\|400px]]

	Once you're done adding checkpoints, make a batch file to import the map's entity data from the .ENT file back into the .BSP. Below is an example of my 'import' batch file, named "ENT_2_BSP.bat".		Once you're done adding checkpoints, make a batch file to import the map's entity data from the .ENT file back into the .BSP. Below is an example of my 'import' batch file, named "ENT_2_BSP.bat".
Line 87:		Line 87:
	The BSP file should now have a checkpoint entity at the coordinates specified in the ENT file. Load it up in-game to check.		The BSP file should now have a checkpoint entity at the coordinates specified in the ENT file. Load it up in-game to check.

	[[File:Svencoop1-2016-01-30-0013 800.png\|~~200px~~]]		[[File:Svencoop1-2016-01-30-0013 800.png\|400px]]

	==Map Configuration File CVARs==		==Map Configuration File CVARs==

Hezus: /* Adding checkpoints with Ripent (for already-compiled maps) */

2020-03-16T12:05:21Z

Adding checkpoints with Ripent (for already-compiled maps)

← Older revision		Revision as of 14:05, 16 March 2020
Line 48:		Line 48:
	In the same folder as ripent.exe, make a batch (.BAT) file to export the map's entity data to a .ENT file. Below is an example of my 'export' batch file, named "BSP_2_ENT.bat".		In the same folder as ripent.exe, make a batch (.BAT) file to export the map's entity data to a .ENT file. Below is an example of my 'export' batch file, named "BSP_2_ENT.bat".

	:''ripent.exe -export %1		:''ripent.exe -export %1''
	:pause''		:''pause''

	Drag and drop the desired BSP file onto this batch file to export it to an ENT file. In this case, I'm adding checkpoints to svencoop1.bsp.		Drag and drop the desired BSP file onto this batch file to export it to an ENT file. In this case, I'm adding checkpoints to svencoop1.bsp.
Line 67:		Line 67:
	You can see the X-Y-Z coordinates of your position on the 'map' line. Scroll down to the bottom of the ENT file and add the following:		You can see the X-Y-Z coordinates of your position on the 'map' line. Scroll down to the bottom of the ENT file and add the following:

	:''{		:''{''
	:"origin" "[X] [Y] [Z]"		:''"origin" "[X] [Y] [Z]"''
	:"classname" "point_checkpoint"		:''"classname" "point_checkpoint"''
	:}''		:''}''

	Where [X] [Y] [Z] are the coordinates, without the [] brackets.		Where [X] [Y] [Z] are the coordinates, without the [] brackets.
Line 78:		Line 78:
	Once you're done adding checkpoints, make a batch file to import the map's entity data from the .ENT file back into the .BSP. Below is an example of my 'import' batch file, named "ENT_2_BSP.bat".		Once you're done adding checkpoints, make a batch file to import the map's entity data from the .ENT file back into the .BSP. Below is an example of my 'import' batch file, named "ENT_2_BSP.bat".

	:''ripent.exe -import %1		:''ripent.exe -import %1''
	:pause''		:''pause''

	Make sure the BSP is in the same folder as the ENT file, then drag and drop the ENT file into the import batch file.		Make sure the BSP is in the same folder as the ENT file, then drag and drop the ENT file into the import batch file.

Hezus: /* Adding checkpoints with Ripent (for already-compiled maps) */

2020-03-16T12:04:33Z

Adding checkpoints with Ripent (for already-compiled maps)

← Older revision		Revision as of 14:04, 16 March 2020
Line 42:		Line 42:
	==Adding checkpoints with Ripent (for already-compiled maps)==		==Adding checkpoints with Ripent (for already-compiled maps)==

	Ripent is a very powerful tool that allows server operators to customize a map without forcing players to redownload the bsp, and will not result in "Map differs from server" errors when a player who already has the unmodified version of the map tries to connect to the server. This is the method that was utilized to place checkpoints in sc_another and YABMA, as the map source files are not available.		Ripent is a very powerful tool that allows server operators to customize a map without forcing players to redownload the bsp, and will not result in "Map differs from server" errors when a player who already has the unmodified version of the map tries to connect to the server. This is the method that was utilized to place checkpoints in sc_another and YABMA, as the map source files are not available. Ripent allows you to export a map's entity data, modify it, and put it back into the map. Sven Co-op includes Ripent.exe in the svencoop/maps folder.

	~~Ripent allows you to export a map's entity data, modify it, and put it back into the map. Sven Co-op includes Ripent.exe in the svencoop/maps folder.~~		Because it requires a command prompt to operate, I prefer to use batch files to export/import the entity data. Setting this up allows you to drag and drop a BSP or ENT file onto the batch file and convert the files without typing a bunch of stuff into a command prompt. It is also a good idea to make a separate 'ripent' folder, containing ripent.exe, your batch files, and whatever ENT or modified BSP files you're working on. Otherwise they just get mixed up in the maps folder.

	Because it requires a command prompt to operate, I prefer to use batch files to export/import the entity data. Setting this up allows you to drag and drop a BSP or ENT file onto the batch file and convert the files without typing a bunch of stuff into a command prompt.

	It is also a good idea to make a separate 'ripent' folder, containing ripent.exe, your batch files, and whatever ENT or modified BSP files you're working on. Otherwise they just get mixed up in the maps folder.

	In the same folder as ripent.exe, make a batch (.BAT) file to export the map's entity data to a .ENT file. Below is an example of my 'export' batch file, named "BSP_2_ENT.bat".		In the same folder as ripent.exe, make a batch (.BAT) file to export the map's entity data to a .ENT file. Below is an example of my 'export' batch file, named "BSP_2_ENT.bat".

	ripent.exe -export %1		:''ripent.exe -export %1
			:pause''

	~~pause~~		Drag and drop the desired BSP file onto this batch file to export it to an ENT file. In this case, I'm adding checkpoints to svencoop1.bsp.

	~~Drag and drop the desired BSP file onto this batch file to export it to an ENT file. In this case, I'm adding checkpoints to svencoop1.bsp~~.		[[File:Bat_export.png\|200px]]

	Next, open the ENT file in a text editor.		Next, open the ENT file in a text editor.

			[[File:Entdata 01.png\|200px]]

	The ENT file is literally a text list of every single entity in the map and all of their keyvalues. You can change any existing entity or add new ones. The only restriction is that you cannot add new brush models to a map that has already been compiled. You can only re-use brush models that are already in the map. But, since we're only adding checkpoints, that doesn't matter to us.		The ENT file is literally a text list of every single entity in the map and all of their keyvalues. You can change any existing entity or add new ones. The only restriction is that you cannot add new brush models to a map that has already been compiled. You can only re-use brush models that are already in the map. But, since we're only adding checkpoints, that doesn't matter to us.
Line 64:		Line 63:
	All you need to do now is insert "point_checkpoint" entities. First, though, you need to find coordinates where you'd like to add a checkpoint. Play through the map and find events where a lot of players might typically die. It is generally a good idea to place checkpoints after these events. When you reach a good checkpoint position, enter "status" into the console to get the coordinates where you're going to place the checkpoint.		All you need to do now is insert "point_checkpoint" entities. First, though, you need to find coordinates where you'd like to add a checkpoint. Play through the map and find events where a lot of players might typically die. It is generally a good idea to place checkpoints after these events. When you reach a good checkpoint position, enter "status" into the console to get the coordinates where you're going to place the checkpoint.

			[[File:Console 01 coordinates.png\|200px]]

	You can see the X-Y-Z coordinates of your position on the 'map' line. Scroll down to the bottom of the ENT file and add the following:		You can see the X-Y-Z coordinates of your position on the 'map' line. Scroll down to the bottom of the ENT file and add the following:

	{		:''{
	"origin" "[X] [Y] [Z]"		:"origin" "[X] [Y] [Z]"
	"classname" "point_checkpoint"		:"classname" "point_checkpoint"
	}		:}''

	Where [X] [Y] [Z] are the coordinates, without the [] brackets.		Where [X] [Y] [Z] are the coordinates, without the [] brackets.

			[[File:Entdata 02.png\|200px]]

	Once you're done adding checkpoints, make a batch file to import the map's entity data from the .ENT file back into the .BSP. Below is an example of my 'import' batch file, named "ENT_2_BSP.bat".		Once you're done adding checkpoints, make a batch file to import the map's entity data from the .ENT file back into the .BSP. Below is an example of my 'import' batch file, named "ENT_2_BSP.bat".

	ripent.exe -import %1		:''ripent.exe -import %1
			:pause''
	pause

	Make sure the BSP is in the same folder as the ENT file, then drag and drop the ENT file into the import batch file.		Make sure the BSP is in the same folder as the ENT file, then drag and drop the ENT file into the import batch file.

			[[File:Bat import.png\|200px]]

	The BSP file should now have a checkpoint entity at the coordinates specified in the ENT file. Load it up in-game to check.		The BSP file should now have a checkpoint entity at the coordinates specified in the ENT file. Load it up in-game to check.

			[[File:Svencoop1-2016-01-30-0013 800.png\|200px]]

	==Map Configuration File CVARs==		==Map Configuration File CVARs==

Hezus: /* Adding checkpoints with Map Editor(for custom maps) */

2020-03-16T11:58:05Z

Adding checkpoints with Map Editor(for custom maps)

← Older revision		Revision as of 13:58, 16 March 2020
Line 26:		Line 26:
	==Adding checkpoints with Map Editor(for custom maps)==		==Adding checkpoints with Map Editor(for custom maps)==

	If you're making a map and you have all of the source files, it is obviously a better idea to add checkpoint entities in the RMF file and compile the map with them than it would be to add checkpoints with Ripent after the map is already compiled.		If you're making a map and you have all of the source files, it is obviously a better idea to add checkpoint entities in the RMF file and compile the map with them than it would be to add checkpoints with Ripent after the map is already compiled. You really don't need to load a special FGD to add a checkpoint to a map. However, if you'd like to be able to select the entity from the dropdown list of entities, or to see a model preview of the entity in Hammer's 3D view window, you'll need to make an FGD or add an entry to the Sven Co-op FGD.

	You really don't need to load a special FGD to add a checkpoint to a map. However, if you'd like to be able to select the entity from the dropdown list of entities, or to see a model preview of the entity in Hammer's 3D view window, you'll need to make an FGD or add an entry to the Sven Co-op FGD.

	The FGD entry that I use is as follows:		The FGD entry that I use is as follows:

	:@PointClass base(Targetname) studio("models/common/lambda.mdl") size(-8 -8 -8, 8 8 8) = point_checkpoint : "A respawn checkpoint" []		:''@PointClass base(Targetname) studio("models/common/lambda.mdl") size(-8 -8 -8, 8 8 8) = point_checkpoint : "A respawn checkpoint" []''

			If you don't do this step, it will show up as a pink box in Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into the "Class" text entry box when creating the entity. No big deal. It will work the same.

	[[File:Hammer_800.png\|200px]]		[[File:Hammer_800.png\|200px]]

	If you don't do this step, it will show up as a pink box in Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into the "Class" text entry box when creating the entity. No big deal. It will work the same.

	All of the checkpoint entities in Sven Co-op's Half-Life maps are 48 units off of the ground, and will hover in the air at any height that you place them.		All of the checkpoint entities in Sven Co-op's Half-Life maps are 48 units off of the ground, and will hover in the air at any height that you place them.

Hezus: /* Adding checkpoints with Map Editor(for custom maps) */

2020-03-16T11:57:07Z

Adding checkpoints with Map Editor(for custom maps)

← Older revision		Revision as of 13:57, 16 March 2020
Line 31:		Line 31:

	The FGD entry that I use is as follows:		The FGD entry that I use is as follows:
	@PointClass base(Targetname) studio("models/common/lambda.mdl") size(-8 -8 -8, 8 8 8) = point_checkpoint : "A respawn checkpoint" []
			:@PointClass base(Targetname) studio("models/common/lambda.mdl") size(-8 -8 -8, 8 8 8) = point_checkpoint : "A respawn checkpoint" []

			[[File:Hammer_800.png\|200px]]

	If you don't do this step, it will show up as a pink box in Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into the "Class" text entry box when creating the entity. No big deal. It will work the same.		If you don't do this step, it will show up as a pink box in Hammer's 3D view, and you'll just have to manually type "point_checkpoint" into the "Class" text entry box when creating the entity. No big deal. It will work the same.