Guild Wars 2

Hello,

We’re sorry for the inconvenience. Please take a look at this thread for helpful tips on how to use the Google Search feature.

Uh oh. Better edit.

Hey, quaggans have to eat, right? I figure there’s a high cost for serving them their tasty morsels.

Oh Snapalope.1378:

Shadelang.3012:

Oh Snapalope.1378:

I’ll explain the lopsided games.

“Beginning with Season 2, matchmaking for Ranked matches will use your placement in your current league division as your primary matchmaking consideration and pair you against players who are placed in the same point range as you, regardless of the skill level (MMR) of the other people in that point range."

This is what they said how the season 2 MM system will work.

So actually to clarify something and please correct me if I’m misreading. The way the system currently works is it only considers MMR on your own team and not the full 10 players. So let’s say there’s 10 people queuing within an acceptable division range, 5 players are around 800 MMR and the other 5 are around 1000 MMR. Due to the fact that the system only considers making a team of 5 of similar MMR players at a time, the 5 800 MMR players will be put on one team and the 5 1000 MMR players will be on the other team. So what you get is high skilled players on 1 team and less skilled players on the other. Of course the result is the 800 MMR team getting stomped.

The result is you will never get a balanced team vs. balanced team like a team of 2 1500 MMR players + 3 800 MMR players vs. 2 1500 MMR players + 3 800 MMR players.

But with all said, I prefer the balanced team vs balanced team setup more.

The thing is eventually the teams will end up balanced. Or atleast so close it won’t matter. As different teams will progress at different rates. The 800mmr people SHOULD start fighting other 800mmr (or close) becuase they will be the only ones in range.

Atleast thats how I have understood it.

Eventually it will work out yes you are correct. As the 800 MMR people will be the only ones in the suitable division range so 800 MMR vs 800 MMR games will happen. The question is how long will that take though and if it takes too long is this system worth it as you’ll be playing lopsided games for a while. Another thing I’m wondering about is the decreasing player population amplifying this as well.

These are all good explanations (and questions) :]

The collection of sales tax is not something that we control. As pointed out in this and other threads, our billing provider is required by law to collect a form of tax (sales, VAT, whatever it may be called or however it is defined) for gem purchases.

You may research the “where and why” of this issue on these resources:

http://www.nolo.com/legal-encyclopedia/50-state-guide-internet-sales-tax-laws.html
https://en.wikipedia.org/wiki/Sales_tax
https://en.wikipedia.org/wiki/Streamlined_Sales_Tax_Project

As mentioned on today’s Guild Chat, the second wing of our first raid will be released on Tuesday, March 8th. You’ve seen the Slothasor. Join the new raid wing on March 8th to see what other surprises are coming your way!

I apologize that forum members and those who are impacted by this bug did not receive an update earlier. I can appreciate that a situation like this is a cause for concern!

You can rest assured that this bug is on the Bugs List that is routed on a regular basis to the dev team. Particularly because of the nature of this situation, I feel sure it’s safe to say it will be given a very focused look and will be addressed as soon as possible.

Takina.1739:

I have now sent PM to

Branden Gee
Ray Patrick
Cameron Rich
Gaile Gray
Jon Olson Mark
Ester Sauter

the PM reads exactly this

Title: This deserves a response
body: Today
[BUG]Characters are Stuttering

So now everyone on this tread knows that those 6 ANET people have been personally made aware of the situation, and that I was nice, if blunt in my informing them.

Lets see if we get anywhere now…

And PMing about a bug is entirely inappropriate. Please do not spam members of the ArenaNet Team to ask for attention to an issue brought up in a forum thread. We have several people in the forums daily, and this thread has been noted and is being investigated. When we have more to share, we will do so.

Again, please do not use the PM system to call attention to your thread. That is an abuse of the PM system, as most likely none of the people you’re distracting with such messages are going to be able to address it directly, and the people who are involved will be made aware through the forums themselves.

I would recommend switching to the 64-bit client.

Ghorman.1368:

Jon – did you get what you needed?

Yes, that helps tie things together. Unfortunately, the details don’t help much in telling us what actually caused it in this case.

Also, Melanion, if you/your friend could post her ticket number(s), we’ll look into the Support end of things and make sure Matthew gets any files that she’s already sent.

That is an interesting suggestion. Who else would you like to see as returning heroes in stronghold?

SmartBobby.6283:

Thank you! Ah cool, I will use the GitHub issue tracker next time.

Whichever’s easier for y’all, it’s no biggie having reports on both. I just like having everything in Github so I can have a kanban-style interface for tracking the million things that need to be done.

Huh, that’s not good. Looking into it now; here’s a tracking issue.

