Getting very angry at Plugin Development

[OmniOwl]

@Antidamage;390335

The plugin tutorials are rubbish, I agree completely. Fortunately you don’t need them.

Tip #1: Try the built-in plugin creation wizard. I think it’s out of beta now so you should have it on by default, but if not you’ll likely need to enable it under plugins (since it’s a plugin too) then reload. Then you can use it to make your plugin skeleton and just start adding code to it. You can find it under the File menu once it’s enabled.

Tip #2: don’t use VS to create any files. Make the files yourself in windows in the proper location, name them correctly then drag them into the VS project explorer to get them into that. If you let VS make them, it’ll put them into your intermediate folder which is annoying and dangerous.

Tip #3: UE won’t put your class files in the right place for your plugin (it’s fine for actual code projects), but it’s still a good way to get the files created and populated with some sample code.

Definitely post your build errors as there’s a lot of gotchas about UE code projects that you need to learn. They’re not too bad though as everyone here can help you out with them as you come across them. One of the main ones that always gets me is the “missing module” problem. Just including header files isn’t enough, you need to put in your build.cs file for your plugin that it’s using the right module. If you already know about this then cool, otherwise there’s a specific way to solve this problem and get the info you need.

Okay so, I used the Wizard and went through the tedious task of making folders in VS and drag and drop files in there. Here are all the Errors:

Most of them got solved by making it auto-solve the issue. It added

#include "..\Public\RandomNumberGeneratorsPlugin.h"

at the top of the file. Now I have the following errors:

And here is what that file looks like: