Guild Wars 2

Hello everyone.

As it has already been stated before, this practice is of course not related to any specific server and generalisations about this should not be made, for obvious reasons. Having this in mind, we proceed to close the thread.

Thanks for your understanding.

Hello everyone.

Thank you for all your answers and contributions. Since the question has been solved already, we proceed to close the thread. Thanks again.

Hello everyone.

Thank you very much indeed for your contributions. Since the question is already solved, we proceed to close the thread. Thanks again!

Hello there, Lalance.

I am sure that the community will help you with other useful links about it, but I would suggest you to start by the GW2 Wiki article on crafting, as you will find direct info about disciplines, materials, crafting locations, and so on.

Have fun!

Thanks for letting us know, Raccoon. Since this is not longer a bug report, we proceed to close the thread. See you in Tyria!

Hello everyone.

Umut, yes, the team is aware of this botting issue since you guys started reporting it. We see that it is harder to report this kind of fellows because of the teleporting but nevertheless we would encourage you to keep on reporting them through the in-game reporting tools (you can also send screenshots to Customer Support via a ticket).

Thank you very much.

Gaile Gray.6028:

I believe that we will be offering name changes in the Gem Store sometime in the future. Hold tight and you will be able to change that name.

There you have, Bree Lynn. We understand the feelings that come along with waiting but I am afraid we cannot say more at this point. Should a change about this arrives to the game, we will keep you all dutifully informed.

We proceed to close the thread now.
Thanks for your understanding.

Hello everyone.

As AwwGee has pointed out, we would like you to report those PMs you get, as the denounces get directly to us and we can act accordingly. Regarding the other issue: rest assured that once your case is cleared, your account will get back to you but you need to be a little bit patient. As indicated before, if you do not get an answer in thee or four days, then proceed to post the reference number in that sticky thread.

Thanks.

Hey there, Nithix.

You friend needs to file a ticket with Customer Support, clic here, detailing all the possible information he has about his account, like e-mail account associated, serial code, etc. They are the ones who can help him regaining the access to the game again.

Hello everyone.

Yes, the team is aware of the presence of bots in WvW as well and fighting against them since the beginning as a priority. We would like to ask you to keep on reporting those fellows as soon as you see them, through the in-game reporting tools (screenshots and vids to Customer Support are also a possibility) as this helps us effectively.

Thanks for your reports and your patience. It´s greatly appreciated.

I won’t be at the office until Monday, but I’ll check it out.

Other than [Group] events, they all scale for 1-10 players. We’re also looking at scaling past that for world bosses and Orr megaevents, but that will take time. If there’s an event that you’re convinced isn’t scaling, please post the name and location and I’ll look at it. I know I’ve solo’d all of the Wayfarer Foothills events that I worked on.

Hi all, I think a little more explanation is in order.

First, let’s call the culling system that we’re switching to “affinity culling” just to make it easier to talk about. Under affinity culling the system handles enemies and allies independently. This means that the maximum number of allies that you can see under affinity culling is 1/2 the maximum number of characters (combined enemy & ally) that you could see under the original culling. Ditto for enemies. In exchange for that cost he benefit that we get is that running with (or through, or past) a large group of allies (e.g. a guild) won’t prevent you from seeing the enemies who are closest to you.

During the initial trial of affinity culling we found that a number of players reported asset loading issues that were highlighted by culling. Any time that your client is aware of another character at all (dot on the map, targetable in world, nameplate is visible, etc.) then culling is no longer a factor because that character has already been reported to your client. In that case if you can’t see the character the issue is one of asset load time. The fallback model feature which is shipping this month directly addresses those issues by providing a cached model to show immediately when the character is reported to the client.

The order of operations looks like this:
1) Character X enters player’s visibility
2) <delay due to the mechanics of culling>
3) Server reports character X to client
4) <delay due to asset load time>
5) Character X full model is visible on-screen to the player

Using fallback models we end up with this instead
1) Character X enters player’s visibility
2) <delay due to the mechanics of culling>
3) Server reports character X to client
4a) Character X fallback model is visible on-screen to the player
4b) <delay due to asset load time>
5) Character X full model is visible on-screen to the player

