Which UE4 Python Implementation to use?

jaredpemberton47 · February 12, 2019, 3:29pm

I am researching automating the editor via Python but have ran across a few conflicting methods that I would be appreciative to receive some experienced perspective on.

One method, which I assume is the more proper method, is to simply enable the Python plugin and Editor Scripting plugin within UE4 and utilize the Unreal Python API documentation.

The other method, which I started with, has you install an embedded Python plugin into the plugins folder within your current project.

github.com

20tab/UnrealEnginePython/blob/master/tutorials/YourFirstAutomatedPipeline.md

Your First Automated Pipeline with UnrealEnginePython (Part 1)
=

In this tutorial i will try to show you how to build a python script that can generate
a new Unreal Engine 4 Blueprint implementing a Kaiju (a big Japanese monster) with its materials and animations. In the second part a simple AI based on Behavior Trees will be added to the Blueprint as well as a bunch of simple unit tests..

Running the script from the Unreal Engine Python Console will result in a native Blueprint (as well as meshes, animations, a blackboard and a behaviour tree graph) that does not require the python plugin to work.

Technically i am showing the "editor scripting" features of the plugin, not its "gameplay scripting" mode.

If this is the first time you use the UnrealEnginePython plugin you should take in account the following notes:

* when you see CamelCase in the python code (for attributes and function calls) it means the UE4 reflection system is being used. Albeit CamelCase for variables and functions is not 'pythonic', you should see it as a 'signal' of jumping into UE4 reflection system.

* in this tutorial i use the embedded python editor. It is pretty raw, if you want you can use your favourite editor (Vim, Sublime, Emacs...). Anything that can edit python files will be good.

* Python scripts are stored in the '/Game/Scripts' folder of the project

* The Python code is pretty verbose and repeat itself constantly to show the biggest possible number of api features, i strongly suggest you to reorganize/refactor it if you plan to build something for your own pipeline

This file has been truncated. show original

Since I am learning Python as I go, I have ran into issues utilizing the Unreal Python API Documentation while using this method. Perhaps this is terrible coding on my part or the code is incompatible between the two methods. I have a feeling it is both

Is this a correct assumption? I appreciate any feedback/advice.

-Jared