IWN makes a good point: I found myself muttering “Where ma loot” last night after another boss encounter. Sure enough, I was getting the goods, I just didn’t note it at the proper time. Earlier this week, I had taken out the same boss in <24 hours (not a factor with all bosses, but a general statement of how some work) and therefore wasn’t entitled to the chest. So stuff sometimes happens and it’s not always a bug.

However, I’m not discounting your report, Ashantara. A ticket would be the best way to communicate this issue, so that a CS agent can look into the matter with you.

Teutos.8620:

My teammate who left the game was NOT a part member.

Still lost a pip. Problem NOT solved.

Edit: Next time the problem happens again, I will make my own thread (with the exact documentation which match it was), seems posting in the same thread get’s you completely ignored.

If this is still happening to you, and it turns out that your situation isn’t the same as ZilentNight’s (where the player that disconnected in your match was also a party member), then I encourage to please either return here or definitely make another post so that we can continue to investigate things further. While ZilentNight’s situation was resolved by getting additional information pertaining to that specific match, if you find that this is still happening to you (or anyone else for that matter), then please don’t hesitate to let us know, as we have no intention of ignoring players if this seems to be an actual recurring issue with Season 2.

Zilent — if you’re the one who updated the thread title to add “resolved” I want to give you a huge “thank you!” It really helps forum members to see those notes, so kudos for the helpful update.

Hi Generix,

I’m sorry to hear this problem is affecting you!

For what it’s worth, this is a known issue that we’re investigating. When we have a solution I’ll be sure to follow up with you and see if it’s fixed the problem.

Was the teammate that left in your party?

Thanks for the reports everyone. I suspect this is still a latency issue. After seeing this behavior, can you try waiting ~5 minutes to see if your main league UI updates and the game shows up in your match history?

Unfortunately, even the most well-intentioned temporary fixes can introduce more issues than they solve, as they typically result in even more convoluted workarounds in content that can have compounding “knock on” effects we might not discover until they go live (which is a big part of why players are now stuck in Chpater 7 of the personal story).

Consistent crashes like the one you’re reporting here on behalf of your friend sound like some sort of hardware issue and are more than likely unrelated to content. I can’t be certain of that fact, but this is the first I’m seeing or hearing of such consistent crashes in that instance – we’ve definitely not experienced it internally (and I’ve run it through with two of my Live characters). Most of the issues surrounding that instance have been related to the phases not always getting set/reset properly, gadget states on things like the floor pieces and updrafts not always reporting correctly, etc. We’ve tried to address almost all the issues we can, but the crashes are definitely not a common occurrence, or we would have seen some bugs come to us on it. If this is still an issue, let me know with more specific details about WHEN these crashes occur.

Hey everyone -

We do in fact care very much about your personal story experience, and we have made concerted attempts to fix these issues in the past, but unfortunately it would appear that there’s not a “one size fits all” solution. Compounding this problem is that there’s not an easy way for us to replicate the issues in order to diagnose all of the problems players have reported on the forums.

However, despite my saying that, blockers like these are an inexcusable error on our part, and we are looking at ways to solve these problems for everyone. Please accept my deepest apologies for the blocking issues, and we appreciate your continuing patience as we work to resolve the blockages as soon as possible.

Could you post your crash details?

@Shadow Dragon.1469, looks like you are unstuck now (probably from when I cleared someone else in your party).

@TwistedFate.8705, you should be unstuck now.

I’ve unstuck all of the people in this thread. If you didn’t see pips awarded you should be them after the next game you play.

Thanks,
Ray

@rhonda berenne.8573, you are unstuck now.

@GreyFeathers.8175 — Thank you.

@GreyFeathers.8175, you are unstuck now.

I’ve freed all of the people in this thread so far.

Thanks,
Ray

@SilentKill.9586 you should be good to go now.

@Caredelth, you should be fixed now.

@OlrunTheBlade – you should be unstuck now.

Just thought of something: Those of you reporting, if you can share your region and your world/server, that may help in the analysis.

Thanks.

I’ve reported this to QA and to the PvP Team. I feel that they will be able to analyze this and define what’s happening.

Thank you for the reports.

LDJ Nine.2047:

The players that purchased these will get refunds, correct? I purchased Vigilant yesterday. >.>

Yes you will be refunded your gold.

A message from the PvP Team:

The Vigilant and Crusader amulet were removed today. We had intended to remove these amulets with yesterday’s kick off to Season 2 but a bug prevented that change from going through. Here is what we previously stated, which still holds true:

“We removed several PvP amulets from rotation because they pushed gameplay in a direction that we weren’t happy with. These amulets were then replaced with four new four-stat amulets, none of which has either Toughness or Vitality as a primary stat.”

We currently have no plans for any additional changes to amulets for Season 2 (including removals or additions), but we will continue to monitor amulet use in relation to the state of PvP throughout this season and may make other changes to amulets for future seasons as needed.