As you can see we’ve made the asset load delay unimportant (or at least less important) and allowed the player to be aware of character X sooner (in some cases quite a bit sooner).

The combination of affinity culling and fallback models provides a better experience than affinity culling alone. Even so, the affinity culling is not intended to be our last change to the system, but rather to hold players over until we can make more extensive updates to the system (which take time to implement and test). In future updates we’ll be making changes in an effort to eliminate the delay due to culling (step 2 above) and to tell each client about character X as soon as the server decides they have become visible again. We hope to do this by removing culling completely and preserving client performance though a mix of network and engine optimizations, the more extensive use of fallback models, and sundry wizardry.

As I’ve said in the past our ultimate goal is to remove culling and we’re pushing hard to make that happen. This update represents the first steps in that direction and much of what it accomplishes is to lay the groundwork for our upcoming updates. The next few months are an exciting time for us on the WvW team and we’re very excited about the changes are coming.

It’s not an issue of the Test sever having different data, it’s not being able to determine how the event got in a bad state. When you expose an event chain to hundreds of thousands of players, one of them might do something you didn’t think was possible and/or didn’t account for. I’ve played this chain dozens of times and haven’t found a way to break it, so I’m just trying to make it as error-proof as I can. In the short term, it sounds like the server resets are at least restarting the chain.

Sypsy.7318:

Will there be an option to keep enemies (and even allies) as fallback models?

For people with lower specced machines or bandwidth limitations, it could increase performance? It could also just be a preference, since having a model “update” could be distracting while trying to track them.

That capability isn’t part of the January update but in future updates we’ll be using fallback models more extensively to help with performance in high population scenarios. The fallback models are cheaper in a number of ways including poly count, texture size, and animation count & complexity. I don’t think it would be visually satisfying to have nothing but fallback models on the screen but we’re definitely exploring the right balance. You will see these additional changes related to fallback models in the coming months.

I’m not currently aware of any behavior that I would classify as an exploit.

GW2’s TP is by a wide margin less effectively manipulated than the other games mentioned in this thread.

We’re actively working on it, but without being able to determine HOW it broke, it’s a tricky process. Without a way to reproduce the issue on a test server, I can’t be sure that the fix is good. Also, note that actual “content” updates are on a monthly schedule at the moment, so if an issue isn’t fixed immediately, it doesn’t mean that we don’t know or care about the bug, but we need time to run new fixes through testing before it goes live. (And there is lead time, so anything I fixed right now wouldn’t make it into the January update.) I’m not all bad news, though. I’ve added some safety checks to these events to make them more reliable, but unless I can repro the bug to test my fix, I can’t provide an accurate ETA.

Hello everybody,
please refer to the existing topics to discuss this issue.
Many thanks!

Kingfisher.7213:

There was a recent Game Developers’ Conference video, which came out about 4 days ago, where ArenaNet discussed their writing experiences/challenges in Guild Wars 2:

http://www.gamasutra.com/view/news/185077/Video_Crafting_the_25_million_words_of_Guild_Wars_2.php#.UP9nI32YNok

The video is an hour long, and it talks about the writing structures they had, as well as how it will likely change going forward.

ArenaNet mentioned they had two writing teams.

One team consisted of two people, the “Loremasters”, and they were responsible for the Personal Story, Dungeons, and Cutscenes.

The second team seemed to have pretty much everyone else, and they were responsible for writing everything else, e.g. the dialogues in Dynamic Events, dialogues we had with NPC’s, and the background converstations we heard NPC’s have with each other across Tyria.

So it sounds like for the story arcs (Personal Story), it wasn’t lots of different writers doing different bits of the story. It sounds like 2 loremasters were working on it.

The video is interesting to watch because ArenaNet is speaking candidly to fellow peers in their field. They made lots of mistakes, but they learned some lessons from them.

The writing team has reorganized since launch to address some of the challenges Angel and I mentioned in that GDC presentation. Here’s a basic view of the current structure of GW2 writing:

Lead Writer – responsible for overall quality and direction of:

• Narrative Design (formerly Lore & Continuity Design)
• Writing (VO dialogue, non-VO text, UI, etc.)
• Editing (copy editing, script preparation, casting support, etc.)

