Showing Posts For Celebane.9813:
1. There currently no way to determine whether an item in an inventory has been soul/account-bound. We’ll have support for that in the next couple of weeks. (EDIT: maybe next month; I’m not exactly sure when that stuff is due to go out).
2. Depends. There’s three parts involved — the map instance server, the player database and the API server that reads player data. The map instance server sends data to the player database roughly every five minutes, or when you make a cross-server transaction (e.g., selling on the trading post, interacting with the guild bank, etc), or when you change maps. The API server only requests a given player blob (which contains all characters) at a maximum of once every five minutes.
Given that, if you just switched maps and your account data hasn’t been requested recently, you’ll get the exact same data as you see in-game. The worst-case is that you’ll see data that’s ~10 minutes old (e.g., the API server cached data from the database just before the map instance server persisted it, and you requested it just before the API server expired its cache).
Numbers are probably a bit off, but it’s safe to assume that any API data regarding the account/characters is a few minutes old.
Thanks for answering so quickly.
Account Bound isn’t really an issue because that shows up as a flag AccountBoundOnAcquire and if the item is on the account/character well…. it’s bound.
1. Looking at the items from my characters inventory i can see flag SoulbindOnUse on weapons. Is there a way to see if the item has actually been bound? I looked at 2 different items. One was bound and the other was not but I could see no differences in the JSON.
2. How much difference is there between in game actions vs. data that the API pulls from. (i.e. If my character picks up an item how long before an API query actually shows that the item is in the character’s inventory.
I did make my way back there and there’s a chest with items in it but didn’t find much else of value.
If you just got back there then you only scraped the tip of the iceberg on the puzzle itself.
Half a month later and this still hasn’t been fixed.
If it was a small bug I wouldn’t mind so much, but it’s preventing this JP from being started entirely.
Why the hell hasn’t this been fixed yet?
This is the type of content I expect ANet to proactively fix ahead of more minor concerns, but expecting a solution after 2 weeks is asking a lot. If you ask for the fix this quickly, you are asking for a fix that isn’t fully tested… And that could leave things immeasurably worse.
Seriously, cool your heels a bit. Ask again in 2 more weeks.
If they have a fix in the pipeline by then they may indicate such (or they may remain silent and you might have to wait a final 2-4 extra weeks to see any fix, depending on what the actual release schedule is, and how hard the bug is to fix). Software release cycles are slow for many reasons, and bug fixes need to be slow for their own reasons as well…mostly so that QA has a chance to spot any new failures the fix may introduce.
//Portable Corpse
I think the impatience is simply because this WAS working and then was broken with an update. It shouldn’t be too terribly difficult to figure out what changed in the update 2 weeks ago that caused it to break and undo it. It’s not like this was brand new content that was deployed in a bugged state. I’d be a lot more tolerant if that were the case.
Same issue on Henge of Denravi Server