I’m trying to set an object variable as a player so that I can have specific players with certain traits and others with certain traits right off spawn. From what I understand all Players are Objects, so I should be able to assign “ON PLAYER SPAWNED” to “SET OBJECT VARIABLE” where the output “player” connects to the input “object”. So when I use the “APPLY TRAIT SET”, I can fill in the input “player” with the output “object” in “GET OBJECT VARIABLE”. I have made sure that all the identifiers match appropriately and that all the scopes’ are set to “global”. Does any one know what I am doing wrong? Or what I need to do to store a player in a variable?
For more clarification, a good example of what I’m trying to do is set some players to survivors, and the others to infected.
It sounds to me like you’re attempting to pass a “player” to the “OBJECT” pin of the “SET OBJECT VARIABLE” node. I believe that is incorrect if you’re trying to save the player to that varaible. When you’re using a “SET OBJECT VARIABLE” node, you would connect the object (a player, in your example) that you want to save to the “VALUE” pin.
Short digression - As I understand it, the “OBJECT” pin is only relevant when you’re setting a variable using the value “Object” for the “SCOPE” pin. If you specify “Object” scope, then the variable is stored on the associated object. I believe it would be possible to store the player, as the value of an object variable, using the object scope, by providing the same player as both the “OBJECT” and “VALUE” pins (though IMO it would be pointless, because to be able to access that variable that exists in the player-object’s scope from somewhere else, you would already need a reference to the player). but I believe when you’re using the LOCAL or GLOBAL scopes, the “OBJECT” pin for the various “SET XYZ VARIABLE” nodes is effectively ignored.