Author Topic: Network ID Assignment Problem  (Read 207 times)

Gabemeister1201

  • Newbie
  • *
  • Thank You
  • -Given: 4
  • -Receive: 0
  • Posts: 10
    • View Profile
Network ID Assignment Problem
« on: October 03, 2017, 04:40:29 PM »
Hello everyone,

I am having a strange issue with Network ID assignment on prefabs that are instantiated multiple times.

I have an object in my scene with a TN Object component attached that has the ID 42 (I have changed it to see if that would fix the problem and it didn't).
When I instantiate the prefab while the same prefab exists in that scene, I get this in my console [Gyazo Link & attached]: https://gyazo.com/b5a626dcaf1970e974068ad0438dcb3c 

Not sure what I am doing wrong. It doesn't seem to be affecting anything yet, however I fear that it will cause problems in the future. Not really sure if that is the case as I am still quite new to TNet.

Thanks,
Gabe

cmifwdll

  • Global Moderator
  • Full Member
  • *****
  • Thank You
  • -Given: 0
  • -Receive: 135
  • Posts: 244
  • TNet Alchemist
    • View Profile
Re: Network ID Assignment Problem
« Reply #1 on: October 03, 2017, 06:11:39 PM »
You should use network ID of 0 on objects that are instantiated multiple times. This'll tell TNet to generate a unique ID for each instantiation.
You will run into problems with the same ID; RFCs won't know which object they're supposed to execute on.