Loading Level Resources With Lua - Revision history

Alazar88: /* Loading Resource Files */

2021-09-30T01:25:17Z

Loading Resource Files

← Older revision		Revision as of 01:25, 30 September 2021
Line 14:		Line 14:
	For example, if you execute this code, then whenever you define swapLevel as an internal level name ("Graveyard","Barrens",etc) the next level's resources will all be replaced with the ones from Level_''swapLevel'':		For example, if you execute this code, then whenever you define swapLevel as an internal level name ("Graveyard","Barrens",etc) the next level's resources will all be replaced with the ones from Level_''swapLevel'':

	~~<div class="toccolours mw-collapsible mw-collapsed">~~		{{Collapse\|1=<pre>
	~~<div style~~=~~"font-weight:bold;line-height:1.6;">Example code mod for swapping resources between levels~~<~~/div~~>		swapLevel = ""
	~~<div class="mw-collapsible-content">~~

	~~<nowiki>~~swapLevel = ""

	function QueueResourcesForLoad( resManager, resTbl, alloc )		function QueueResourcesForLoad( resManager, resTbl, alloc )
Line 60:		Line 57:
	end		end
	end		end
	</~~nowiki>~~		</pre>\|2=Example code mod for swapping resources between levels}}
	~~</div></div~~>

	"Script" resources are Lua files embedded in Journey.exe, but all other resources are loaded from the game folders.		"Script" resources are Lua files embedded in Journey.exe, but all other resources are loaded from the game folders.
Line 72:		Line 68:

	Here is a sample of the contents of resTbl as it gets passed to QueueResourcesForLoad:		Here is a sample of the contents of resTbl as it gets passed to QueueResourcesForLoad:
	~~<div class="toccolours mw-collapsible mw-collapsed">~~
	~~<div style~~=~~"font-weight:bold;line-height:1.6;">Format of resource tables loaded when level starts~~<~~/div~~>		{{Collapse\|1=<pre>
	~~<div class="mw-collapsible-content">~~		{
	~~<nowiki>~~{
	{		{
	class = "ScreamBank",		class = "ScreamBank",
Line 163:		Line 158:
	source = "Level_Graveyard/DuneColorShadow.dds"		source = "Level_Graveyard/DuneColorShadow.dds"
	}		}
	}</~~nowiki></div></div~~>		}
			</pre>\|2=Format of resource tables loaded when level starts}}

	==Adding/Modifying Individual Level Objects ==		==Adding/Modifying Individual Level Objects ==
	'''Important things to remember'''		'''Important things to remember'''

Alazar88: /* Decoration Meshes */

2021-09-25T21:33:23Z

Decoration Meshes

← Older revision		Revision as of 21:33, 25 September 2021
Line 328:		Line 328:
	They can definitely have individual variables modified by running <code>Names["The DM's ObjectName"]:function</code> with the same kind of code found inside the DecorationInitialize function (found in DecorationMeshes.lua);		They can definitely have individual variables modified by running <code>Names["The DM's ObjectName"]:function</code> with the same kind of code found inside the DecorationInitialize function (found in DecorationMeshes.lua);

	for example <code>Names["ObjectName"]:SetMatrix( Transformation~~, see~~ below )</code> will change the rotation/scale/position of the mesh.		for example <code>Names["ObjectName"]:SetMatrix( Transformation formatted like below )</code> will change the rotation/scale/position of the mesh.

	Here is basically how the Decoration Mesh constructor table is formatted (this is the Sphinx in Level_Graveyard):		Here is basically how the Decoration Mesh constructor table is formatted (this is the Sphinx in Level_Graveyard):
Line 334:		Line 334:
	<div style="font-weight:bold;line-height:1.6;">Example of non-binarized Decoration Mesh constructor</div>		<div style="font-weight:bold;line-height:1.6;">Example of non-binarized Decoration Mesh constructor</div>
	<div class="mw-collapsible-content">		<div class="mw-collapsible-content">
	<nowiki>{		<nowiki> {
	ObjectName = "ecd9205156899a8ad85b0dc3eb91313c"		ObjectName = "ecd9205156899a8ad85b0dc3eb91313c"
	, GardenerName = "\|Decoration549\|Decoration549_G"		, GardenerName = "\|Decoration549\|Decoration549_G"
Line 410:		Line 410:
	}		}
	}		}
	}</nowiki></div></div>		}
			</nowiki>
			</div></div>


