Limit of Custom properties at StartGameArgs
Key Problem
Max amount of custom properties(if any) and how to handle longer load time due to massive size. Optimal n-size.
Expected Output/Definition of Done
Difference between different StartGameArgs time-wise, maximum amount of multiple arguments.
Key Solution
StartGameArgs, a struct class that is passed to the NetworkRunner when starting a room/session, has multiple public attributes that each can be specified to start with custom configuration(s).
*Example of specifying a custom StartGameArgs object.*
Having more attributes being specified does not have significant time difference when compared to less attributes specified. Each attributes are not collection except for SessionProperties (Dictionary <string, SessionProperty>)
Notable Attributes
-
SessionProperties, a collection of item in form of
Dictionary <string, SessionProperty>. Have limited amount of items to be passed in the Dictionary having max size of 10 properties. Else will be returned withStartGameException: Max number of Custom Session Properties reached, only 10 properties are allowed. -
GameMode, determines the type of room being created. Does affect the time taken to make room specifically when using
GameMode.Single, as it is not starting any connection to the Photon Cloud thus having significantly faster start time than any other modes.
No Comments