Nanoforge basics - Revision history

Camo: Added limit for multi_object_markers

2025-07-04T09:05:46Z

Added limit for multi_object_markers

← Older revision		Revision as of 09:05, 4 July 2025
Line 102:		Line 102:
	* Next, bottom left is the zone objects list. This lists the objects inside the selected zone. Click an object to see its properties in the properties panel. Some objects have child objects, denoted by having a triangle in front of their name which you can click to expand them. You can filter objects by type inside the filters header. By default some very common objects like navpoints are hidden.		* Next, bottom left is the zone objects list. This lists the objects inside the selected zone. Click an object to see its properties in the properties panel. Some objects have child objects, denoted by having a triangle in front of their name which you can click to expand them. You can filter objects by type inside the filters header. By default some very common objects like navpoints are hidden.
	* Finally, in the top right is the properties panel. This shows the properties of the selected zone object.		* Finally, in the top right is the properties panel. This shows the properties of the selected zone object.

			==Core concepts==
			* The total limit of <code>multi_object_markers</code> you can have on a single map is 25, if you exceed this spawn backpack / backpack racks, CTF, damage control & siege will all stop working.

	==Object Flags==		==Object Flags==

Moneyl at 23:43, 21 February 2024

2024-02-21T23:43:05Z

← Older revision		Revision as of 23:43, 21 February 2024
Line 3:		Line 3:

	This page goes over how to install Nanoforge and it's basic features. This article only goes over the basics of each feature. See the other guides for more detailed explanations.		This page goes over how to install Nanoforge and it's basic features. This article only goes over the basics of each feature. See the other guides for more detailed explanations.

			===IMPORTANT NOTE===
			Nanoforge was rewritten starting with version v1.0.0. At the time of writing that version only has a map editor for multiplayer and wrecking crew maps. The other editors will return in future releases. If you're editing MP/WC maps it recommended that you use the latest version of Nanoforge. It has many improvements to the map editor. If you want to use features that are still missing in the rewrite such as the texture and mesh exporters, you should use v0.21.1

	==Installation==		==Installation==

Camo: /* Spectator Cameras */

2023-06-25T03:29:34Z

Spectator Cameras

← Older revision		Revision as of 03:29, 25 June 2023
Line 202:		Line 202:
	* Believed to be similar to a <code>Spawn node</code> but used exclusively by players using the spectator option in matchmaking. Recommended to just ignore adding these since the community only plays custom games and adding <code>Spawn nodes</code> to your map will serve the same purpose.		* Believed to be similar to a <code>Spawn node</code> but used exclusively by players using the spectator option in matchmaking. Recommended to just ignore adding these since the community only plays custom games and adding <code>Spawn nodes</code> to your map will serve the same purpose.
	* Foward X axis (blue line) determines player camera direction & view.		* Foward X axis (blue line) determines player camera direction & view.
	* These camera views are also shared with <code>Spawn nodes</code> at start of match or when a player dies and is spectating.

	==Mover Types==		==Mover Types==

Camo: /* Bagman Objective Spawn */

2023-06-21T05:08:38Z

Bagman Objective Spawn

← Older revision		Revision as of 05:08, 21 June 2023
Line 259:		Line 259:
	* Ignore the varying bounding box sizes when positioning the bag spawn, the XYZ axis position is what matters (the red, blue & green lines).		* Ignore the varying bounding box sizes when positioning the bag spawn, the XYZ axis position is what matters (the red, blue & green lines).
	* The <code>respawn</code> boolean doesn't do what you expect, the bag will still return to the original spawn point regardless if it's enabled or not.		* The <code>respawn</code> boolean doesn't do what you expect, the bag will still return to the original spawn point regardless if it's enabled or not.
	* You can't place more than one bag on a map, only one will spawn.		* You can't place more than one bag on a map normally, only one will spawn. However you can have different bag locations in Bagman and Team Bagman by using the gamemode flags.
	* You can have different bag locations in Bagman and Team Bagman by using the gamemode flags.

	==Weapon Spawns==		==Weapon Spawns==

Camo: /* Shape Cutters */

2023-06-21T04:29:00Z

Shape Cutters

← Older revision		Revision as of 04:29, 21 June 2023
Line 286:		Line 286:
	==Shape Cutters==		==Shape Cutters==
	* Used to damage or cut holes into destructible objects ahead of time.		* Used to damage or cut holes into destructible objects ahead of time.
	* <code>outer_radius</code> ~~= Unknown~~.		* <code>outer_radius</code> might control the size of the cutter, but this is untested.

	==Maps with names different from their in-game names==		==Maps with names different from their in-game names==

Camo: /* Trigger Regions */

2023-06-21T04:28:39Z

Trigger Regions

