player.name is renamed to Guest xxxx?

Options
mindlube
mindlube
edited January 2012 in Photon Unity Networking (PUN)
It it correct that if a player's name is not unique in the room, it gets renamed by Photon to "Guest xxxx"? I have seen that happen and it's not documented, so just wanting to confirm I understand what's going on . thanks.

Comments

  • mindlube
    mindlube
    Options
    Or, to be more specific, if I'm setting the player name before connecting to Photon,

    why does the masterClient receive the OnPhotonPlayerConnected event for a new player named "Guest (int)" ?

    I want to encode some info in a json string in the player name, but photon keeps renaming the player to Guest (int).

    Thanks- hopefully just confused here.
  • mindlube
    mindlube
    Options
    Hmm, setting the name after connecting to photon, but before any other photon events seems to work though. :D
  • Tobias
    Tobias admin
    Options
    I hope you didn't spend all those hours on this topic :)

    You got all code of PUN. It's in there somewhere. Search for "Guest" and find it in the PhotonNetwork constructor.
    In there, the re-naming is plain wrong and should be replaced with string.Empty. This sets the name (until otherwise set) to "". This is what the next update of PUN will do but it's maybe not cause for your issue.

    There is another place in a demo "MainMenu" Awake. Again, the name is set to "Guest" and a random number. Most likely this is where your name is re-set again.
  • mindlube
    mindlube
    Options
    Tobias, thanks OK thanks for the tips & encouragement I will try to remember to dig into source code next time. I saw there was a .dll too, so I wasn't sure how much is actually exposed in the .cs code.

    Speaking of PUN 1.8, and player names, is there any metadata/properties support for players now? Another thread was saying that was going to get rewritten or something? I want to stuff a permanent unique id string into the photon player, but encoding json into the photon player name is perhaps not the best way to do it.

    edit: actually never mind about that. I realized that since PhotonMessageInfo has the photonplayer sender, it's easy to make an RPC saying "here is my player metadata".
  • Tobias
    Tobias admin
    Options
    v1.8 is more or less a bugfix release, so no properties yet, sorry.

    Using RPCs is a much better way to send the unique ID than encoding it into the name.
    Make the RPC buffered and it gets sent to players when they join, too.

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).