Replaced mod creation with wiki link

Author: Nagord

README.md

@@ -29,7 +29,7 @@ Injects a basic mod loader into [*PULSAR: Lost Colony*][10].
 
 By default, PML will attempt to patch the Steam version of the game in Steam's default install location.  To patch a PULSAR installation in another location (non-Steam version, copy of client, etc), simply specify the path to `Assembly-CSharp.dll` as shown above.
 
-Afterwards, add mods to then `PULSARLostColony\Mods` directory, then run PULSAR normally.  `PulsarModLoaderInstaller.exe` is not needed after this.
+Afterwards, add mods to the `PULSARLostColony\Mods` directory and run PULSAR normally.  `PulsarModLoaderInstaller.exe` is not needed after this.
 
 ### Removal
 
@@ -41,73 +41,4 @@ Optionally remove `PulsarModLoader.dll` and `Assembly-CSharp.dll.bak` from `PULS
 
 ## Creating Mods
 
-All mods must be C# Class Libraries targeting .NET Framework 4.0 or later (to work around some jankery).  See [this screenshot][11] for an example of project creation settings in Visual Studio Community 2019 ([free download][12]).
-
-[11]: https://i.imgur.com/X7bDnYr.png "New Project"
-[12]: https://visualstudio.microsoft.com/vs/community/ "Visual Studio 2019"
-
-You Should reference the following assemblies in your mod project:
-
- * `PulsarModLoader.dll` (PML code)
- * `Assembly-CSharp.dll` (Game code)
-
-Additionally, the following Assemblies might be needed.
- * `0Harmony.dll` (Patch Code)
- * `ACTk.Runtime.dll` (Obscured Object Code)
- * `UnityEngine.CoreModule.dll` (Engine code)
- * `UnityEngine.*.dll` (optional; specific DLL depends what changes are made)
-
-Mods must also contain a subclass of `[PulsarModLoader.PulsarMod]` for mod initialization.  This class is instantiated once during game startup (currently before `PLGlobal.Awake()`), so do mod setup in its constructor.  The base constructor already loads Harmony, so only overriding `protected string HarmonyIdentifier()` may be enough for simple mods.  To extend setup, override the constructor with a call to base:
-
-```csharp
-class MyMod : PulsarMod
-{
-    public MyMod() : base()
-    {
-        // Do additional setup here
-    }
-    
-    [...]
-}
-```
-
-Using [`HarmonyLib`] to hook PULSAR methods is strongly recommended due to its simple API and tools that help multiple mods play nicely when modifying the same methods (stacking hooks instead of overwriting each other, prioritization, etc).  Any class using Harmony decorators will magically hook their methods.
-
-[13]: https://github.com/pardeike/Harmony "HarmonyLib"
-
-### Basic Mod Example
-
-```csharp
-using PulsarModLoader;
-
-namespace ExampleMod
-{
-    class MyMod : PulsarMod
-    {
-        public override string HarmonyIdentifier()
-        {
-            // Make this unique to your mod!
-            return "com.example.pulsar.mods";
-        }
-    }
-}
-```
-
-```csharp
-using Harmony;
-
-namespace ExampleMod
-{
-	[HarmonyPatch(typeof(PLNetworkManager))]
-	[HarmonyPatch("Start")]
-	class VersionModifier
-	{
-		static void Postfix(PLNetworkManager __instance)
-		{
-			__instance.VersionString += "\nCool Kid Version";
-		}
-	}
-}
-```
-
-Distribute mods as `.dll` assemblies.  To install, simply drop the assembly into the `Mods` folder; any properly-defined `*.dll` mods assemblies are automatically loaded.
+[Check out the wiki for basic instructions on creating mods.](https://github.com/PULSAR-Modders/pulsar-mod-loader/wiki/Creating-Mods)