Multi-Part Buildables - Revision history

Administrator at 18:03, 22 June 2007

2007-06-22T18:03:21Z

← Older revision		Revision as of 18:03, 22 June 2007
Line 49:		Line 49:
	==Team Changes==		==Team Changes==
	===This section has not been written yet.===		===This section has not been written yet.===

			[[Category:Mapping\|Multi-Part Buildables]]

Reginald2710 at 13:19, 21 March 2007

2007-03-21T13:19:17Z

← Older revision		Revision as of 13:19, 21 March 2007
Line 9:		Line 9:
	You should be familiar with the concept of entities, and how they can have attributes, inputs and outputs. What you may not know is that all the entities available to you in the Hammer editor are defined in a text file, with the extension "''.fgd''". It is necessary for us to first make some changes to this file, in order to grant us access to some features that are not present in the default Empires install.		You should be familiar with the concept of entities, and how they can have attributes, inputs and outputs. What you may not know is that all the entities available to you in the Hammer editor are defined in a text file, with the extension "''.fgd''". It is necessary for us to first make some changes to this file, in order to grant us access to some features that are not present in the default Empires install.

	~~# First of all,~~ we ~~have to find the ''".fgd"'' file. Now this will usually be in ''"Steam/SteamApps/SourceMods/Empires/mapsrc/fgd"'', and will be named ''"empires.fgd"''~~		The feature that we're most interested in is the onKill output of the [[emp_eng_map_brush]] entity. Details on how to add this can be found [[Useful_FGD_Modifications#OnKill \| here]].
	~~# Before making any changes, backup the file by creating a copy and naming it '~~'~~"empires.fgd.backup"''. Should anything go wrong, you can always revert to this file.~~
	~~# Open the original file~~ in ~~notepad, and find the following line: '''"@SolidClass base(Targetname) = emp_eng_map_brush :"'''. This~~ is ~~where~~ the ~~definition for~~ the [[emp_eng_map_brush]] ~~(the~~ entity ~~that we will be modifying) begins~~.
	~~# Beneath~~ this ~~line, locate the output section, which should~~ be ~~a group of lines, each beginning with the word ''"output"''. There should exist one entry for the object being constructed by the Northern Faction team, and another for the Brenodi Empire.~~
	# ~~After these two lines, add the following: '''"output~~ OnKill(void) : "Output for destruction of the object."'''. This will provide us with an output in hammer which fires when the object is destroyed. This output forms the cornerstone of the whole multi-part method.
	~~# Save the file~~.

	~~Now that~~ you have your ''"empires.fgd"'' set up correctly, you can launch ~~into~~ hammer and start putting your object together.		Once you have your ''"empires.fgd"'' set up correctly, you can launch hammer and start putting your object together.

	{{Note\|Re-installing or upgrading to a new version will most probably overwrite your fgd file. For this reason, it is advisable to check that this line is present after every change to your installation.}}

	==Creating the Object==		==Creating the Object==

Reginald2710: /* This is a work in progress tutorial, actively under development by Broccoli. */

2007-01-25T16:50:21Z

This is a work in progress tutorial, actively under development by Broccoli.

← Older revision		Revision as of 16:50, 25 January 2007
Line 55:		Line 55:

	==Team Changes==		==Team Changes==
	===This ~~is a work in progress tutorial, actively under development by Broccoli~~.===		===This section has not been written yet.===

Reginald2710 at 09:06, 23 January 2007

2007-01-23T09:06:36Z

← Older revision		Revision as of 09:06, 23 January 2007
Line 1:		Line 1:
	{{Sitenav\|[[Mapping]] > Multi-Part Buildables}}		{{Sitenav\|[[Mapping]] > Multi-Part Buildables}}

	~~===This is a work in progress tutorial, actively under development by Broccoli.===~~

	This is a guide to creating '''multi-part buildable objects'''. These are the kinds of objects that are built in stages, for example an upgradeable bunker, or a tower that gets taller as more sections are built. This guide only covers brush-based buildables, though the principle would remain the same for model-based ones.		This is a guide to creating '''multi-part buildable objects'''. These are the kinds of objects that are built in stages, for example an upgradeable bunker, or a tower that gets taller as more sections are built. This guide only covers brush-based buildables, though the principle would remain the same for model-based ones.