Line 418:		Line 420:

	DecorationMeshes.lua includes a DecorationMeshes function (mostly commented out) and DecorationInitialize function, which seem like they could convert data in a DecorationMeshInstances table to Decorations and load them into the Names table, but there is no DecorationMeshInstances table ever created(?), plus the DecorationMeshes function needs to be passed a DecorationBarn as "decBarn" and there is nothing like a game:decBarn()/decorationBarn()/etc. It is not yet known if/how we could call a usable DecorationBarn in Lua.		DecorationMeshes.lua includes a DecorationMeshes function (mostly commented out) and DecorationInitialize function, which seem like they could convert data in a DecorationMeshInstances table to Decorations and load them into the Names table, but there is no DecorationMeshInstances table ever created(?), plus the DecorationMeshes function needs to be passed a DecorationBarn as "decBarn" and there is nothing like a game:decBarn()/decorationBarn()/etc. It is not yet known if/how we could call a usable DecorationBarn in Lua.

	===Rails===		===Rails===
	Rails are invisible lines drawn between a set of point locations, which may be "closed", as in the last point connects back to the first point. They seem to mostly be used as a path for an object/etc to move along, but are also used for other kinds of things that are based on a "2D" line in space - like some wind walls are an infinite flat plane stretching up and/or down from a Rail.		Rails are invisible lines drawn between a set of point locations, which may be "closed", as in the last point connects back to the first point. They seem to mostly be used as a path for an object/etc to move along, but are also used for other kinds of things that are based on a "2D" line in space - like some wind walls are an infinite flat plane stretching up and/or down from a Rail.

Alazar88: added/updated methods for changing triggers, markers, decoration meshes; updated some info about rails, hulls; made wording more accurate about "level objects" vs "level resources" - those categories should probably be split into two pages

2021-09-25T21:24:37Z

added/updated methods for changing triggers, markers, decoration meshes; updated some info about rails, hulls; made wording more accurate about "level objects" vs "level resources" - those categories should probably be split into two pages

Show changes

Juest: cat upd

2021-09-25T07:18:50Z

cat upd

← Older revision		Revision as of 07:18, 25 September 2021
Line 1:		Line 1:
			[[Category:Lua Code]]
	[[Category:Native Lua Functions]]		[[Category:Native Lua Functions]]
	[[Category:Level Resources]]		[[Category:Level Resources]]

Alazar88: info on using functions with "hidden" barns (only tested on creatures so far), other minor updates

2021-07-29T00:23:05Z

info on using functions with "hidden" barns (only tested on creatures so far), other minor updates

← Older revision		Revision as of 00:23, 29 July 2021
Line 242:		Line 242:
	Creatures include Fish/Carpets, Guardians/War Machines, Cloth Guardians/Whales/Dragons, Jellyfish, Flow creatures, and Meteors/Comets/Shooting Stars.		Creatures include Fish/Carpets, Guardians/War Machines, Cloth Guardians/Whales/Dragons, Jellyfish, Flow creatures, and Meteors/Comets/Shooting Stars.

	~~It has not yet been tested, but~~ Creatures can ~~probably~~ be added and/or modified in a similar way to Triggers and Clumps, ~~based on DynamicNodeInstances.lua's and~~ the functions in Creatures.lua:		Creatures can be added and/or modified in a similar way to Triggers and Clumps, using the functions from Creatures.lua:
	DynamicNodeInstances = { construct based on the format in DynamicNodeInstances.lua }		DynamicNodeInstances = { construct based on the format in DynamicNodeInstances.lua }
	CreateCreatures( ~~game:~~creatureBarn() ) --only used when adding new creatures(?)		CreateCreatures( creatureBarn* ) --only used when adding new creatures(?)
	ResolveCreatureNames( game:creatureBarn~~() )~~		ResolveCreatureNames( creatureBarn* )
	~~It seems that Creatures/Dynamic Nodes might actually be Triggers~~, ~~based on how TriggerInitialize() is also used in Creatures.lua - so new Creatures might have~~ the ~~same issue as Triggers,~~ and ~~might disappear from the Names table shortly after being created with this method~~.		'''*''' There is no "game:creatureBarn" or other predefined global variable, but you can still access the "hidden" Barn and use these functions - see end of article.
	===Particle Emitters===		===Particle Emitters===
	Particle Emitters emit particles (sparkles, puffs of sand/dust, etc.)		Particle Emitters emit particles (sparkles, puffs of sand/dust, etc.)