As long as you have a claim ticket, Evon Gnashblade will still be willing to exchange it. Feel free to hang onto it a little longer.

Hello everyone.

We understand that it is pretty much frustrating but rest assured that the team is taking this issue very seriously. Please, whenever you receive this kind of messages proceed to report them immediately so we can act accordingly.

Thanks for your reports and your patience, it´s very much appreciated.

arrownin.3128:

Oops this is supposed to be in the suggestion forums, that’s what happens when you have too many tabs open ;\

No problem when the mod team is nearby.

I’m aware of this issue, and keeping track of it.

Hello there.

This topic has been widely discussed here already and there are still threads popping out in the Suggestion subforum from time to time so we would kindly request you to search for them and contribute with your thoughts there in order to avoid duplicates of the same topic.

Thanks for your understanding.

Krakah, no, the behavior that you’re describing is the server culling which characters get reported to your client. This update doesn’t eliminate that, though it biases the algorithm such that being surrounded by allies won’t cause you to be unable to see any enemies (and vice versa). Disabling culling entirely is something that we’re working on still and this update lays some of the groundwork we need to do that.

Hello Cynikh.

First of all, welcome to Tyria and the official forums!! Indeed, we used to offer a “Invite a friend” feature during the Lost Shores event, that too place in November. At the moment we cannot really say whether we will be offering this in the future. If this comes up again we will let the community know through out official channels.

In the January update we’ll be making a couple of preliminary changes to WvW.
1. The first of our engine changes will be coming on line to help improve character load times by using fallback models.
2. We’ll be switching over to the culling methodology that we trialed in December.

The engine change we’re making uses fallback models to represent characters until their detailed models are fully loaded. The fallback models are cached so that they can display without any asset load delay and there is a distinct fallback model for each race/gender/armor-class combination. As a result of this change players will be able to see characters represented as fallback models as soon as those characters are reported to the client. Once the specific, detailed model for a given character is completely loaded from disk the fallback model will be replaced with the detailed model. This visual compromise will help to ensure that players see other characters as quickly as possible in WvW. Please note that this change does not eliminate delays due to culling, it only addresses delays due to asset load times. Players on higher spec machines would therefore expect to see fallback models less often than players on lower spec machines. This change also lays the groundwork for more extensive uses of fallback models in future updates.

In December we ran a one matchup trial of an updated culling system. Based on all the feedback we received, both during and after the trial, we will be transitioning to the updated culling system that we used in the trial. This update allows the culling system to handle allies and enemies separately so that being surrounded by a group of allies will not impact the culling of enemies (and vice-versa). The general consensus after the trial is that this system lead to a better player experience in WvW. We further saw that some of the issues people had with the new system were related to asset load times rather than culling issues so making this change in combination with our character loading improvements should lead to an improved overall experience. It is important to note, however, that while we believe this change is an improvement to the WvW experience it does not fully address the issues with culling and we are still working towards our goal of removing culling from WvW completely. This change is intended to give players an improved WvW experience while we continue work on our more comprehensive solution.

While this update only contains a couple of visible changes to WvW it lays a lot of important groundwork for future updates. We have some exciting changes coming and this update is just the beginning!

Hello to both of you.

Thanks for that answer, JayMack. Since the question has been answered, we proceed to close the thread.

Hello everyone.

Thanks for that answer, Zaxares. Since the question is already solved, we proceed to close the thread.

Hey there,

thanks, Khisanth, for that quick answer. Since the question is already answered, we proceed to close the thread.

DejaVuGurl.8023:

EDIT: After some time and thinking, I have realized that this is purely my fault and ANET shouldn’t have to reimburse me. I just got really upset when it happened and kind of overreacted.

No problem, DejaVuGurl. The only thing is, try not to make ANet call-outs in your thread titles as this is against our code of conduct. We would like to thank all of you guys for your contributions up to this point and since the situation seems to be solved, we proceed to close the thread.

Thanks again for your understanding.

Hello Grezko.

