Cast to Player controller input pin unconnectable

Can you put show screenshot of you graph?

Hi,

I am new to UE4 and C++ / Blueprints but not new to programming as a whole.

This is with UE4 v4.13

As part of my getting up to speed with UE4 I am following a YouTube tutorial series on creating a multiplayer game in blueprints (Blueprint Multiplayer by Unreal Engine). I am on part 14 [here][1] and have hit an issue. On the cast to lobby PC (@ 13:55) the cast is being created with the input pin being unconnectable. When I mouse over the pin (labeled as object) I get an error about wildcards.

I suspect I have missed a checkbox or connection somewhere else in the previous 13 videos but with no experience on this I am not sure where the config info to generate the input pin details are set.

For those without access to YouTube, the flow is (items in bold are the issue);

All players → Set Array of players → for each loop → cast each (custom) player controller → Show widget

Any help / direction would be much appreciated.
[1]: Blueprint Multiplayer: Lobby Menu Graph | 14 | v4.11 Tutorial Series | Unreal Engine - YouTube

Thanks for the reply.

Hey RimBlock,

You’ll need to plug in a reference to a Controller in your Cast to LobbyPC node for it to cast from.

Yes, as I understand it, the feed comes from the for each loop but it will not accept linking element to the cast to it.

Thanks for the pointer, turns out the All Player Controllers variable, defined in player lobby GM, was a Boolean and not a Player Controller. I fixed that and now it is all compiling.

Supplemental question, where is the command reference (ie. standard UE function descriptions, input / outputs etc) ?. I cannot seem to find one.

All Player Controllers is an array of bool types. bool will not be able to cast into a LobbyPC (I am guessing a Player Controller).
You will need a reference that is of a like type to LobbyPC to cast into LobbyPC, such as Controller or Player Controller.

We have not heard back from you in a few days, so we are marking this post as Resolved for tracking purposes. If you are still experiencing the issue you reported, please respond to this message with additional information and we will follow up.