← Older revision		Revision as of 04:28, 21 June 2023
Line 274:		Line 274:
	* In singleplayer the <code>trigger_flags</code> can be changed so the trigger isn't enabled during missions and/or activities. Eg. <code>not_in_mission</code> will disable it during a main mission, <code>not_in_activity</code> would disable it during a side activity and <code>not_in_mission not_in_activity</code> would disable it during both.		* In singleplayer the <code>trigger_flags</code> can be changed so the trigger isn't enabled during missions and/or activities. Eg. <code>not_in_mission</code> will disable it during a main mission, <code>not_in_activity</code> would disable it during a side activity and <code>not_in_mission not_in_activity</code> would disable it during both.
	* The <code>enabled</code> boolean allows mappers to enable/disable the region.		* The <code>enabled</code> boolean allows mappers to enable/disable the region.
			* The <code>trigger_shape</code> can be set to a <code>box</code> or <code>sphere</code>. However Nanoforge cannot render spherical bounding boxes yet.
			* <code>outer_radius</code> might control the size of the region, but this is untested.

	==Object Effects==		==Object Effects==

Camo: /* Object Info */

2023-06-21T04:25:31Z

Object Info

← Older revision		Revision as of 04:25, 21 June 2023
Line 174:		Line 174:
	* <code>object_mission_start_node</code> = Probably where you can start a main mission.		* <code>object_mission_start_node</code> = Probably where you can start a main mission.
	* <code>object_restricted_area</code> = Probably where the EDF will attack on sight and you will get an alert level in SP.		* <code>object_restricted_area</code> = Probably where the EDF will attack on sight and you will get an alert level in SP.
			* <code>backpack_effect_attach.cchk_pc</code> = Seems to be for attaching the backpack to the player when they spawn, DO NOT TOUCH IT ALL OR THE MAP WILL CRASH WHEN SPAWNING.

	==Object Properties==		==Object Properties==

Camo: /* Capture the Flag targets */

2023-06-10T00:54:43Z

Capture the Flag targets

← Older revision		Revision as of 00:54, 10 June 2023
Line 251:		Line 251:
	* Make sure you use deep cloning and only move the parent when placing or moving them so the child is offset correctly.		* Make sure you use deep cloning and only move the parent when placing or moving them so the child is offset correctly.
	* Objects are called <code>edf_flag_stand.cchk_pc</code> & <code>guerrilla_flag_stand.cchk_pc</code>.		* Objects are called <code>edf_flag_stand.cchk_pc</code> & <code>guerrilla_flag_stand.cchk_pc</code>.
	* If you attempt to add more than two stands to a map, the ~~extra two~~ will not work as capture points and only the asset will appear.		* If you attempt to add more than two stands to a map, the extras will not work as capture points and only the asset will appear.
	* <code>Neutral</code> is not a valid value for <code>mp_team</code>.		* <code>Neutral</code> is not a valid value for <code>mp_team</code>.

Camo: /* Capture the Flag targets */

2023-06-10T00:53:58Z

Capture the Flag targets

← Older revision		Revision as of 00:53, 10 June 2023
Line 250:		Line 250:
	* The EDF and Red Faction have their own unique flag stand placed near their team spawns on regular multiplayer maps.		* The EDF and Red Faction have their own unique flag stand placed near their team spawns on regular multiplayer maps.
	* Make sure you use deep cloning and only move the parent when placing or moving them so the child is offset correctly.		* Make sure you use deep cloning and only move the parent when placing or moving them so the child is offset correctly.
	* Objects are called <code>edf_flag_stand.cchk_pc</code>, <code>guerrilla_flag_stand.cchk_pc</code>.		* Objects are called <code>edf_flag_stand.cchk_pc</code> & <code>guerrilla_flag_stand.cchk_pc</code>.
	* If you attempt to add more than two stands to a map, the extra two will not work as capture points and only the asset will appear.		* If you attempt to add more than two stands to a map, the extra two will not work as capture points and only the asset will appear.
	* <code>Neutral</code> is not a valid value for <code>mp_team</code>.		* <code>Neutral</code> is not a valid value for <code>mp_team</code>.

Camo: /* Object Flags */

2023-06-10T00:52:47Z

Object Flags

← Older revision		Revision as of 00:52, 10 June 2023
Line 105:		Line 105:
	* Flag 2: Unknown		* Flag 2: Unknown
	* Flag 3: Unknown; might be related to how the game saves/loads map data from save files (requires more investigation)		* Flag 3: Unknown; might be related to how the game saves/loads map data from save files (requires more investigation)
	* Flag 4: Unknown; seems to always get converted to the runtime flag <code>streaming_fixed</code>, most <code>rfg_movers</code> and <code>general_movers</code> have this flag. If you're using the Terraform Patch it's recommended you don't disable this flag as it applies it to all objects since it was used most of the time and objects missing it were assumed to be an error by Volition. (They also made mistakes with the gamemode flags)		* Flag 4: Unknown; seems to always get converted to the runtime flag <code>streaming_fixed</code>, most <code>rfg_movers</code> and <code>general_movers</code> have this flag. If you're using the Terraform Patch it's recommended you don't disable this flag as it applies it to all objects since it was used most of the time and objects missing it were assumed to be an error by Volition. (They also made mistakes with the gamemode and persistent flags)
	* Flag 5: Unknown; seems to get converted to the runtime flag <code>force_full_save</code>		* Flag 5: Unknown; seems to get converted to the runtime flag <code>force_full_save</code>
	* Flag 6: Unknown		* Flag 6: Unknown