Modding:Sonic Forces - Revision history

imported>Boilingpot at 20:00, 6 April 2021

2021-04-06T20:00:22Z

← Older revision	Revision as of 20:00, 6 April 2021
(No difference)

imported>Boilingpot at 20:00, 6 April 2021

2021-04-06T20:00:22Z

← Older revision	Revision as of 20:00, 6 April 2021
(No difference)

imported>Boilingpot at 20:00, 6 April 2021

2021-04-06T20:00:22Z

← Older revision		Revision as of 20:00, 6 April 2021
Line 1:		Line 1:
	==Intro==		==Intro==
	Hi! I’m going to keep this simple, but seeing as there’s like a very small number of tutorials for anything relating to modding 3D Sonic games, I’m going to focus on the Sonic Forces corner of HedgeEdit, a level-editing tool made by Radfordhound. Keep in mind that this only covers editing object layouts, since HedgeEdit can’t edit terrain or anything like that. If there’s enough demand, I’ll make more tutorials. ~~Also, some~~ of the object templates in the base download are either missing or broken, so I’ll also be including a download to some updated templates I made in the HedgeEdit DL link (These may be updated from time to time, so check back here every so often. I’ll have a comment detailing the last update date).		Hi! I’m going to keep this simple, but seeing as there’s like a very small number of tutorials for anything relating to modding 3D Sonic games, I’m going to focus on the Sonic Forces corner of HedgeEdit, a level-editing tool made by Radfordhound. Keep in mind that this only covers editing object layouts, since HedgeEdit can’t edit terrain or anything like that. If there’s enough demand, I’ll make more tutorials. Some of the object templates in the base download are either missing or broken, so I’ll also be including a download to some updated templates I made in the HedgeEdit DL link (2 zips, one containing the essentials and the other containing all assets). These may be updated from time to time, so check back here every so often. I’ll have a comment detailing the last update date. Also, be sure to read the readme file in the HedgeEdit DL!

	To start level modding in Sonic Forces, you’ll need a couple of other tools.		To start level modding in Sonic Forces, you’ll need a couple of other tools.

	==Tools:==		==Tools:==
	* [https://drive.google.com/~~file~~/d/~~1k9OMGJ3R764qK21SEbSxrtgxR5engCFx/view~~?usp=sharing HedgeEdit] [V4 UPDATED 4/5/21, Includes resources and templates!]		* [https://drive.google.com/drive/folders/1kC9ri9mauTIRVbHYfowleC1HJtlDSgP_?usp=sharing HedgeEdit] [V5 UPDATED 4/6/21, Includes resources and templates!]
	* [https://github.com/thesupersonic16/HedgeModManager/releases/tag/7.3-2 HedgeModManager]		* [https://github.com/thesupersonic16/HedgeModManager/releases/tag/7.3-2 HedgeModManager]
	* [https://github.com/PTKickass/ForcesModInstaller PackCPK]		* [https://github.com/PTKickass/ForcesModInstaller PackCPK]
Line 33:		Line 33:

	'''HedgeArcPac''': Basically the same thing, but… it has its own instructions so just follow those.		'''HedgeArcPac''': Basically the same thing, but… it has its own instructions so just follow those.

			===HedgeEdit Controls===
			* Right Click + WASD/Movement Arrows: Move Camera (+Ctrl for slow movement, +Shift for fast movement)
			* Right Click + Mouse Movement: Aim Camera
			* Ctrl+S: Save Set Data
			* Ctrl+Shift+S: Save All (Set Data & Materials)
			* Ctrl+A: Select All
			* Ctrl+D: Select None
			* Ctrl+X: Cut selected
			* Del: Delete selected
			* Ctrl+F: View Selected
			* Ctrl+N: New
			* Ctrl+O: Open
			* Alt+F4: Exit (Close HedgeEdit)
			* Ctrl+Click multiple objects: Select multiple objects

	==Bugs & Other Issues==		==Bugs & Other Issues==
Line 122:		Line 137:
	\|-		\|-
	\| PathUID		\| PathUID
	\| ~~Duh~~		\| ID of the badnik's path.
	\|-		\|-
	\| AttackDelay		\| AttackDelay
Line 167:		Line 182:
	\|-		\|-
	\| In3D		\| In3D
	\| ~~Duh~~		\| Whether the badnik is in 3D.
	\|-		\|-
	\| DoesRespawn		\| DoesRespawn

imported>Boilingpot at 01:14, 6 April 2021

2021-04-06T01:14:25Z

← Older revision	Revision as of 01:14, 6 April 2021
(No difference)

imported>Boilingpot at 01:14, 6 April 2021

2021-04-06T01:14:25Z

← Older revision	Revision as of 01:14, 6 April 2021
(No difference)

imported>Boilingpot at 01:14, 6 April 2021

2021-04-06T01:14:25Z

← Older revision		Revision as of 01:14, 6 April 2021
Line 5:		Line 5:

	==Tools:==		==Tools:==
	* [https://drive.google.com/file/d/1k9OMGJ3R764qK21SEbSxrtgxR5engCFx/view?usp=sharing HedgeEdit] [V3 UPDATED 4/3/21, Includes resources and templates!]		* [https://drive.google.com/file/d/1k9OMGJ3R764qK21SEbSxrtgxR5engCFx/view?usp=sharing HedgeEdit] [V4 UPDATED 4/5/21, Includes resources and templates!]
	* [https://github.com/thesupersonic16/HedgeModManager/releases/tag/7.3-2 HedgeModManager]		* [https://github.com/thesupersonic16/HedgeModManager/releases/tag/7.3-2 HedgeModManager]
	* [https://github.com/PTKickass/ForcesModInstaller PackCPK]		* [https://github.com/PTKickass/ForcesModInstaller PackCPK]
Line 179:		Line 179:
	\|}		\|}

	'''~~Eggwalker~~''' (i’m just guessing for most of these, this badnik is very inconsistent in its behavior):		'''Egg Walker''' (i’m just guessing for most of these, this badnik is very inconsistent in its behavior):

	{\| class="wikitable"		{\| class="wikitable"
Line 426:		Line 426:
	\|-		\|-
	\| UpdateMaterial		\| UpdateMaterial
	\| See ~~EggWalker~~.		\| See Egg Walker.
	\|-		\|-
	\| IsStatic		\| IsStatic
Line 603:		Line 603:
	'''BallMoveTrigger''':		'''BallMoveTrigger''':

	A trigger that causes the player to enter a roll based on the speed of the player when crossing through the trigger. The player will decelerate and uncurl in response to the settings in the physics rfls.		A trigger that causes the player to enter a roll, based on the speed of the player when crossing through the trigger. The player will decelerate and uncurl in response to the settings in the physics rfls.

	'''BallLaunchTrigger''':		'''BallLaunchTrigger''':
Line 638:		Line 638:
	'''TerrainBlock/TerrainBlocks''':		'''TerrainBlock/TerrainBlocks''':

	Placeholder terrain blocks that were used ~~as… placeholders…~~ for terrain during testing. Unfortunately, these only draw in the game’s built-in level editor (presumably). They’re still useful for simple shapes, though.		Placeholder terrain blocks that were used as placeholders for terrain during testing. Unfortunately, these only draw in the game’s built-in level editor (presumably). They’re still useful for simple shapes, though.

	'''DebugNote''':		'''DebugNote''':
Line 663:		Line 663:

	The Thornballs seen in the extra stages and Casino Forest. I only understand some of these values, so I’m only going to cover those for now.		The Thornballs seen in the extra stages and Casino Forest. I only understand some of these values, so I’m only going to cover those for now.

	{\| class="wikitable"		{\| class="wikitable"
	\|-		\|-
Line 841:		Line 842:
	'''Important/Common Parameters''':		'''Important/Common Parameters''':

	* Speed: The speed of the object or ~~it’s~~ function.		* Speed: The speed of the object or its function.
	* Camera: The ID of the cameravolume the object uses.		* Camera: The ID of the cameravolume the object uses.
	* PathID: The ID of the path the object uses.		* PathID: The ID of the path the object uses.
	* IsEventDriven: Whether or not the object is triggered by default or must be triggered by something else.		* IsEventDriven: Whether or not the object is triggered by default or must be triggered by something else.
	* phase: It’s basically a time offset. For example, setting the phase to 1 will make the object behave as if it had been activated one second earlier.		* phase: It’s basically a time offset. For example, setting the phase value to 1 will make the object behave as though it had been activated one second earlier.

	'''Object Parenting''':		'''Object Parenting''':
Line 888:		Line 889:
	\|-		\|-
	\| BasePoint		\| BasePoint
	\| Determines the origin point of the volume, 0 sets it to be in the center while 1 sets it to be at the start of the object's Z plane.		\| Determines the origin point of the volume. 0 sets it to be in the center while 1 sets it to be at the start of the object's Z plane.
	\|-		\|-
	\| Width, Height and Depth		\| Width, Height and Depth
	\| Controls the size of the volume in distance units. There's no way to preview the volume size in HedgeEdit so you ~~just kinda~~ have to guess.		\| Controls the size of the volume in distance units. There's no way to preview the volume size in HedgeEdit so you have to guess.
	\|}		\|}

	'''CameraSubVolumes''':		'''CameraSubVolumes''':

	If you want to reuse the same camera repeatedly in a stage you can use a CameraSubVolume. Instead of putting in the ID of a camera object you put in the ID and GroupID of another CameraVolume, and the CameraSubVolume will take on all the parameters the CameraVolume uses(aside from ~~it's~~ BasePoint and size).		If you want to reuse the same camera repeatedly in a stage you can use a CameraSubVolume. Instead of putting in the ID of a camera object you put in the ID and GroupID of another CameraVolume, and the CameraSubVolume will take on all the parameters the CameraVolume uses (aside from its BasePoint and size).

	'''Camera Objects''':		'''Camera Objects''':

imported>Boilingpot at 00:55, 6 April 2021

2021-04-06T00:55:04Z

← Older revision	Revision as of 00:55, 6 April 2021
(No difference)

imported>Boilingpot at 00:55, 6 April 2021

2021-04-06T00:55:04Z

← Older revision	Revision as of 00:55, 6 April 2021
(No difference)

imported>Boilingpot at 00:55, 6 April 2021

2021-04-06T00:55:04Z

← Older revision		Revision as of 00:55, 6 April 2021
Line 44:		Line 44:

	'''Object selection bug''' (fixed?):		'''Object selection bug''' (fixed?):
	I have no idea what causes this, but in a modified Lost Valley & Imperial Tower, you can’t select objects that don’t have a model set (~~basically,~~ anything that uses the ~~Default~~ checkerboard cube. You’ll have to go into the scene view to fish the object out.		I have no idea what causes this, but in a modified Lost Valley & Imperial Tower, you can’t select objects that don’t have a model set (anything that uses the default checkerboard cube). You’ll have to go into the scene view to fish the object out.

	'''Not having a gedit file in the mod folder...'''		'''Not having a gedit file in the mod folder...'''
Line 429:		Line 429:
	\|-		\|-
	\| IsStatic		\| IsStatic
	\| Whether or not this badnik has its AI disabled~~, basically~~.		\| Whether or not this badnik has its AI disabled.
	\|-		\|-
	\| BehaviorType		\| BehaviorType
Line 543:		Line 543:
	\|-		\|-
	\| PlaceType		\| PlaceType
	\| Has two options, Line and Circle. Line places springs in a row and Circle places them in, well, a circle. I'd ~~probably~~ recommend just using Line though ~~cause~~ it's basically impossible to tell what you're doing with Circle until HedgeEdit becomes capable of ~~visualising~~ the spring placement.		\| Has two options, Line and Circle. Line places springs in a row and Circle places them in, well, a circle. I'd recommend just using Line though because it's basically impossible to tell what you're doing with Circle until HedgeEdit becomes capable of visualizing the spring placement.
	\|-		\|-
	\| CircleRadius		\| CircleRadius
Line 595:		Line 595:
	'''MoveRingBuilder''':		'''MoveRingBuilder''':

	These are also really fucky and A LOT OF THIS MAY BE WRONG so I’m ~~basically~~ going to gloss over them, but here’s what I know: These are the objects that get used in Aqua Road that create the moving ring trails you can collect. BuildType Loop means that the rings will keep looping after they reach their end point. BuildNum is the number of chains of rings (as in respawning? I’m not certain on that). BuildInterval is the amount of time between spawns. ItemId is the id of the Red Ring this object uses if the ring type is set to red ring. PathID is self explanatory (or at least I hope it as this point), Movespeed is the speed of the rings as they travel along their path, the meandering parameters are for the wavy movement patterns, limittime is the maximum time the rings can spawn for, overtime is the time they end at(?), columnnum is the amount of rings in a column, rownum is the amount of rings in a row, column offset is the offset, and the rest is self explanatory.		These are also really fucky and A LOT OF THIS MAY BE WRONG so I’m going to gloss over them, but here’s what I know: These are the objects that get used in Aqua Road that create the moving ring trails you can collect. BuildType Loop means that the rings will keep looping after they reach their end point. BuildNum is the number of chains of rings (as in respawning? I’m not certain on that). BuildInterval is the amount of time between spawns. ItemId is the id of the Red Ring this object uses if the ring type is set to red ring. PathID is self explanatory (or at least I hope it as this point), Movespeed is the speed of the rings as they travel along their path, the meandering parameters are for the wavy movement patterns, limittime is the maximum time the rings can spawn for, overtime is the time they end at(?), columnnum is the amount of rings in a column, rownum is the amount of rings in a row, column offset is the offset, and the rest is self explanatory.

	'''ObjectLayerTrigger/ObjectLayerVolume''':		'''ObjectLayerTrigger/ObjectLayerVolume''':
Line 607:		Line 607:
	'''BallLaunchTrigger''':		'''BallLaunchTrigger''':

	~~Basically~~ the BallMoveTrigger, but it uses set speed parameters and follows a path.		Similar to the BallMoveTrigger, but it uses set speed parameters and follows a path.

	'''PipeMoveTrigger''':		'''PipeMoveTrigger''':
Line 634:		Line 634:
	'''ShowTimeEffect''':		'''ShowTimeEffect''':

	An object that ~~basically~~ functions ~~like~~ the Infinite object in Capital City, but without Infinite. Keep in mind that a second ~~rgb~~ table must be added to the stage’s terrain common in order for this to work.		An object that functions similarly to the Infinite object in Capital City, but without Infinite. Keep in mind that a second RGB table must be added to the stage’s terrain common in order for this to work.

	'''TerrainBlock/TerrainBlocks''':		'''TerrainBlock/TerrainBlocks''':
Line 642:		Line 642:
	'''DebugNote''':		'''DebugNote''':

	~~Basically just an~~ object that lets you leave notes for other people looking at the gedit you’re working on. Useful when working with a team (then again, you could just tell them directly).		An object that lets you leave notes for other people looking at the gedit you’re working on. Useful when working with a team (then again, you could just tell them directly).

	'''Gravity Objects''':		'''Gravity Objects''':

	I’m going to gloss over this one too due to them being kind of odd, but ~~basically~~ these objects ~~just~~ control gravity based on the direction and position of the object.		I’m going to gloss over this one too due to them being kind of odd, but these objects control gravity based on the direction and position of the object.

	'''ObjReleaseBox''':		'''ObjReleaseBox''':
Line 856:		Line 856:
	'''CameraVolumes''':		'''CameraVolumes''':

	In order to activate camera objects they have to be assigned to CameraVolumes, which are ~~basically~~ invisible boxes that activate the cameras when you go inside them. To assign a camera object to a CameraVolume you simply need to put the ID and GroupID of the object into the volume's Camera parameter.		In order to activate camera objects they have to be assigned to CameraVolumes, which are invisible boxes that activate the cameras when you go inside them. To assign a camera object to a CameraVolume you simply need to put the ID and GroupID of the object into the volume's Camera parameter.

	{\| class="wikitable"		{\| class="wikitable"
Line 927:		Line 927:
	\|-		\|-
	\| Azimuth		\| Azimuth
	\| Generally only seen on CameraRail objects, it ~~basically~~ controls how the camera is rotated left/right around the target.		\| Generally only seen on CameraRail objects, it controls how the camera is rotated left/right around the target.
	\|-		\|-
	\| Elevation		\| Elevation
Line 985:		Line 985:
	\|-		\|-
	\| AngleSensitivity		\| AngleSensitivity
	\| ~~Kind of~~ hard to explain, but ~~basically~~ controls how sensitive the camera is to turns and slopes in the path. If you set it to a low value, the camera is slow to rotate with the path and moves more smoothly~~, while if~~ it's set to a higher value it will follow the path more exactly and become more jerky unless the path is very smooth.		\| Somewhat hard to explain, but it controls how sensitive the camera is to turns and slopes in the path. If you set it to a low value, the camera is slow to rotate with the path and moves more smoothly. If it's set to a higher value it will follow the path more exactly, and become more jerky unless the path is very smooth.
	\|-		\|-
	\| AngleSensitivityBoost		\| AngleSensitivityBoost
Line 1,034:		Line 1,034:
	'''SetPath'''		'''SetPath'''

	You put a setpath down, and then you put an ID in. This is going to be the path’s ID (obviously). You have 3 pathtypes. The first is Object Path (use this for most cases), 2D path (you can ~~basically~~ just use Object Path it doesn’t really matter), and grind path ~~which-- you~~ guessed ~~it-- is~~ used for grind rails. Theres also a true or false toggle for the path being used for loops, but it’s useless because loops have their own path objects so just pretend that doesn’t exist. StartLineType decides whether or not the path smoothing between nodes will be straight or curved. DivideLength is the distance between the invisible points between each node. Higher values make the path more rigid, whereas lower values make the path smoother. Do NOT use ~~one~~, it will crash. 10 should be your minimum.		You put a setpath down, and then you put an ID in. This is going to be the path’s ID (obviously). You have 3 pathtypes. The first is Object Path (use this for most cases), 2D path (you can just use Object Path, it doesn’t really matter), and grind path which—you guessed it—is used for grind rails. Theres also a true or false toggle for the path being used for loops, but it’s useless because loops have their own path objects so just pretend that doesn’t exist. StartLineType decides whether or not the path smoothing between nodes will be straight or curved. DivideLength is the distance between the invisible points between each node. Higher values make the path more rigid, whereas lower values make the path smoother. Do NOT use a value of 1, it will crash. 10 should be your minimum.

	'''SetPathNode'''		'''SetPathNode'''
Line 1,046:		Line 1,046:
	'''CorrectPathVolume2'''		'''CorrectPathVolume2'''

	This object ~~basically~~ allows you to force the player along a given path. Useful for tight turns (such as that one part in Metropolitan Highway, except that there is one there, it’s just really weak lol).		This object allows you to force the player along a given path. Useful for tight turns (such as that one part in Metropolitan Highway, except that there is one there, it’s just really weak lol).

	==Triggers==		==Triggers==
Line 1,057:		Line 1,057:
	'''EventSetter'''		'''EventSetter'''

	~~Basically~~ a switchvolume, but it is triggered by destroying badniks. There’s not much to explain here, just read the object parameter descriptions.		Similar to a switchvolume, but it is triggered by destroying badniks. There’s not much to explain here, just read the object parameter descriptions.

	==Tips==		==Tips==

imported>Boilingpot: /* Stage Objects & Enemies */

2021-04-06T00:41:32Z

Stage Objects & Enemies

← Older revision	Revision as of 00:41, 6 April 2021
(No difference)