I had years of fun just making new builds, sometimes to optimize and sometimes to just make something crazy work, before getting bored. I'm not a fan of the new endgame, the latest expansion plays too much like NWNO, but there's tons of fun game content before you get to the endgame, with many complex and interesting build choices (being very D&D based, there's remarkable depth to the "skill system" - it's like nothing else I've seen). There's so much low level content that you never need to repeat a quest on your way to max level. And remember that an emulator of a game is not a work that would be done in 1 day.By far the least repetitive MMO I've played, with the best low-level content, is D&D Online. All links in this thread are broken 'even if they was not complete' a person with knownledge could do something with that.
#SCARLET BLADE VENDETTA INCORRECT PASSWORD FREE#
first of all I appreciate the effort of your team your doing a great job trying to revive the scarlet blade.But in my opinion and considering that you don´t have free time to advance you should consider to share the project files.
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.good news anyway. 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. Once the client attempts to use character authentication (in game) to retrieve character data from the database, it fails due to not having maintained authentication of the 'character inside the client'. As the web api is merely forcing an account name/password to be validated for account login / char creation only (at the moment). 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.
0 kommentar(er)
