Any way to identify the object via PrefabPool in first hand?

Options
Levent
Levent ✭
in Photon Bolt
if i create let's say a FPS character on ClientA, then it is automatically replicated on ClientB as TPS character by using the class extending IPrefabPool. All is okay, i just wonder if i can identify the TPS character on ClientB at first event? I'm using a "ConnectionID" state right now to identify it, but would be very nice to identify it on the first PrefabPool Instantiate event on ClientB. Otherwise It is not easy to control their call orders on client side. What i do is to buffer them first and wait for their "ConnectionID" state is set from server and then they are identified so i can do some assignment. Any easy way other than this? Thanks, regards.

Cookies,
anyone?

We use cookies and related technologies to enhance your experience, show you personalised content and analyze performance and traffic on our website. By clicking on the „Accept All“ button you consent to the use of non-functional cookies and the subsequent processing of personal data to optimize our website and services as described in more detail in our Privacy and Cookie Policy.

By clicking on the „Customize or Deny all“ button you can decide otherwise. Clicking on the „Customize“ button will take you to a page where you can configure the usage of non-functional cookies (and related technologies) or deny all of them. You can access these settings at any time and also subsequently deselect cookies at any time in the footer area of our website.

ACCEPT ALL

Cookie Overview

We use the following categories of cookies and related technologies to enhance your experience, show you personalized content, and analyze performance and traffic on our website. We respect your right to privacy and accordingly you can chose to not allow some types of cookies (and related technologies). Click on the different category sliders and change our default settings to manage your cookie settings.

For more information on the specific cookies/related technologies we use and on how we use these, please see section 15 E. of our Privacy and Cookie Policy.

ABSOLUTELY NECESSARY

Authentication cookies we use are required to run our services … Cookies are required: Link

FUNCTIONAL AND MARKETING COOKIES

These cookies collect anonymous data and allow us to optimize our website and user experience. These cookies are listed here:

ANALYTICS

Help us to understand how visitors interact with our services, enables us to analyze and improve our services (also through third party analytics).