No, it is not a mistake. The team is aware of this issue and encouraging the players to select the Botting tab when reporting with the in-game reporting tools. Another alternative way you can use is to take a screenshot and attach it with a ticket to our Customer Support. Either way helps us.

Thanks for your reports. They are greatly appreciated.

Hello Xemnes.

Glad that it got finally resolved for you. We will pass today this info to the team anyway and proceed now to close the thread.

Hello everyone.

Since the problem has been resolved and this is not a bug report any more, we proceed to close the thread. Thanks for your answer, Mira.

Hello everyone.

Vadiana, as Mespilia says, most of the times this is a temporal issue that gets resolved after restarting the client again. Other times it is due to maintenance procedures and it is also temporary. Please, whenever you encounter this bug, exist and start the game again. If this does not solve the problem, then proceed to write a ticket to Customer Support to inform them about this.

Thanks.

Alathon.8451:

My post “Am I blocked from playing with my WvW guild?” was moved from the general forum to WvW forum; when it was moved, the Q/A mode was removed from it.

Link: https://forum-en.gw2archive.eu/forum/pvp/wuvwuv/Am-I-blocked-from-playing-with-my-WvW-guild

I have added the Q/A back to your post, sorry that this was over looked when the post was moved

Thank you Drizzzle for taking the time to post your kind words here. It’s really appreciated!

We’ll now close this thread as the problem is solved.

Hello everyone,

Even if the topic of this thread could have been constructive, we’ll now close it as this thread is derailing into off topic discussions.

Also, we would like to remind you that the comparison between GW2 and other games is accepted as long as it’s to support your opinion or argumentation. However, opening a thread dedicated to this kind of comparisons has to be avoided as most of the time it derails into off topic, unconstructive exchanges etc…

Thanks!

What exactly is your current objective?

https://forum-en.gw2archive.eu/forum/support/bugs/FPS-drop-to-10-in-Bandithaunt-Caverns/1257685

I play all the story steps as a thief, designed to be able to solo veterans. It’s based on the build I use for my Live thief to tackle skill challenges. (And for lower levels, I make sure I’m not using traits/skills I wouldn’t have access to, and I actually set my level down, I’m not using a downscaled L80.) Not all builds are going to work in all cases, we simply can’t make every story step work for all possible builds. In general, survivability > glass cannon.

Sorry, I don’t know an ETA for this feature. I do know it is still planned in the future.

If a second player runs up and hits the champion once while you’re fighting it, does that mean you’ve been griefed?

Hiooih.4603:

Hi Gaile, I told my friend that he would have to make a new account however when he attempted to use the second serial code he bought to register (which he paid for and the charge was not denied like how the account was terminated in the first place) And it gave him the error “Serial code already registered” when he entered it in. In your reply I was under the impression that the account is banned as the first serial code is no longer valid and he should make a new account and the second code would work. I’m not sure how your systems would say that two codes would be registered to the banned account. Can you see about releasing the second code that was purchased or refunding the money? The order number is 31099385 for you to look it up.

This is something that your friend needs to continue to discuss with Support. It sounds like something they’ll need to research from the codes on up.

Amazing work, klhyatt!

Do you have “Fast cast ground targeting” turned on in options? If so, it’s trying to use the mouse cursor as your target, and depending on where you have the cursor, it might not be a valid target.

Shwaz.1548:

Thanks. Resolved. I apologize for my attitude, just frustration.

Really glad that you were helped and are enjoying the game. I certainly understand the frustration, and thank you for updating!

yamz.5897:

So I pay 100 dollars for this game here in Australia, Download it, register, input my details and no go… your game isn’t broken is it? Some assistance would be much appreciated.

Nope, the game is just fine. We want to help so please contact Support by filing a ticket through the “Ask a Question” tab on that linked page. They will be able to assist you. For tips on what information to provide in a ticket, please read this post.

Oh sorry, I misunderstood. No, in-game reports will not help this situation. It needs to be documented in a ticket. (I don’t even know that there’s a reason code for errors with in-game mail in the drop down for in-game reports.)

If you could kindly contact Support by filing a ticket through the “Ask a Question” tab on that linked page, we’d like to look at this situation and assist you. For tips on what information to provide in a ticket, please read this post.