Why is my character movement component null?

I understand that these features seem like they’re important, but it still doesn’t justify ignoring issues that break the engine and prevent people from delivering a full project. UE4 is great for getting a bunch of people hyped up so you can get funding, but even as I write this answer I’m seeing a boatload of issues that are actively preventing these people from packaging their games. Lighting features are awesome and everything, but I can’t think of anyone that wants to install the editor and run a game from source rather than running a packaged .exe. So eliminating bugs that prevent the packaging process should be P1 IMO. At worst, there should be a dedicated wiki for debugging and removing issues that could prevent the packaging process. It wouldn’t be as big of a problem if Epic didn’t completely dismiss bug reports either but in most cases they’re just going to tell you that it’s your fault for not assuming that the engine would act like a piece of garbage when you need it most. My frustration isn’t just from the presence of these issues. I’m frustrated because the only documentation for resolving these issues comes from a handful community members that made their wikis 10-15 engine versions ago. UE4 is awesome and that’s why I’ll continue to support it over Unity any day, but issues like this aren’t okay, especially when the documentation states that they are clearly supported.