Modding:Sonic Forces - Revision history

Boilingpot at 20:00, 6 April 2021

2021-04-06T20:00:22Z

Boilingpot at 01:14, 6 April 2021

2021-04-06T01:14:25Z

Boilingpot at 00:55, 6 April 2021

2021-04-06T00:55:04Z

Boilingpot: /* Stage Objects & Enemies */

2021-04-06T00:41:32Z

‎Stage Objects & Enemies

Boilingpot at 00:39, 6 April 2021

2021-04-06T00:39:05Z

Boilingpot: /* Stage Objects & Enemies */

2021-04-06T00:30:13Z

‎Stage Objects & Enemies

Boilingpot at 22:09, 5 April 2021

2021-04-05T22:09:47Z

Boilingpot at 21:27, 5 April 2021

2021-04-05T21:27:09Z

Show changes

Boilingpot at 21:19, 5 April 2021

2021-04-05T21:19:16Z

Boilingpot: /* Bugs & Other Issues */

2021-04-05T21:00:12Z

‎Bugs & Other Issues

@@ Line 1: / Line 1: @@
 ==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.
 ==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/PTKickass/ForcesModInstaller PackCPK]
@@ Line 33: / Line 33: @@
 '''HedgeArcPac''': Basically the same thing, but… it has its own instructions so just follow those.
 ==Bugs & Other Issues==
@@ Line 122: / Line 137: @@
 |-
 | PathUID
-| Duh
+| ID of the badnik's path.
 |-
 | AttackDelay
@@ Line 167: / Line 182: @@
 |-
 | In3D
-| Duh
+| Whether the badnik is in 3D.
 |-
 | DoesRespawn

@@ Line 5: / Line 5: @@
 ==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/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"
@@ Line 426: / Line 426: @@
 |-
 | UpdateMaterial
-| See EggWalker.
+| See Egg Walker.
 |-
 | IsStatic
@@ Line 603: / Line 603: @@
 '''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''':
@@ Line 638: / Line 638: @@
 '''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''':
@@ 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.
 {| class="wikitable"
 |-
@@ Line 841: / Line 842: @@
 '''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.
 * 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.
-* 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''':
@@ Line 888: / Line 889: @@
 |-
 | 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
-| 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''':
-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''':

@@ Line 44: / Line 44: @@
 '''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...'''
@@ Line 429: / Line 429: @@
 |-
 | IsStatic
-| Whether or not this badnik has its AI disabled, basically.
+| Whether or not this badnik has its AI disabled.
 |-
 | BehaviorType
@@ Line 543: / Line 543: @@
 |-
 | 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
@@ Line 595: / Line 595: @@
 '''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''':
@@ Line 607: / Line 607: @@
 '''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''':
@@ Line 634: / Line 634: @@
 '''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''':
@@ Line 642: / Line 642: @@
 '''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''':
-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''':
@@ Line 856: / Line 856: @@
 '''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"
@@ Line 927: / Line 927: @@
 |-
 | 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
@@ Line 985: / Line 985: @@
 |-
 | 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
@@ Line 1,034: / Line 1,034: @@
 '''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'''
@@ Line 1,046: / Line 1,046: @@
 '''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==
@@ Line 1,057: / Line 1,057: @@
 '''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==

@@ Line 101: / Line 101: @@
 After you’ve opened and loaded the stage you’re looking to edit in HedgeEdit, hit ‘edit’ at the top and click ‘scene view’. You’ll see a box open up on the right with two groups: ‘Set Layers’ and ‘Terrain Instances’. Terrain instances can be ignored, as it serves no real function currently. What you’ll want to focus on here is the ‘Set Layers’ tab. In each stage, different groups of objects are loaded into their own Set Layers. Whenever you open a stage in HedgeEdit, you’ll need to select one of these layers by clicking on it in order to place objects. The currently selected layer will be shown in parenthesis at the top of the window next to the program’s name. To avoid disorganization, you’ll want to pay attention to whatever set layers you use. If you want to rename or delete a set layer, you can right click a layer and pick an option. Please note that deleting or renaming a set layer does not actually remove or rename it inside your gedit file, so if you need to do that, you’ll want to close HedgeEdit after making that change, open the gedit file in your mod using SFPac, and remove anything you don’t need from there, then repack it by running the folder through SFPac again.
-==Stage Objects & Enemies==
+==Enemies & Stage Objects==
 Now that you understand how to open stages and set layers, let’s get to the basics: Object Placement.
@@ Line 111: / Line 111: @@
 Onto enemies. I’m only going to be focusing on the ones that aren’t self-explanatory.
 '''Valkeen''' (must be spawned using a trigger):
@@ Line 519: / Line 521: @@
 | The pitch rotation of this badnik’s head.
 |}
 '''Collectibles''':

@@ Line 1: / Line 1: @@
 ==Intro==
-Hi! I’m gonna 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 gonna 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. 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).
 To start level modding in Sonic Forces, you’ll need a couple of other tools.
@@ Line 19: / Line 19: @@
 ===Creating a mod folder===
-After the aforementioned CPKs are unpacked, you’re gonna want to open HedgeModManager, and hit ‘Add Mod’ at the bottom left. This will open a dialogue box with several options. You’ll want to hit the last choice (making one), and then hit ‘ok’. This will open *another* dialogue box. For now, you can ignore everything above the ‘description’ tab. For everything in the description tab, you can fill out basically whatever you want, it’s pretty self-explanatory. Once you’re done, you can hit ‘OK’. This will open up a new folder for your mod. Click into the ‘disk’ folder in the new window, and create a folder named ‘wars_patch’ with an underscore between wars and patch.
+After the aforementioned CPKs are unpacked, you’re going to want to open HedgeModManager, and hit ‘Add Mod’ at the bottom left. This will open a dialogue box with several options. You’ll want to hit the last choice (making one), and then hit ‘OK’. This will open ''another'' dialogue box. For now, you can ignore everything above the ‘description’ tab. For everything in the description tab, you can fill out basically whatever you want, it’s pretty self-explanatory. Once you’re done, you can hit ‘OK’. This will open up a new folder for your mod. Click into the ‘disk’ folder in the new window, and create a folder named ‘wars_patch’.
 ===Putting your stage files in your mod folder===
@@ Line 74: / Line 74: @@
 '''Green Hill Mat Issues''':
-Often times, placing grass platforms in Green Hill stages will make the grass appear red and the platform itself white. You *should* be able to fix this by replacing the materials with the originals but I’m not 100% sure.
+Often times, placing grass platforms in Green Hill stages will make the grass appear red and the platform itself white. You ''should'' be able to fix this by replacing the materials with the originals but I’m not 100% sure.
 '''Virton object incompatibilities''':
@@ Line 86: / Line 86: @@
 '''Particle Limit''':
-Sonic Forces has a very small particle limit, so if you hit it, stuff like homing attack and boost particles are gonna start disappearing. This also disables any SFX tied to these particles.
+Sonic Forces has a very small particle limit, so if you hit it, stuff like homing attack and boost particles are going to start disappearing. This also disables any SFX tied to these particles.
 '''Stage-specific issues''':
@@ Line 854: / Line 854: @@
 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.