Line 7:		Line 5:
	Before you begin, I would recommend reading the [[Engineer-Buildable Objects\|basic tutorial]], covering single-part buildables.		Before you begin, I would recommend reading the [[Engineer-Buildable Objects\|basic tutorial]], covering single-part buildables.

	# You should be familiar with the concept of entities, and how they can have attributes, inputs and outputs. What you may not know is that all the entities available to you in the Hammer editor are defined in a text file, with the extension "''.fgd''". It is necessary for us to first make some changes to this file, in order to grant us access to some features that are not present in the default Empires install.		==Editing the FGD==
	## First of all, we have to find the ''".fgd"'' file. Now this will usually be in ''"Steam/SteamApps/SourceMods/Empires/mapsrc/fgd"'', and will be named ''"empires.fgd"''
	## Before making any changes, backup the file by creating a copy and naming it ''"empires.fgd.backup"''. Should anything go wrong, you can always revert to this file.		You should be familiar with the concept of entities, and how they can have attributes, inputs and outputs. What you may not know is that all the entities available to you in the Hammer editor are defined in a text file, with the extension "''.fgd''". It is necessary for us to first make some changes to this file, in order to grant us access to some features that are not present in the default Empires install.
	## Open the original file in notepad, and find the following line: '''"@SolidClass base(Targetname) = emp_eng_map_brush :"'''. This is where the definition for the [[emp_eng_map_brush]] (the entity that we will be modifying) begins.
	## Beneath this line, locate the output section, which should be a group of lines, each beginning with the word ''"output"''. There should exist one entry for the object being constructed by the Northern Faction team, and another for the Brenodi Empire.		# First of all, we have to find the ''".fgd"'' file. Now this will usually be in ''"Steam/SteamApps/SourceMods/Empires/mapsrc/fgd"'', and will be named ''"empires.fgd"''
	## After these two lines, add the following: '''"output OnKill(void) : "Output for destruction of the object."'''. This will provide us with an output in hammer which fires when the object is destroyed. This output forms the cornerstone of the whole multi-part method.		# Before making any changes, backup the file by creating a copy and naming it ''"empires.fgd.backup"''. Should anything go wrong, you can always revert to this file.
	## Save the file.		# Open the original file in notepad, and find the following line: '''"@SolidClass base(Targetname) = emp_eng_map_brush :"'''. This is where the definition for the [[emp_eng_map_brush]] (the entity that we will be modifying) begins.
	# Now that you have your ''"empires.fgd"'' set up correctly, you can launch into hammer and start putting your object together.		# Beneath this line, locate the output section, which should be a group of lines, each beginning with the word ''"output"''. There should exist one entry for the object being constructed by the Northern Faction team, and another for the Brenodi Empire.
	## In this tutorial, I will be creating a tower that is to be built in three stages.		# After these two lines, add the following: '''"output OnKill(void) : "Output for destruction of the object."'''. This will provide us with an output in hammer which fires when the object is destroyed. This output forms the cornerstone of the whole multi-part method.
	## Firstly, create the brushwork that will form the base for your first stage. In my case, this would be the lowest section of my tower.		# Save the file.
	## Select all parts of your first stage, and press Ctrl-T to tie them to an [[emp_eng_map_brush]].
	## Now, create your second stage. You do not need to duplicate the brushwork that forms your first stage, just create the parts that extend it.		Now that you have your ''"empires.fgd"'' set up correctly, you can launch into hammer and start putting your object together.
	## Select it, and tie it to another [[emp_eng_map_brush]], as you did with your first stage.
	## Repeat the process for your third and final stage. Now you should have three separate entities, each of which form one stage of your completed object.		{{Note\|Re-installing or upgrading to a new version will most probably overwrite your fgd file. For this reason, it is advisable to check that this line is present after every change to your installation.}}
	## Give each stage a meaningful name. Mine are called ''"tower_bottom"'', ''"tower_middle"'' and ''"tower_top"''.
	## For the moment, my tower is owned exclusively by the Northern Faction (team changes will be covered later on). So set the bottom section's '''"Initial Owner"''' to '''"Northern Faction"'''.		==Creating the Object==
	## Because I only want the bottom section to be buildable from the beginning, the upper sections must start disabled. To do this, set their '''"Initial Owner"''' to '''"No Owner (Disabled)"'''.
	## The other properties, such as ''"Initial Health"'', ''"Max Health"'' and ''"Raise Object On Build"'', can all be set as you wish.		In this tutorial, I will be creating a tower that is to be built in three stages.
	~~## Now here~~ is the principal on which my tower operates:
	~~###~~ When the bottom is built, I enable the middle.		# Firstly, create the brushwork that will form the base for your first stage. In my case, this would be the lowest section of my tower.
	~~###~~ When the middle is built, I enable the top.		# Select all parts of your first stage, and press Ctrl-T to tie them to an [[emp_eng_map_brush]].
	~~###~~ When the top is built, I don't do anything!		# Now, create your second stage. You do not need to duplicate the brushwork that forms your first stage, just create the parts that extend it.
	~~###~~ When the top is destroyed, I don't do anything.		# Select it, and tie it to another [[emp_eng_map_brush]], as you did with your first stage.
	~~###~~ When the middle is destroyed, I destroy the top.		# Repeat the process for your third and final stage. Now you should have three separate entities, each of which form one stage of your completed object.
	~~###~~ When the bottom is destroyed, I destroy the middle and the top.		# Give each stage a meaningful name. Mine are called ''"tower_bottom"'', ''"tower_middle"'' and ''"tower_top"''.
	## Now that we've established these rules, we quite simply translate them into a format that Hammer's I/O system can understand.		# For the moment, my tower is owned exclusively by the Northern Faction (team changes will be covered later on). So set the bottom section's '''"Initial Owner"''' to '''"Northern Faction"'''.
	~~###~~ For '''tower_bottom''', add the output '''OnNFBuilt''' to target '''tower_middle''' with '''InputNFEnable'''.		# Because I only want the bottom section to be buildable from the beginning, the upper sections must start disabled. To do this, set their '''"Initial Owner"''' to '''"No Owner (Disabled)"'''.
	~~###~~ For '''tower_bottom''', add the output '''OnKill''' to target '''tower_middle''' with '''InputDisable'''.		# The other properties, such as ''"Initial Health"'', ''"Max Health"'' and ''"Raise Object On Build"'', can all be set as you wish.
	~~###~~ For '''tower_bottom''', add the output '''OnKill''' to target '''tower_top''' with '''InputDisable'''.
	~~###~~ For '''tower_middle''', add the output '''OnNFBuilt''' to target '''tower_top''' with '''InputNFEnable'''.		==Making it Work==
	~~###~~ For '''tower_middle''', add the output '''OnKill''' to target '''tower_top''' with '''InputDisable'''.
	# And that's it! Your structure is now complete. You can compile your level at this stage, and you should be able to see it in action. What follows is an explanation of how to deal with your structure changing teams in co-ordination with the ownership of a flag.		Here is the principal on which my tower operates:
			* When the bottom is built, I enable the middle.
			* When the middle is built, I enable the top.
			* When the top is built, I don't do anything!
			* When the top is destroyed, I don't do anything.
			* When the middle is destroyed, I destroy the top.
			* When the bottom is destroyed, I destroy the middle and the top.

			Now that we've established these rules, we quite simply translate them into a format that Hammer's I/O system can understand.
			* For '''tower_bottom''', add the output '''OnNFBuilt''' to target '''tower_middle''' with '''InputNFEnable'''.
			* For '''tower_bottom''', add the output '''OnKill''' to target '''tower_middle''' with '''InputDisable'''.
			* For '''tower_bottom''', add the output '''OnKill''' to target '''tower_top''' with '''InputDisable'''.
			* For '''tower_middle''', add the output '''OnNFBuilt''' to target '''tower_top''' with '''InputNFEnable'''.
			* For '''tower_middle''', add the output '''OnKill''' to target '''tower_top''' with '''InputDisable'''.

			And that's it!
			Your structure is now complete. You can compile your level at this stage, and you should be able to see it in action. What follows is an explanation of how to deal with your structure changing teams in co-ordination with the ownership of a flag.

			==Team Changes==
			===This is a work in progress tutorial, actively under development by Broccoli.===