Bug Fixes:

• Removed two amulets from PvP, the Vigilant Amulet and Crusader Amulet.
• Fixed a client crash.
• Fixed a server crash.
• Fixed a bug in which the player’s position would not save correctly when players transitioned between map versions or logged out.
• Fixed a bug that prevented LFG descriptions from being updated on initial posting.
• Fixed a bug that caused the LFG search bar to overlap the Refresh button.

Late Notes:

World Polish
Southsun Cove

• The “Reclaim the settlement by burning out the karka nests” event now broadcasts correctly to the area indicated by the world map event circle.

Fireheart Rise

• Fixed a bug that blocked progress in the “Defeat Scaldmaw of the Flame Legion to gain the help of the grawl” event.

Dry Top

• Rare boss events have had their spawn cycle updated.
  • Five minutes into each dust storm, one of the rare bosses will spawn with a map-wide marker.
  • The five bosses spawn one at a time in a set, repeating the rotation of Sol Eater, Sand Savage, Bloodscale, Grit, and Dune Soarer.

Profession Skills
Ranger

• Spike Barrage (Bristleback Pet F2 skill): Reduced the damage of this skill by 25%.

Necromancer—Reaper

• Deathly Chill: Reduced the condition damage multiplier for this trait by 15%.

Aha! We aren’t ignoring you, but we couldn’t determine a repro until very recently. A fix is in testing, but I don’t have an ETA for when it will reach the live servers.

Long winded explanation:
Basically, there are several dwarven relics scattered across the lake, only one of which is the item you’re looking for. If you pick up 6 relics without finding the scabbard, it will mark it and update the objective to “Pick up the scabbard.” If one of the relics you picked up was the scabbard it would complete the search and move on to the “Escape with the scabbard” step. BUT… If you got close to the scabbard (without picking it up) it would mark the search as complete, but not advance to the “Pick up the scabbard” step. You can swim around and interact with the relics and eventually you’ll find the scabbard, but since it’s not marked it’s very hard to find.

I’ve fixed it so the “Pick up the scabbard” step (and a marker on the scabbard) will correctly appear when you get close to it. This is also why we had such a hard time reproducing it—you have to get close to the scabbard but not have picked up 6 relics in the mean time. Since it randomly changes spawn positions, it’s a matter of luck.

Our Server Team will be doing maintenance tonight (24 February) starting at 9:00 PM Pacific time (-8 UTC). The maintenance period is expected to last up to four hours. We do not anticipate any significant impact on the game, but a few players may experience intermittent disconnects.

Thank you for your understanding.

My Slothasor experiences so far.

OK so we all know the plan. I mean what could possibly go wrong? Charge!!!!!
(grinding, rending noise)
Well, yes now you think it through it’s pretty obvious that could happen!
(burning, gurgling, sobbing sounds)
I’ll be honest, I didn’t see that coming!
(exploding, wheezing, soft whimpering noises)
I want my mommy

Seriously though, I think you will enjoy the challenge.

Ok, I admit it. I really did lol.

And yes, you were very inclusive, covering all types of players. Well played!

Mosferre.1246:

“Get Her!”

That’s your entire strategy?

@tekknotroll – looks like you and your team members aren’t stuck any more.

We are aware of a couple of issues and have fixes identified. Stay tuned.

@jetwing – you should be good to go now.

Ray

Hi all,

Due to a scheduling conflict, the Challenger Cup will now be taking place on Sunday, March 6, 2016 for both Europe and North America. My sincere apologies for the late notice.

• The European Cup will begin at 9am Pacific (17:00 GMT).
• The North American Cup will begin at 4pm Pacific.

I will be reaching out to team captains next week with additional details.

@Ace, from what I can tell you aren’t stuck anymore. Please let me know if this isn’t the case.

Ray

So, time for a dose of honesty.

This account was blocked because both the display name and character names are obviously disallowed. The account also has chat showing repeated use of “Sig Heil”.

At the time of the block, the account was free-to-play and it is our policy to block ‘troll accounts’. The account has since been upgraded and is being allowed name changes in exchange for returned game access.

atalexsutter.9360:

Do you know how high can these numbers get?

In the database they’re stored as a bigint (maximum 2^63), but since we’re serializing to JSON the API will break after they exceed 2^52 (because JSON encodes numbers as IEEE 754 doubles, that’s the maximum integer that can be exactly represented). So storing them as a 64-bit integer on your side should be safe.

I think that was a cache issue — the daily achievements are automatically whitelisted (they bypass the normal manual approval). The master list of whitelisted achievements was probably just cached for a while after reset (it’s got a fairly long cache duration since it only updates once/day at most — since usually it’s a manual process).

IIRC this happened because there were new dailies released yesterday, so this shouldn’t happen too frequently.