-[Insert Table]
+{| class="wikitable"
 '''CameraSubVolumes''':

@@ Line 687: / Line 687: @@
 '''ObjLaserTurret''':
-[Insert Table]
+The Laser Turrets in Metropolis.
 '''ObjWallJumpTest''':
@@ Line 705: / Line 765: @@
 The floating platforms used throughout the games.
-[Insert Table]
+{| class="wikitable"
 '''(Custom) scaletest''':

@@ Line 102: / Line 102: @@
 ==Stage Objects & Enemies==
-Now that you understand how to open stages and set layers, let’s get to the basics: Object Placement. I’m not gonna be super thorough with this, but I’ll be going over anything that might be confusing in the second half of this video.
+Now that you understand how to open stages and set layers, let’s get to the basics: Object Placement.
-Let me start by letting you know that, if there’s a specific object from another stage you want to use, you’re gonna want to copy it’s assets (which may include files from both the object pac AND terrain common) into your mod’s object pac or terrain common. Though, as long as it’s the same in-game location (such as Green Hill) it usually should work without having to add files.
+Let me start by letting you know that, if there’s a specific object from another stage you want to use, you’re going to want to copy its assets (which may include files from both the object pac AND terrain common) into your mod’s object pac or terrain common. Though, as long as it’s the same in-game location (such as Green Hill) it usually should work without having to add files.
 Quick note: You can move the camera in HedgeEdit by holding right click and moving the mouse. You can also press the arrow keys or WASD keys to move, and hold shift to move faster.
@@ Line 738: / Line 738: @@
 '''Camera Objects''':
-[Insert Table]
+{| class="wikitable"
 '''CameraFollow''':
@@ Line 751: / Line 782: @@
 Looks at the player from the point the object is placed.
-[Insert Table]
+{| class="wikitable"
 '''CameraPoint''':
@@ Line 761: / Line 808: @@
 Generally something you want to use in 3D running/boosting sections, it moves along a spline path while following behind the player.
-[Insert Table]
+{| class="wikitable"
 '''CameraRailSideView''':
@@ Line 767: / Line 833: @@
 Best used for 2D sections (unless you want to do something like that psuedo side-scrolling bit in Spaceport), it moves along a spline path while following the player from more of a side view, hence the name. Also this camera is a bit confusing to work with so there's a couple values I haven't figured out yet.
-[Insert Table]
+{| class="wikitable"
 '''DefaultCameraSetting''':

@@ Line 15: / Line 15: @@
 ===Using PackCPK===
-PackCPK is what you’ll need to unpack the CPK files in Sonic Forces (which contain all of the game’s assets and such). After downloading PackCPK, right click on Sonic Forces in your Steam Library, and hit properties. This will open a menu. On the left, navigate to Local Files and hit the browse button at the top right. This will open the location of Sonic Forces’ files on your PC. Click into the ‘image’ folder, then ‘x64’, then ‘disk’. Inside the ‘disk’ folder, there are several CPK files. Wars_0 contains all of the essential game assets (such as enemies, characters, and UI) as well as all the stage folders for Lost Valley through Aqua Road. Wars_1 contains everything from sunset heights to the final boss. Wars_dlc01 contains all of the episode shadow files, dlc02 contains Super Sonic’s files, and the rest are all of the other avatar costume dlcs and whatnot. There’s also wars_patch, which contains all of the game’s gedit files and other miscellaneous files. For what we’ll be doing, you’ll want to unpack wars_0, wars_1, and wars_patch. Make sure you do these separately, and they may take a while. Keep in mind that often times, PackCPK sometimes misses files, so to be safe, you may want to run the CPKs through a second time after the first attempt.
+PackCPK is what you’ll need to unpack the CPK files in Sonic Forces (which contain all of the game’s assets and such). After downloading PackCPK, right click on Sonic Forces in your Steam Library, and hit properties. This will open a menu. On the left, navigate to Local Files and hit the browse button at the top right. This will open the location of Sonic Forces’ files on your PC. Click into the ‘image’ folder, then ‘x64’, then ‘disk’. Inside the ‘disk’ folder, there are several CPK files. Wars_0 contains all of the essential game assets (such as enemies, characters, and UI) as well as all the stage folders for Lost Valley through Aqua Road. Wars_1 contains everything from Sunset Heights to the final boss. Wars_dlc01 contains all of the Episode Shadow files, dlc02 contains Super Sonic’s files, and the rest are all of the other avatar costume DLCs and whatnot. There’s also wars_patch, which contains all of the game’s gedit files and other miscellaneous files. For what we’ll be doing, you’ll want to unpack wars_0, wars_1, and wars_patch. Make sure you do these separately, and they may take a while. Keep in mind that often times, PackCPK sometimes misses files, so to be safe, you may want to run the CPKs through a second time after the first attempt.
 ===Creating a mod folder===
@@ Line 23: / Line 23: @@
 ===Putting your stage files in your mod folder===
-Next, navigate back to your unpacked CPKs. We’ll be starting with Lost Valley. Go into your wars_0 folder, and find the folder labeled ‘w5a01’. This actually brings me to something important: You may be confused by the naming scheme of stages, so here’s something to help you out: ‘w’ refers to the ‘world’ number, where w1 is Death Egg, w2 is Chemical Plant, w3 is City, w4 is Mystic Jungle, w5 is Green Hill, w6 is Metropolis, and w7 is Eggman Empire Fortress. The letter and the 2 numbers after the world number represent the type of act and the character. ‘A’ means it is a stage from the main story. ‘D’ means it is a dlc stage, ‘B’ means it’s a boss stage, and ‘X’ or ‘S’ means it’s an extra or secret stage. For stages from the main story, the number 01 means it is a Sonic stage, 02 is an avatar stage, 03 is a tag team stage, and 04 is a Classic stage. For boss stages or secret/extra stages, the number refers to the act or stage number. (For example, w7b02 is the final boss, since it’s the second boss in that world).
+Next, navigate back to your unpacked CPKs. We’ll be starting with Lost Valley. Go into your wars_0 folder, and find the folder labeled ‘w5a01’. This actually brings me to something important: You may be confused by the naming scheme of stages, so here’s something to help you out: ‘w’ refers to the ‘world’ number, where w1 is Death Egg, w2 is Chemical Plant, w3 is City, w4 is Mystic Jungle, w5 is Green Hill, w6 is Metropolis, and w7 is Eggman Empire Fortress. The letter and the 2 numbers after the world number represent the type of act and the character. ‘A’ means it is a stage from the main story. ‘D’ means it is a DLC stage, ‘B’ means it’s a boss stage, and ‘X’ or ‘S’ means it’s an extra or secret stage. For stages from the main story, the number 01 means it is a Sonic stage, 02 is an avatar stage, 03 is a tag team stage, and 04 is a Classic Sonic stage. For boss stages or secret/extra stages, the number refers to the act or stage number. (For example, w7b02 is the final boss, since it’s the second boss in that world).
-Anyways, back to what i was saying before: click into the w5a01 folder. You’ll see a bunch of pacs. You won’t need to do much with these for now, but just know that these files are opened using ‘SFPac’. Back out of the w5a01 folder, and copy it into the ‘wars_patch’ folder in your mod. While still in your mod’s wars_patch folder, you’ll want to create a folder named ‘gedit’. Next, navigate back to the folder containing the game’s CPKs, and go into *it’s* wars_patch folder (NOT the one in your mod that you just copied files into!). Once inside, you’ll see a ‘gedit’ folder. Go inside it, and copy ‘w5a01_gedit.pac’ into your mod’s gedit folder. Now, you’re ready to start using HedgeEdit. (If you haven’t already downloaded it, do that now). Next, I’m going to teach you how to open stages in HedgeEdit. Simply go into your mod’s wars_patch folder, and copy that directory. Open hedgeedit, click ‘open’ and paste the directory where it says ‘data directory’. Then, enter the ID of the stage you’re looking to edit in the STAGE ID box (w5a01 in our case). If the game is not already set to Sonic Forces, be sure to set it as such.
+Anyways, back to what i was saying before: click into the w5a01 folder. You’ll see a bunch of pacs. You won’t need to do much with these for now, but just know that these files are opened using ‘SFPac’. Back out of the w5a01 folder, and copy it into the ‘wars_patch’ folder in your mod. While still in your mod’s wars_patch folder, you’ll want to create a folder named ‘gedit’. Next, navigate back to the folder containing the game’s CPKs, and go into ''its'' wars_patch folder (NOT the one in your mod that you just copied files into!). Once inside, you’ll see a ‘gedit’ folder. Go inside it, and copy ‘w5a01_gedit.pac’ into your mod’s gedit folder. Now, you’re ready to start using HedgeEdit. (If you haven’t already downloaded it, do that now). Next, I’m going to teach you how to open stages in HedgeEdit. Simply go into your mod’s wars_patch folder, and copy that directory. Open hedgeedit, click ‘open’ and paste the directory where it says ‘data directory’. Then, enter the ID of the stage you’re looking to edit in the STAGE ID box (w5a01 in our case). If the game is not already set to Sonic Forces, be sure to set it as such.
 One more quick thing: Be aware that HedgeEdit copies anything you load or save to it’s own cache folder (to make loading faster) so if you’re running low on space, you might want to check there every now and then to clean out anything you don’t need.
@@ Line 106: / Line 106: @@
 Let me start by letting you know that, if there’s a specific object from another stage you want to use, you’re gonna want to copy it’s assets (which may include files from both the object pac AND terrain common) into your mod’s object pac or terrain common. Though, as long as it’s the same in-game location (such as Green Hill) it usually should work without having to add files.
-Quick note: You can move the camera in HedgeEdit by holding right click and moving the mouse. You can also press the arrow keys or wasd keys to move, and hold shift to move faster.
+Quick note: You can move the camera in HedgeEdit by holding right click and moving the mouse. You can also press the arrow keys or WASD keys to move, and hold shift to move faster.
 Most object descriptions are at the bottom of the object template xmls, unfortunately HedgeEdit doesn’t display object descriptions in-editor and I really don’t want to spend thirty minutes reading all of the object descriptions, so… sorry. You can open up the templates in notepad.
@@ Line 209: / Line 209: @@
 |-
 | Range
-| The search range of the Badnik.
+| The search range of the badnik.
 |-
 | Missileriselength
@@ Line 263: / Line 263: @@
 |-
 | IsRespawn
-| Whether or not this Badnik respawns. It respawns by materializing in mid air and dropping onto the ground.
+| Whether or not this badnik respawns. It respawns by materializing in mid air and dropping onto the ground.
 |-
 | BulletSpeed
@@ Line 289: / Line 289: @@
 |-
 | MoveSpeed
-| The speed this Badnik moves at.
+| The speed this badnik moves at.
 |-
 | MaxMoveDist
-| The maximum distance this Badnik can travel.
+| The maximum distance this badnik can travel.
 |-
 | isFV
@@ Line 298: / Line 298: @@
 |-
 | LocaterList
-| Each locator correlates to the position the Badnik will land after being hit. Note that the locators must be rotated to face the direction the Badnik is meant to face.
+| Each locator correlates to the position the badnik will land after being hit. Note that the locators must be rotated to face the direction the badnik is meant to face.
 |-
 | RingType
@@ Line 304: / Line 304: @@
 |-
 | RingID
-| The number of the Red Ring or Number Ring this Badnik drops.
+| The number of the Red Ring or Number Ring this badnik drops.
 |-
 | isBound
-| Unknown.
+| ''Unknown.''
 |}
@@ Line 324: / Line 324: @@
 |-
 | Locatelist
-| The locator defines where this Badnik will move to after it spawns. These can be used as pathnodes in order to make the Badnik move around. The potos pauses for a brief moment between locators.
+| The locator defines where this badnik will move to after it spawns. These can be used as pathnodes in order to make the badnik move around. The potos pauses for a brief moment between locators.
 |-
 | AttackInterval
@@ Line 333: / Line 333: @@
 |-
 | RespawnTime
-| The amount of time after this Badnik is destroyed before it respawns. Set to 0 in order to have it not respawn.
+| The amount of time after this badnik is destroyed before it respawns. Set to 0 in order to have it not respawn.
 |}
@@ Line 365: / Line 365: @@
 |-
 | Pad values
-| Unknown. Possibly just padding values.
+| ''Unknown'', likely just padding values.
 |-
 | Repeatspantime

@@ Line 43: / Line 43: @@
 When placing or moving Rings using the arrows, their vertical height will be offset by 6 units (this is not reflected visually). If you want to move rings without encountering this issue, you can type the position in manually. ''This issue has been patched for ObjRing and ObjRedRing as of V3. Other objects that possess this issue will be updated in the future.''
-'''Object selection bug''':
+'''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.
@@ Line 55: / Line 55: @@
 Whenever you place an object, the scene view tabs will collapse. Whenever you save, the scene view and assets dialogue will close. This gets very annoying very fast, but uh… Too bad, F in the chat.
-'''Movement arrows disappearing''':
+<s>'''Movement arrows disappearing''':
-Movement arrows disappear when you select multiple objects.
+Movement arrows disappear when you select multiple objects.</s> Fixed as of V4.
 '''Actstgmission issues''':