DontDestroyOnLoad and TNManager.Create

[Simie]

I have a few dynamic objects which persist between scenes. I am getting "Network ID ## is already in use" error messages, which appear to be caused by TNManager.LoadLevel resetting the object counter used for assigning ids. Is there a supported way of having network objects correctly surviving a scene load?

[ArenMook]

You should not be setting TNet-created objects to be DontDestroyOnLoad.

If you want a static object that travels from scene to scene, then don't use TNManager.Create to instantiate it. Simply have it already be there with a TNObject attached and an ID already set.

[Simie]

Alright, thanks.

[MasterMoo]

Hi Aren,

I have a follow up question.  I'm creating a turn-based strategy game.  In my first level the players select their combat units that they'll control.  Once all players have indicated they are ready the game loads the second level where the game play takes place.  I'm using TNet to instantiate the units in the first level.  Is there no way to persist those units to the game play level?  Thanks!

[ArenMook]

Save the player selection in TNManager.playerDataNode (each player should save their own selection). When the level loads, each player is responsible for creating their units using the stored data.

I do this in Windward myself -- I save the player's zone ID, respawn position, pennant colors, ship colors, sails, inventory and ship selection in the player's data object. When the scene loads, I create the appropriate ship and "equip" items (attach scripts).