For the toast!
For the toast!
There should be atleast at confirmation: “Do you want to kick that person?”.
Maybe not — a lot of guilds purge inactive members once a month; this would slow them down a lot (and get them to stop paying attention to the message).
Removing the option from friends list and party menu would be a great start.
Then maybe for guild leaders there could be a button on the roster that is something like: “show everyone who hasn’t logged on and/or hasn’t gained any achievement points since year-month-day” and if that’s selected, then there’s no warning dialogue that you are about to kick.
Once both of those are done, then add a confirmation message before kicking someone in any other context.
This bug warrants a fix. I shouldn’t have to resize my inventory window everytime I login.
It happened before. then they fixed it. then they broke it again. its the cycle of A-net.
A guy in my guild has kicked several people from the guild this way. We’ve just taken to calling him an evil overlord.
Haha, I second this so badly. I’ve kicked one of our member like 4 times already. Must agree that it’s a poor UI, especially when you’re trying to join a guildie on another map and the option itself is placed right above the Kick from guild button.
I couldn’t see a place for feature requests, so here it is. Having the “Kick from guild” option in the party window is just an accident waiting to happen. I have never intentionally kicked anyone from the guild within the party window, but I have done it twice now accidentally. Please move this option onto the guild panel only.
Thanks,
During a boss fight:
Oh sweet, an Ice bow.
Gonna pick it up.
Oops, picked up a banner.
Try again.
Picks up a rock.
Dang it.
I dunno what I’m picking up anymore.
=P
I also noticed that something was terribly wrong with “Pick Up [F]” but couldn’t remember what it was.
why are these all on the same key anyway?
why can I not bind revive player, talk to npc, and pick up item to different buttons?
The interact [F] problem has been discussed a lot because re-binding auto-loot key works but is not the ultimate solution to all annoyances of that [F]unction (including it not working on chests). I have several suggestion just on it gathered in this list:
48. Option to AoE auto-loot everything automatically (AoE-loot-on-kill) instead of AoE-loot-on-constantly-spamming-interact-key-and-ressing-or-talking-to-NPCs-instead. I know it is possible to bind interact and loot onto different keys, but having 1 key for both seems more user-friendly. Still, hilarious things happen when you pick up a banner instead, press 4 and rush into certain death because you didn’t notice it wasn’t a loot [F] but a banner [F].
49. Dedicated colour for looting [F] only (blue?).
50. Option to disable talking to NPCs in combat (there’s nothing worse than having an NPC dialogue pop up over mobs and target info while trying to spot a Subjugator in the middle of a zerg).
51. Ability to display a list of [F] actions and/or cycle through them instead of clicking to select a target which fails 95% of time (just try to click and pick up a Fiery Greatsword next to a Frostbow next to warrior Banner next to a dead player next to a dead NPC next to a NPC with a popping dialogue box); and/or a “Select next object” key. Also makes it easier to choose between crafting station/trader/merchant/NPCs and similar interact-heavy environments.
52. Do not display “Use [F]” for siege when it is already used by another player.
53. Option to relocate the interact [F] pop-up.
why are these all on the same key anyway?
why can I not bind revive player, talk to npc, and pick up item to different buttons?
“Rise from the grave!” byebye Butterflies
This not okay.
just give Citri 200g+ item plus exp for survivor + item to summon carrot infinity
Update: Still an issue.
To the guy above me, it WAS an issue a few months ago that got a fix. Then the April patch hit and it’s been close to 2 months since Anet’s bothered to do anything to fix it. It’s not the same as the last one. Last time, whenever you opened your inventory, it would slowly change size. Now, whenever you log out and log back in, your inventory will be approximately one size smaller (as opposed to 10 across, it’s not 8 or 9 across).
Update post-03/06 patch: Still an issue. I was hoping that Anet pushed the patch through without telling anyone. They have not.
Bumping my own posts now, but nobody else seems to be talking about this. Have to keep it at the front of the forum queue so Anet does something about it. Even just mentions that they’re working on the issue (although that means a fix is at least a month away)
yeah i moved on to necro. maybe once no one plays this class anymore, anet will realize that they nee to fix the bugs and rework the class…but that would be wishful thinking
Nah, they just will be happy about it.
‘Yay, finally no one plays that annoying unique class that has no equivalents in other mmos and was contributing to making GW2 something standing out among other games, wich was totally unacceptable. And we don’t need to imitate active bugfixing for it anymore! Time to buff some other class every second player has!"
Seriously, sometimes I can understand devs unable to solve bug due to mechanism limits. But lack of responses and delayed/unable to fulfill the promises they make to mesmers are downright disheartening. We have amazing contributions from this thread and mesmer forums but the conversation seems rather in one direction only.
It’s almost like mesmers are BEGGING for fixes now. A very strange consumer/producer relationship indeed.
(edited by NICENIKESHOE.7128)
It’s almost like the Mesmer bug fix section of the patchnotes is a running joke xD It’s hard to believe. Every time I excitedly scroll down to the Mesmer section and am greeted with tooltip changes and fixes for obscure bugs we rarely encounter.
I’ve lost countless items to this bug, thankfully nothing as expensive as a precursor, but it is endlessly frustrating to sell a nice weapon when you’re sure you’re selling a beet you just harvested. And of course the weapon instantly sells due to the buy orders, giving you no chance to correct the game’s mistake.
It is even very easy to mess up with stacks of items, I’ve often had problems after hitting the nodes in my home instance. I’m not positive this was with the right clicking and sell option.
I’ve had this happen a quite a few times since the Bazaar patch dropped and the TP interface fell from its knees to its face. I never used that inventory list method until then when I got fed up trying to get the usual item listing up after several tries most times. I sold off quite a few items at very low prices (fortunately, at that time they sold to high buy orders so it wasn’t as bad as it would be now), and a number of items were put up for far more than they should’ve causing me to lose money by having to take them down and relist them properly.
Dunno what’s up with that GUI element, but it can’t be trusted. Showing one item’s data, and selling a different one when you hit that button is….not a good thing.
It first happened to me months ago, and like Stinvec, I do the exact same thing now. And shortly after the patch, someone was in LA saying they accidentally sold Dusk for 4s (no idea if serious but it is possible now). Before it was just an inconvenience and a little lost money, now it has the potential for dramatic losses. If this and some other TP bugs are fixed, then it’s just player error when something like that happens, but with this issue, you can be tricked into selling it at the wrong amount.
The listing fee can no longer be avoided by listing an item at a lower price than the highest buy order. Items priced lower than an existing highest buy order will now be sold at the lower price. The player with the highest buy order will receive the item and be refunded any difference in price.
This is interesting, but this makes a bug that has existed for a while (possibly since beta?), become very, very serious. I will attempt to describe what happens, and hope that you can see how this is a much bigger issue now.
Example situation, but based on what really can happen, as something similar did happen to me (except the exotic was a rare, the garlic bread was real, and the situation overly dramatized to express the point, and to highlight that until this bug is fixed, this really could, and likely will, happen to someone):
You go to your inventory where you just had an exotic greatsword drop for you. You right click on it, and choose to sell on trading post. The Black Lion Trading Post window appears, but instead it shows only your inventory items, and doesn’t ‘select’ the greatsword. You think on it for a minute, and decide to keep it instead. Since the trading post window is already open, you click on ‘Garlic Bread’ from the AC run you just did, and put it up for sale for 1 silver. You don’t think anything of it, head off to Lion’s Arch.
A little later, you want to show your guild the exotic greatsword you got earlier, but instead all you find is the 1 garlic bread you are positive you sold. They tell you to check your sale history, and sure enough, you sold the greatsword outright at a buy offer… and now you take note of the name of this greatsword, that is used to make a legendary, that you just sold for 1s…
Prior to today’s update, this would just sell at the highest buy order. Now, this situation is very real. Ever since I had it happen to me with a rare, I close the window if it will not show the item, and reopen it, every time. I was not aware this bug existed just a few months ago until this happened to me (again, it was a rare so at most I was out 3 ecto and gained probably 35s).
Don’t know if it’s relevant here or it’s just me, but prior to the “first” build today I deposited collectibles in my bank, none of which showed up in bank after I restarted my client.
Hey all: The development team is currently investigating this issue and working to address it.
It would help if we had as much detail as possible regarding this bug so that we can relay that information to the team.
I was in Queensdale moving towards Shaemoor when disconnected with code 7:11:3:191:101. Logged back in to find myself back in Claypool. Started off towards Shaemoor again when disconnected. Logged back in and my character’s map completion statistic showed zero instead of 64%. Pressed ‘play’ got 2 minutes of game-time when disconnected again with the same code.
It would help if we had as much detail as possible regarding this bug so that we can relay that information to the team.
Here you go:
Right after updating the client I went to Eternal Battlegrounds and a few minutes later to Edge of the Mist: No problems at all.
Then I went killing the Harathi world boss Modnir. From there the problems started: I went to Frostgorge and got a first DC after I touched a banner. I was thrown to the char select. On Login the loading screens of Harathi and frostgourge mixed and I got to see both. Every 2 seconds it changed and took quite some time to load. I was in Harathi, without the loot of Modnir, but with the loot of his minions.
Then back to Frostgorge: Instant DC on entering the map. Game wasn’t loading char selection. After loging in back, (was now in Frostgorge) I tried queensdale just to get the same problems again. Then I closed the client and now I’m waiting
Sorry for the long text, but you asked for it :p
Error code: 7:11:3:191:101
I just did some system monitoring on my end and gw2 now eats my graphics card for no performance increase since before the update, it’s also using around 40% of my 6 core (all of them) processor.
1. System bootup
2. Character login
3. GW2 crashes
When it eats 100% of my graphics card it crashes to character select.
Attachments:
Shamelessly bumping this post, since apparently there is no in-game reason for the AC waypoint to ever be contested (nor have I ever seen it contested while in the same map myself), yet it’s contested all the time when I’m in another map.
Hardly a priority compared to some of the class-breaking bugs we have to contend with on a daily basis, but it still really annoys me that after all this time characters still glide across the ground when Blinking while running.
Back to the place where you belong, topic.