Jump to content
Sign in to follow this  
rimblock

Changes with SetOwner in A3 1.40 ?

Recommended Posts

Hi,

So I have a script working fine where a new unit would be created and equipped on the server and then passed to the client via the setOwner command. The client would then place the player in the new unit and dispose of the old unit.

Since A3 v1.4 came out I am now getting a new error. Everything still seems to be working but I would still like to dig into what is causing it and remove it if possible.

Script command setOwner cannot be used for object 'C_man_p_beggar_F_euro'. Use setGroupOwner instead.

What are the new constraints with setOwner ?.

Share this post


Link to post
Share on other sites
Hi,

So I have a script working fine where a new unit would be created and equipped on the server and then passed to the client via the setOwner command. The client would then place the player in the new unit and dispose of the old unit.

Since A3 v1.4 came out I am now getting a new error. Everything still seems to be working but I would still like to dig into what is causing it and remove it if possible.

Script command setOwner cannot be used for object 'C_man_p_beggar_F_euro'. Use setGroupOwner instead.

What are the new constraints with setOwner ?.

Think the error is more than self descriptive, use setGroupOwner instead. As for the question https://community.bistudio.com/wiki/setOwner

Edited by Killzone_Kid

Share this post


Link to post
Share on other sites

I noticed the updated text in the Wiki after posting and changed to setGroupOwner and the answer seems to be that setOwner is no longer any good for AI units.

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×