Reginald2710 at 08:58, 23 January 2007

2007-01-23T08:58:24Z

← Older revision		Revision as of 08:58, 23 January 2007
Line 15:		Line 15:
	## Save the file.		## Save the file.
	# Now that you have your ''"empires.fgd"'' set up correctly, you can launch into hammer and start putting your object together.		# Now that you have your ''"empires.fgd"'' set up correctly, you can launch into hammer and start putting your object together.
	## In this tutorial, I will be creating ~~an object~~ that is to be built in three stages. Firstly, create the brushwork that will form the base for your first stage. In my case, this would be the lowest section of my tower.		## In this tutorial, I will be creating a tower that is to be built in three stages.
			## Firstly, create the brushwork that will form the base for your first stage. In my case, this would be the lowest section of my tower.
	## Select all parts of your first stage, and press Ctrl-T to tie them to an [[emp_eng_map_brush]].		## Select all parts of your first stage, and press Ctrl-T to tie them to an [[emp_eng_map_brush]].
	## Now, create your second stage. You do not need to duplicate the brushwork that forms your first stage, just create the parts that extend it.		## Now, create your second stage. You do not need to duplicate the brushwork that forms your first stage, just create the parts that extend it.
Line 21:		Line 22:
	## Repeat the process for your third and final stage. Now you should have three separate entities, each of which form one stage of your completed object.		## Repeat the process for your third and final stage. Now you should have three separate entities, each of which form one stage of your completed object.
	## Give each stage a meaningful name. Mine are called ''"tower_bottom"'', ''"tower_middle"'' and ''"tower_top"''.		## Give each stage a meaningful name. Mine are called ''"tower_bottom"'', ''"tower_middle"'' and ''"tower_top"''.
	## --set disabled~~/enabled attributes--~~		## For the moment, my tower is owned exclusively by the Northern Faction (team changes will be covered later on). So set the bottom section's '''"Initial Owner"''' to '''"Northern Faction"'''.
			## Because I only want the bottom section to be buildable from the beginning, the upper sections must start disabled. To do this, set their '''"Initial Owner"''' to '''"No Owner (Disabled)"'''.
			## The other properties, such as ''"Initial Health"'', ''"Max Health"'' and ''"Raise Object On Build"'', can all be set as you wish.
	## Now here is the principal on which my tower operates:		## Now here is the principal on which my tower operates:
	### When the bottom is built, I enable the middle.		### When the bottom is built, I enable the middle.
Line 28:		Line 31:
	### When the top is destroyed, I don't do anything.		### When the top is destroyed, I don't do anything.
	### When the middle is destroyed, I destroy the top.		### When the middle is destroyed, I destroy the top.
	### When the bottom is destroyed, I destroy the middle.		### When the bottom is destroyed, I destroy the middle and the top.
	## Now that we've established these rules, we quite simply translate them into a format that Hammer's I/O system can understand. For ~~the moment~~, ~~my tower is owned exclusively by~~ the ~~Northern Faction. We will deal~~ with ~~team changes later on~~.		## Now that we've established these rules, we quite simply translate them into a format that Hammer's I/O system can understand.
	### For '''tower_bottom''', add the output '''~~OnBuiltNF~~''' to target '''tower_middle''' with '''~~enableNF~~'''.		### For '''tower_bottom''', add the output '''OnNFBuilt''' to target '''tower_middle''' with '''InputNFEnable'''.
	### For '''tower_bottom''', add the output '''OnKill''' to target '''~~tower_middle~~''' with '''~~disable~~'''.		### For '''tower_bottom''', add the output '''OnKill''' to target '''tower_middle''' with '''InputDisable'''.
	### For '''tower_middle''', add the output '''~~OnBuiltNF~~''' to target '''tower_top''' with '''~~enableNF~~'''.		### For '''tower_bottom''', add the output '''OnKill''' to target '''tower_top''' with '''InputDisable'''.
	### For '''tower_middle''', add the output '''OnKill''' to target '''tower_top''' with '''~~disable~~'''.		### For '''tower_middle''', add the output '''OnNFBuilt''' to target '''tower_top''' with '''InputNFEnable'''.
			### For '''tower_middle''', add the output '''OnKill''' to target '''tower_top''' with '''InputDisable'''.
	# And that's it! Your structure is now complete. You can compile your level at this stage, and you should be able to see it in action. What follows is an explanation of how to deal with your structure changing teams in co-ordination with the ownership of a flag.		# And that's it! Your structure is now complete. You can compile your level at this stage, and you should be able to see it in action. What follows is an explanation of how to deal with your structure changing teams in co-ordination with the ownership of a flag.

Reginald2710 at 21:16, 22 January 2007

2007-01-22T21:16:25Z

@@ Line 19: / Line 19: @@
 ## Now, create your second stage. You do not need to duplicate the brushwork that forms your first stage, just create the parts that extend it.
 ## Select it, and tie it to another [[emp_eng_map_brush]], as you did with your first stage.
-## Repeat the process for your third and final stage.
+## Repeat the process for your third and final stage. Now you should have three separate entities, each of which form one stage of your completed object.
-## Now you should have three separate entities, each of which form one stage of your completed object.
+## Give each stage a meaningful name. Mine are called ''"tower_bottom"'', ''"tower_middle"'' and ''"tower_top"''.
-# Compile and test
+## --set disabled/enabled attributes--

Reginald2710 at 20:53, 22 January 2007

2007-01-22T20:53:37Z

← Older revision		Revision as of 20:53, 22 January 2007
Line 3:		Line 3:
	===This is a work in progress tutorial, actively under development by Broccoli.===		===This is a work in progress tutorial, actively under development by Broccoli.===

	This is a guide to creating '''multi-part buildable objects'''. These are the kinds of objects that are built in stages, for example an upgradeable bunker, or a tower that gets taller as more sections are built.		This is a guide to creating '''multi-part buildable objects'''. These are the kinds of objects that are built in stages, for example an upgradeable bunker, or a tower that gets taller as more sections are built. This guide only covers brush-based buildables, though the principle would remain the same for model-based ones.

	Before you begin, I would recommend reading the [[Engineer-Buildable Objects\|basic tutorial]], covering single-part buildables.		Before you begin, I would recommend reading the [[Engineer-Buildable Objects\|basic tutorial]], covering single-part buildables.

	# ~~Create~~ the fgd ~~entry~~		# You should be familiar with the concept of entities, and how they can have attributes, inputs and outputs. What you may not know is that all the entities available to you in the Hammer editor are defined in a text file, with the extension "''.fgd''". It is necessary for us to first make some changes to this file, in order to grant us access to some features that are not present in the default Empires install.
	## ~~Find~~ line		## First of all, we have to find the ''".fgd"'' file. Now this will usually be in ''"Steam/SteamApps/SourceMods/Empires/mapsrc/fgd"'', and will be named ''"empires.fgd"''
	## ~~Edit~~ line		## Before making any changes, backup the file by creating a copy and naming it ''"empires.fgd.backup"''. Should anything go wrong, you can always revert to this file.
	# ~~Set~~ up the entities		## Open the original file in notepad, and find the following line: '''"@SolidClass base(Targetname) = emp_eng_map_brush :"'''. This is where the definition for the [[emp_eng_map_brush]] (the entity that we will be modifying) begins.
			## Beneath this line, locate the output section, which should be a group of lines, each beginning with the word ''"output"''. There should exist one entry for the object being constructed by the Northern Faction team, and another for the Brenodi Empire.
			## After these two lines, add the following: '''"output OnKill(void) : "Output for destruction of the object."'''. This will provide us with an output in hammer which fires when the object is destroyed. This output forms the cornerstone of the whole multi-part method.
			## Save the file.
			# Now that you have your ''"empires.fgd"'' set up correctly, you can launch into hammer and start putting your object together.
			## In this tutorial, I will be creating an object that is to be built in three stages. Firstly, create the brushwork that will form the base for your first stage. In my case, this would be the lowest section of my tower.
			## Select all parts of your first stage, and press Ctrl-T to tie them to an [[emp_eng_map_brush]].
			## Now, create your second stage. You do not need to duplicate the brushwork that forms your first stage, just create the parts that extend it.
			## Select it, and tie it to another [[emp_eng_map_brush]], as you did with your first stage.
			## Repeat the process for your third and final stage.
			## Now you should have three separate entities, each of which form one stage of your completed object.
	# Compile and test		# Compile and test

Reginald2710 at 20:21, 22 January 2007

2007-01-22T20:21:43Z

← Older revision		Revision as of 20:21, 22 January 2007
Line 1:		Line 1:
	{{Sitenav\|[[Mapping]] > Multi-Part Buildables}}		{{Sitenav\|[[Mapping]] > Multi-Part Buildables}}

	This is a work in progress tutorial, actively under development by Broccoli.		===This is a work in progress tutorial, actively under development by Broccoli.===

			This is a guide to creating '''multi-part buildable objects'''. These are the kinds of objects that are built in stages, for example an upgradeable bunker, or a tower that gets taller as more sections are built.

			Before you begin, I would recommend reading the [[Engineer-Buildable Objects\|basic tutorial]], covering single-part buildables.

			# Create the fgd entry
			## Find line
			## Edit line
			# Set up the entities
			# Compile and test

Reginald2710 at 20:08, 22 January 2007

2007-01-22T20:08:10Z

New page

{{Sitenav|[[Mapping]] > Multi-Part Buildables}}

This is a work in progress tutorial, actively under development by Broccoli.