Creating a new Mod - Revision history

Silverfish: /* Steam Workshop */ Reset to default size on video embed

2018-04-07T07:19:49Z

Steam Workshop: Reset to default size on video embed

← Older revision		Revision as of 00:19, 7 April 2018
Line 268:		Line 268:
	{{#ev:youtube		{{#ev:youtube
	\|wOL0LJBRcas		\|wOL0LJBRcas
	\|~~420~~		\|
	\|right		\|right
	\|How to upload a mod to the Steam Workshop		\|How to upload a mod to the Steam Workshop

Silverfish: /* Steam Workshop */ Added video tutorial

2018-04-07T05:09:56Z

Steam Workshop: Added video tutorial

← Older revision		Revision as of 22:09, 6 April 2018
Line 266:		Line 266:

	== Steam Workshop ==		== Steam Workshop ==
			{{#ev:youtube
			\|wOL0LJBRcas
			\|420
			\|right
			\|How to upload a mod to the Steam Workshop
			\|frame
			\|start=702&end=873
			}}

	Overgrowth comes with built in tools for uploading your mods to the Steam Workshop.		Overgrowth comes with built in tools for uploading your mods to the Steam Workshop.

Mng: Added to category Tutorials

2018-03-09T22:58:20Z

Added to category Tutorials

← Older revision		Revision as of 15:58, 9 March 2018
Line 287:		Line 287:
	This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.		This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.

			[[Category: Tutorials]]
			[[Category: Modding]]
	[[Category: Overgrowth]]		[[Category: Overgrowth]]
	~~[[Category: Modding]]~~

Mng: Added to category: Modding, Overgrowth

2018-03-08T17:47:22Z

Added to category: Modding, Overgrowth

← Older revision		Revision as of 10:47, 8 March 2018
Line 286:		Line 286:

	This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.		This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.

			[[Category: Overgrowth]]
			[[Category: Modding]]

Silverfish: /* Category */ fixed todo

2018-01-17T07:58:08Z

Category: fixed todo

← Older revision		Revision as of 00:58, 17 January 2018
Line 59:		Line 59:
	=== Category ===		=== Category ===

	~~'''TODO: Verify that this is correct.'''~~		Required for a valid mod, but does not have any effect.

	Required for a valid mod, but does not ~~seem to~~ have any effect.

	Example:		Example:

Silverfish: /* SupportedVersion */ Added how to check game version

2018-01-17T07:52:55Z

SupportedVersion: Added how to check game version

← Older revision		Revision as of 00:52, 17 January 2018
Line 111:		Line 111:
	=== SupportedVersion ===		=== SupportedVersion ===

	Which ~~update~~ of the game this mod can be used in. Can be something like <code>b4</code>, or <code></code> to indicate that it can be used with any version. Using <code></code> is useful for mods that don't rely on the game code as much, such as assets, levels and so on.		Which version of the game this mod can be used in. Can be something like <code>1.2.0</code>, or <code></code> to indicate that it can be used with any version. Using <code></code> is useful for mods that don't rely on the game code as much, such as assets, levels and so on.

	~~'''TODO: How can you~~ find out which is the ~~current~~ version~~?''~~'		To find out which version of the game you're running, in the top menu bar, press <code>Help → About...</code>. Here you will see 4 lines of information, where the third line shows your version number. It starts with three numbers separated by periods, and this is the version you're running. It can for example be <code>1.2.0</code>.

	Example:		Example:
	<code><SupportedVersion>b4</SupportedVersion></code>		<code><SupportedVersion>1.2.0</SupportedVersion></code>

	=== LevelHookFile ===		=== LevelHookFile ===

Silverfish: /* Steam Workshop */ Added "uploading a mod" heading and added small introduction

2018-01-17T07:43:07Z

Steam Workshop: Added "uploading a mod" heading and added small introduction

← Older revision		Revision as of 00:43, 17 January 2018
Line 268:		Line 268:

	== Steam Workshop ==		== Steam Workshop ==

			Overgrowth comes with built in tools for uploading your mods to the Steam Workshop.

			=== Uploading a Mod ===

	[[File:Steamworks_upload.jpg\|200px\|thumb\|right\|The Steamworks New Upload menu]]		[[File:Steamworks_upload.jpg\|200px\|thumb\|right\|The Steamworks New Upload menu]]
Line 279:		Line 283:
	If the mod requires some other mod to work, make sure to specify that using the "Add/Remove Required Items" in the "Owner Controls".		If the mod requires some other mod to work, make sure to specify that using the "Add/Remove Required Items" in the "Owner Controls".

	=== Updating a Mod ~~on Steam Workshop~~ ===		=== Updating a Mod ===

	To update a mod that you've already uploaded to Steam Workshop, start by opening up the [[#Advanced_mod_menu\|advanced mod menu]]. Select the workshop mod you want to update under the "My Steam Workshop Mods" heading in the left column, and press "Upload Update..." under "Owner Controls" in the right column.		To update a mod that you've already uploaded to Steam Workshop, start by opening up the [[#Advanced_mod_menu\|advanced mod menu]]. Select the workshop mod you want to update under the "My Steam Workshop Mods" heading in the left column, and press "Upload Update..." under "Owner Controls" in the right column.

	This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.		This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.

Silverfish: /* OverloadFile */ removed OverloadFile since it's not in use

2018-01-17T07:40:54Z

OverloadFile: removed OverloadFile since it's not in use

← Older revision		Revision as of 00:40, 17 January 2018
Line 228:		Line 228:
	<Version>1.0.0</Version>		<Version>1.0.0</Version>
	</ModDependency>		</ModDependency>

	~~=== OverloadFile ===~~

	~~'''TODO: Write description'''~~

	~~Example:~~
	~~<code><OverloadFile>'''TODO: Write example</OverloadFile></code>'''~~

	=== Item ===		=== Item ===

Silverfish: /* Updating a Mod on Steam Workshop */ Wrote instructions for updating existing mod on Workshop

2018-01-17T07:34:02Z

Updating a Mod on Steam Workshop: Wrote instructions for updating existing mod on Workshop

← Older revision		Revision as of 00:34, 17 January 2018
Line 288:		Line 288:
	=== Updating a Mod on Steam Workshop ===		=== Updating a Mod on Steam Workshop ===

	'~~''TODO: What is the process for updating an~~ already uploaded mod on Steam Workshop~~?'''~~		To update a mod that you've already uploaded to Steam Workshop, start by opening up the [[#Advanced_mod_menu\|advanced mod menu]]. Select the workshop mod you want to update under the "My Steam Workshop Mods" heading in the left column, and press "Upload Update..." under "Owner Controls" in the right column.

			This brings up a window where you can choose which local source mod to use as the updated version, you can control its visibility on the workshop and write an update message. After agreeing to the text at the bottom of the window you can upload the update.

Xagor-the-ninja: /* Folder structure */ Added note that "Mods" folder in both program files and "My Documents" will both work for mod location.

2018-01-16T09:50:47Z

Folder structure: Added note that "Mods" folder in both program files and "My Documents" will both work for mod location.

← Older revision		Revision as of 02:50, 16 January 2018
Line 17:		Line 17:
	└── Levels/		└── Levels/

	The folder called my_mod in the tree structure above is what is compressed into a zip file and distributed when a mod is released. You can also release the mod on Steam Workshop, which is a different process that you can read about [[#Steam_Workshop\|a bit further down]].		Note that your mod can be set up and kept in either YourPC/Documents/Wolfire/Overgrowth/Data/Mods, or in the actual program files, in YourPC/(C:)/Program Files(x86)/Steam/steamapps/common/Overgrowth/Data/Mods - both of these "Mods" folder locations will work. The folder called my_mod in the tree structure above is what is compressed into a zip file and distributed when a mod is released. You can also release the mod on Steam Workshop, which is a different process that you can read about [[#Steam_Workshop\|a bit further down]].

	== The mod.xml file ==		== The mod.xml file ==