diff --git a/Using-RenderDoc-in-a-Development-Environment..md b/Using-RenderDoc-in-a-Development-Environment..md
new file mode 100644
index 0000000..15a75ea
--- /dev/null
+++ b/Using-RenderDoc-in-a-Development-Environment..md
@@ -0,0 +1,42 @@
+Foreword: This method is disgusting but relatively easy to setup. There's very likely a better way to achieve this.
+
+## Setting up RenderDoc
+
+Install [RenderDoc](https://renderdoc.org/).
+
+Go to Tools > Settings.
+
+![](https://i.imgur.com/LVmSBCE.png)
+
+In the General tab on the left (should be open by default), enable process injection and restart.
+
+![](https://i.imgur.com/LL7UqSv.png)
+
+## Launching the game
+
+Add a breakpoint on the first line of `net.minecraft.client.Main#main`
+
+![Line numbers subject to change](https://i.imgur.com/QgzlAyd.png)
+
+Launch the game.
+
+Once the breakpoint is hit, find the pid of the Minecraft process.
+
+Open RenderDoc if you haven't already.
+
+Go to File > Inject into process.
+
+![](https://i.imgur.com/MhP4t46.png)
+
+Enter Minecraft's pid into the bar on the bottom. If it doesn't show up, click the `Refresh` button on the right.
+
+![](https://i.imgur.com/TPgQUgp.png)
+
+Double-click on the process in the list.
+
+![](https://i.imgur.com/UlEGksT.png)
+
+Resume from the breakpoint.
+
+
+