The authenticated account can log out and generate a new character based on that authentication, but it is not carried over inside the game.Once in game, the client does not have the proper authentication to retrieve data from the database. The web-api authenticates account login and character creation. Currently, we're using the (custom made) web api to authenticate the client. So the next item auto-equipped gets forced into weapon slot without a means to validate InvenType and SlotIndex (since the SlotIndex returns 'null').This is also why the item poofs upon logout, as the item registered in weapon slot is no longer 'temporarily' stored in memory - the location slotted upon reward acceptance.We'll continue to work on the issue. Problem with other gear types, they cannot validate their InvenType/SlotIndex from the db vs character.
The server knows the character is correct and thus populates the data to the database, but retrieval is failing since the client cannot authenticate the character during the retrieval of information via database queries.In this instance the client can only return a null value for SlotIndex (for character sheet) and the auto-equipped items get stored into the 'weapon slot' since the weapon slot would have SlotIndex = 0 (queensguicharinfo.layouts) and SlotType (queensguiinventory.layouts).Auto-equipped items are done so at time of accepting reward, so show automatically in character sheet. This can be validated by attempting to use in-game GUI's that reference character authentication (2 examples are the Broker or Guild Storage - which require character authentication and query from the database, but fails due to lack of character authentication via client).Since the character authentication in game versus the database retrieval of information is not maintained the items cannot be read from the current character stored data in the database.
0 kommentar(er)