Line 254:		Line 254:
	LoadEnvFXParticles( game:envFXBarn(), game:particleBarn() )		LoadEnvFXParticles( game:envFXBarn(), game:particleBarn() )
	Based on tests where logging code was put in LoadEnvFXParticles() and ParticleEmitterInitialize() and nothing was logged, it seems this script doesn't actually run at level start, so Particle Emitters might be added to Names table by another Lua script or by inaccessible C code. But maybe this function could still add/modify Particle Emitters anyway.		Based on tests where logging code was put in LoadEnvFXParticles() and ParticleEmitterInitialize() and nothing was logged, it seems this script doesn't actually run at level start, so Particle Emitters might be added to Names table by another Lua script or by inaccessible C code. But maybe this function could still add/modify Particle Emitters anyway.
	===Sound Emitters===		=== Sound Emitters===
	Sound Emitters emit sounds. They can be stationary or attached to a moving object somehow. It seems that most looping music is played by Sound Emitters that are set to be audible at the same volume anywhere in the level.		Sound Emitters emit sounds. They can be stationary or attached to a moving object somehow. It seems that most looping music is played by Sound Emitters that are set to be audible at the same volume anywhere in the level.

Line 274:		Line 274:
	LoadEnvNodes does ''not'' clear the EnvNodeInstances table automatically upon completion, and the code comments say this causes a crash, so might be a bad idea to do it yourself.		LoadEnvNodes does ''not'' clear the EnvNodeInstances table automatically upon completion, and the code comments say this causes a crash, so might be a bad idea to do it yourself.
	===Markers===		===Markers===
	Markers seem to be locations, or regions of space around locations, which objects can be aimed or moved towards/away from by certain Triggers. Also, Markers can be moved around or attached to moving objects by Triggers.		Markers seem to be locations, or regions of space around locations, which objects can be aimed or moved towards/away from by certain Triggers. Also, Markers can maybe be moved around or attached to moving objects by Triggers.

	It has not yet been tested, but Markers can probably be added and/or modified in a similar way to Triggers and Clumps, based on MarkerInstances.lua's and the functions in Markers.lua:		It has not yet been tested, but Markers can probably be added and/or modified in a similar way to Triggers and Clumps, based on MarkerInstances.lua's and the functions in Markers.lua:
