Thank you for responding. I spent some time messing around and found that the version of dnSpy I was using (6.1.8) was adding unnecessary lines of code that it could not interpret and if I simply removed/reformatted the lines throwing errors, the problem would be resolved.
This new version fixes the issue altogether, thank you very much.
+ I want to add this post in case anyone comes looking for solutions after me.
dnSpy just kinda sucks, it will tell you there are things wrong with your code that you didn't change, it will put things in the code that it can't read and it will say it's broken, it needs to be restarted if you added a method and try to call it in the same session, there are many problems.
Updating to the correct version does prevent some of these things from happening but they will still occur. The solution is being smart enough and have the patience enough (because you have to do it everytime you recompile) to unfuck whatever it decides to fuck up.
There's always the possibility that this issue only exists on my machine, or it's a fault of mine but just in case anyone else has this issue, blame dnSpy and spend the next 6 hours reformatting the same 6 lines of the base game's code everytime you make a change and save and restart the program frequently.