Line 284:		Line 284:
	It has not yet been tested, but Rails can probably be added and/or modified in a similar way to Triggers and Clumps, based on RailInstances.lua's and the functions in RailBarn.lua:		It has not yet been tested, but Rails can probably be added and/or modified in a similar way to Triggers and Clumps, based on RailInstances.lua's and the functions in RailBarn.lua:
	RailInstances = { construct based on the format in RailInstances.lua }		RailInstances = { construct based on the format in RailInstances.lua }
	LoadRails( railBarn )		LoadRails( railBarn* )
	( There ~~doesn't seem to be a~~ game:railBarn~~(), so maybe it's a different name in game:,~~ or ~~maybe it's used like RailBarn~~, ~~RailBarn() or RailBarn(game)~~. )		'''*''' There is no "game:railBarn" or other predefined global variable, but you can probably still access the "hidden" Barn and use this function - see end of article.
	===Camera Key Frames===		===Camera Key Frames===
	Camera Key Frames seem to be the data for basically any location/angle/etc that the camera can get moved to, whenever the camera moves by itself - not just following behind the player, or being moved around by the player.		Camera Key Frames seem to be the data for basically any location/angle/etc that the camera can get moved to, whenever the camera moves by itself - not just following behind the player, or being moved around by the player.
Line 297:		Line 297:
	It has not yet been tested, but Jets can probably be added and/or modified in a similar way to Triggers and Clumps, based on JetInstances.lua's and the functions in Jets.lua:		It has not yet been tested, but Jets can probably be added and/or modified in a similar way to Triggers and Clumps, based on JetInstances.lua's and the functions in Jets.lua:
	JetInstances = { construct based on the format in JetInstances.lua }		JetInstances = { construct based on the format in JetInstances.lua }
	LoadJets( ~~JetBarn~~ )		LoadJets( jetBarn* )
	( There ~~doesn't seem to be a~~ game:jetBarn~~(), so maybe it's a different name in game:,~~ or ~~maybe it's used like JetBarn~~, ~~JetBarn() or JetBarn(game)~~. )		'''*''' There is no "game:jetBarn" or other predefined global variable, but you can probably still access the "hidden" Barn and use this function - see end of article.
	===Signs===		===Signs===
	Signs are scrolling text, used only in the credits. Could maybe be used for other scrolling text as well, although there seem to already be scrolling text Triggers that might be easier for that.		Signs are scrolling text, used only in the credits. Could maybe be used for other scrolling text as well, although there seem to already be scrolling text Triggers that might be easier for that.
Line 305:		Line 305:
	Credits = { construct based on the format in SignData.lua }		Credits = { construct based on the format in SignData.lua }
	SignInstances = { construct based on the format in SignInstances.lua }		SignInstances = { construct based on the format in SignInstances.lua }
	InitializeSignBarn( signBarn, signData, signInstances )		InitializeSignBarn( signBarn, signData, signInstances* )
	( There ~~doesn't seem to be a~~ game:~~signBarn(), so maybe it's a different name in game:,~~ or ~~maybe it's used like SignBarn~~, ~~SignBarn() or SignBarn(game)~~. ~~Also,~~ signData/signInstances don't seem to actually be referenced inside InitializeSignBarn, so they might not be required, but if required then maybe signData is Credits and signInstances is SignInstances. )		<nowiki>*</nowiki> There is no "game:jetBarn" or other predefined global variable, but you can probably still access the "hidden" Barn and use this function - see end of article.
	===TBD / Other===
			<nowiki>**</nowiki> signData and signInstances don't seem to actually be referenced inside InitializeSignBarn, so they might not be required, but if required then maybe signData is the Credits table and signInstances is the SignInstances table. )
			=== TBD / Other===
	These are the remaining types of level resources. They can maybe be manipulated in real time with Lua code, but it's not yet known if/how it can be done.		These are the remaining types of level resources. They can maybe be manipulated in real time with Lua code, but it's not yet known if/how it can be done.
	====Hulls====		====Hulls====
Line 329:		Line 331:

	These are LevelSfx''Somewhere''-SFX.bnk and LevelMus''Somewhere''-MUS.bnk in the Data/Sounds folder; not much is known yet about how to edit these at all, other than renaming files to swap one level for another.		These are LevelSfx''Somewhere''-SFX.bnk and LevelMus''Somewhere''-MUS.bnk in the Data/Sounds folder; not much is known yet about how to edit these at all, other than renaming files to swap one level for another.
	====TerrainData====		====TerrainData ====
	Terrain Data determines the terrain's Height Map and Land Color (the color of sand/snow added to the sides and/or top of some Decoration Meshes, and that collects on the player avatars). It also determines Mask Data which seems to be unused.		Terrain Data determines the terrain's Height Map and Land Color (the color of sand/snow added to the sides and/or top of some Decoration Meshes, and that collects on the player avatars). It also determines Mask Data which seems to be unused.

Line 337:		Line 339:

	You can change what is loaded at the start of a level by editing/replacing the DuneColorShadow.dds texture inside the DuneColorShadow.dds.D3D11x64 file in the Data/Textures/Level_''Somewhere''/Bin folder.		You can change what is loaded at the start of a level by editing/replacing the DuneColorShadow.dds texture inside the DuneColorShadow.dds.D3D11x64 file in the Data/Textures/Level_''Somewhere''/Bin folder.

			==Using Functions With "Hidden" Barns/Managers==
			Many of the functions for creating resources need a related "somethingBarn"/etc - many of them already have this as "game:somethingBarn()", but some don't appear to have any predefined global variable in Lua. For at least some of these, you can still access it and make your own global variable for it, and then use that variable whenever a function calls for a "somethingBarn". (This has only been tested with Creatures)

			You do this by modifying/overwriting the function used with the Barn, to save the variable that it receives when the game calls it normally (whenever a level loads). For example, you could overwrite CreateCreatures with this:
			function CreateCreatures( creatureBarn )
			Hack_CreatureBarn = creatureBarn -- this is the part that's been modded in
			for i, v in ipairs( DynamicNodeInstances ) do
			if v.Type == "Creature" then
			Names[ v.ObjectName ] = creatureBarn:CreateCreature()
			end
			end
			end
			And then after the game has loaded a level at least once, you would be able to successfully call the function yourself anytime with:
			CreateCreatures( Hack_CreatureBarn )

Alazar88: /* Loading Resource Files */ corrected example script so it actually works

2021-06-17T01:56:45Z

Loading Resource Files: corrected example script so it actually works

← Older revision		Revision as of 01:56, 17 June 2021
Line 16:		Line 16:
	if v.class == "Script" then v.source = "Level_"..swapLevel.."/"..v.name..".lua"		if v.class == "Script" then v.source = "Level_"..swapLevel.."/"..v.name..".lua"
	elseif v.class == "Binary" then v.source = "Scripts/Level_"..swapLevel.."/"..v.name..".lua"		elseif v.class == "Binary" then v.source = "Scripts/Level_"..swapLevel.."/"..v.name..".lua"
	elseif v.name == "LvlMus" then v.source = swapLevel.."~~_MUS~~.bnk"		elseif v.name == "LvlMus" then v.source = swapLevel.."-MUS.bnk"
	elseif v.name == "LvlSfx" then v.source = swapLevel.."~~_SFX~~.bnk"		elseif v.name == "LvlSfx" then v.source = swapLevel.."-SFX.bnk"
	elseif v.class == "Texture" then v.source = "Level_"..swapLevel.."/DuneColorShadow.dds"		elseif v.class == "Texture" then v.source = "Level_"..swapLevel.."/DuneColorShadow.dds"
	elseif v.class == "TerrainData" then		elseif v.class == "TerrainData" then

Alazar88: /* Adding/Modifying Individual Resources */

2021-06-12T00:01:54Z

Adding/Modifying Individual Resources

← Older revision		Revision as of 00:01, 12 June 2021
Line 149:		Line 149:
	These methods do not actually edit how the game reads an embedded Level_''Somewhere''/''Something''Instances.lua , so these changes only last until the level is unloaded. When a level unloads, it seems the Names table is completely cleared, including any new objects you created that weren't in the original ''Something''Instances.lua.		These methods do not actually edit how the game reads an embedded Level_''Somewhere''/''Something''Instances.lua , so these changes only last until the level is unloaded. When a level unloads, it seems the Names table is completely cleared, including any new objects you created that weren't in the original ''Something''Instances.lua.

	If you reference an ObjectName that exists in the Names table, but the associated object no longer exists in memory or is corrupted, your game will most likely crash.		If you reference an ObjectName that exists in the Names table, but the associated object no longer exists in memory or is corrupted, your game will most likely crash. It also may crash if you reference an object that isn't in the Names table.

	The ''Something''Instances/etc tables that you construct to load resources into the Names table are usually (but not always) cleared automatically after the functions run, to free up memory.		The ''Something''Instances/etc tables that you construct to load resources into the Names table are usually (but not always) cleared automatically after the functions run, to free up memory.

Alazar88: /* Adding/Modifying Individual Resources */ never mind, tables can be split apart on separate lines just like they are in SomethingInstances.lua's and work fine with injector or just editing original lua

2021-06-12T00:00:50Z

Adding/Modifying Individual Resources: never mind, tables can be split apart on separate lines just like they are in SomethingInstances.lua's and work fine with injector or just editing original lua

Show changes

Alazar88: added research on decoration meshes (still can't load with lua), reformatted code blocks to be actual blocks, a couple other edits

2021-06-11T23:22:35Z

added research on decoration meshes (still can't load with lua), reformatted code blocks to be actual blocks, a couple other edits

Show changes

Alazar88: /* Loading Resource Files */

2021-06-10T03:03:43Z

Loading Resource Files

← Older revision		Revision as of 03:03, 10 June 2021
Line 54:		Line 54:
	If you try to load a set of resources that doesn't exist, some resource types will allow it and just load none of that resource, but other types will make the game crash.		If you try to load a set of resources that doesn't exist, some resource types will allow it and just load none of that resource, but other types will make the game crash.

	Here is the ~~format~~ of resTbl as it gets passed to QueueResourcesForLoad:		Here is a sample of the contents of resTbl as it gets passed to QueueResourcesForLoad:
	{		{
	{		{
Line 207:		Line 207:
	TriggerInstances = { ObjectType = "TriggerInstances", { ObjectName = "TextTrigger", GardenerName = "TextTrigger_G", Type = "DisplayText", Shortcut = "", Vars = {text = "Check this out, I can do a backflip", x = 0, y = 0, duration = 3, fadeTime = 0.5 } }, { ObjectName = "AnimTrigger", GardenerName = "AnimTrigger_G", Type = "PlayDudeAnim", Shortcut = "", Vars = { animName = "HitBodyMAir", clearAnimQueue = true, useLocal = true} } }		TriggerInstances = { ObjectType = "TriggerInstances", { ObjectName = "TextTrigger", GardenerName = "TextTrigger_G", Type = "DisplayText", Shortcut = "", Vars = {text = "Check this out, I can do a backflip", x = 0, y = 0, duration = 3, fadeTime = 0.5 } }, { ObjectName = "AnimTrigger", GardenerName = "AnimTrigger_G", Type = "PlayDudeAnim", Shortcut = "", Vars = { animName = "HitBodyMAir", clearAnimQueue = true, useLocal = true} } }
	CreateTriggers( game:eventBarn() )		CreateTriggers( game:eventBarn() )

	ResolveTriggerNames( game:eventBarn(), game:clumpBarn() )		ResolveTriggerNames( game:eventBarn(), game:clumpBarn() )

	-- these activations aren't necessary to load the triggers, just done on the same frame to demonstrate that they work; see below for why it's done on same frame		-- these activations aren't necessary to load the triggers, just done on the same frame to demonstrate that they work; see below for why it's done on same frame

	ActivateTriggerByName( "TextTrigger" )		ActivateTriggerByName( "TextTrigger" )
	ActivateTriggerByName( "AnimTrigger" )		ActivateTriggerByName( "AnimTrigger" )
Line 238:		Line 236:

	<code>		<code>
	ClumpInstances = { ObjectType = "ClumpInstances", { ObjectName = "NewClumpName", GardenerName = "NewClumpName_G(this name doesn't matter?)", Objects = { "some object's ObjectName", "another object's ObjectName", "and another, etc" } }, { same thing for another new Clump }, {another, etc} }		ClumpInstances = { ObjectType = "ClumpInstances", { ObjectName = "NewClumpName", GardenerName = "NewClumpName_G(this name doesn't matter?)", Objects = { "some object's ObjectName", "another object's ObjectName", "and another, etc" } }, { same thing for another new Clump }, {another, etc} }
	LoadClumps( game:clumpBarn() )		LoadClumps( game:clumpBarn() )
	SetClumpMembers( game:clumpBarn() )		SetClumpMembers( game:clumpBarn() )
Line 246:		Line 244:

	<code>		<code>
	ClumpInstances = { ObjectType = "ClumpInstances", { ObjectName = "NewGameStandUpEvents", GardenerName = "NewGameStandUpEvents_G", Objects = { "70c1306a4a41c624a9ff123f344ef6ad", "d951daedc9f58a681efd39a8875f32c6", "1a737db99c2f3a7733e5c6426211d0e8", "daa0dd930abe88d5d241e02752c636d4", "f26b85b929a3e48edf43a5ec1f076c91", "65eef6f7bcbfcfa07b32c34d07e53132", "796c354ac61bd62ac987778b9fa96c4c", "5abf9a5b00e2e29c36f7871028e9c1e5", "e4fada7df843f162ebb2ee56a0e9f40f" } } }		ClumpInstances = { ObjectType = "ClumpInstances", { ObjectName = "NewGameStandUpEvents", GardenerName = "NewGameStandUpEvents_G", Objects = { "70c1306a4a41c624a9ff123f344ef6ad", "d951daedc9f58a681efd39a8875f32c6", "1a737db99c2f3a7733e5c6426211d0e8", "daa0dd930abe88d5d241e02752c636d4", "f26b85b929a3e48edf43a5ec1f076c91", "65eef6f7bcbfcfa07b32c34d07e53132", "796c354ac61bd62ac987778b9fa96c4c", "5abf9a5b00e2e29c36f7871028e9c1e5", "e4fada7df843f162ebb2ee56a0e9f40f" } } }
	LoadClumps( game:clumpBarn() )		LoadClumps( game:clumpBarn() )
	SetClumpMembers( game:clumpBarn() )		SetClumpMembers( game:clumpBarn() )
Line 255:		Line 253:
	<code>		<code>
	SpawnEvent {EventAfterDelay = {delay = 0.01, effects = Names["NewGameStandUpEvents"]}}		SpawnEvent {EventAfterDelay = {delay = 0.01, effects = Names["NewGameStandUpEvents"]}}

	Demonstration of the Clump it's duplicating:		Demonstration of the Clump it's duplicating: