Pemberly.6305

Everyone who plays WvW regularly has an opinion about what WvW should be. This is a good thing, it means people are invested. It also means people disagree, which is okay as long as people keep the vitriol to a minimum. Alliances is meant to balance server populations, by creating pseudo-servers every 2 months. Alliances will not affect fight outcomes based on squad size, in my opinion. Big blobs will still wreck smaller groups, plain and simple. The alliance limit of 500 still allows a pseudo-server to field 4 squads (one each map) of over 70, or a map queue for each BL/EBG, for the selected time zone. This assumes that alliances are made with guilds from the same time zone, which in my experience is likely. Fight group size (5, 20 or 50) is affected by alliances. It is determined from how many players there are available for each time zone. Last I heard, alliances don't balance populations for each time zone, although I hope they will. Thus, with alliances, you can still have a server dominating one time zone, and dead the rest of the time. Players can still spend gems each re-link to play on a server that meets their needs. This is no different than today. So if alliances don't affect fight outcomes, and don't affect local population imbalances, what do they do. Alliances prevent servers from being "FULL", and so you can always spend gems to transfer your guild(alliance) to a pseudo server of your choice. In fact, you now have to do these transfers every 8 weeks, after re-link occurs. So, ANET makes more money.

I think the player stereotypes are right on. Let me add one thing. With the constant nerfing of classes (eg.scrapper) Anet has actually made the game harder to play. The margins for error are smaller. Have they gotten to the point where casual players are leaving WvW because it is too hard? My anecdotal evidence is there are fewer 40+ blobs (ally and enemy) across the time zones I play. Commanders running open tags are fewer, because the remaining pugs aren't as talented....and so on. All of this points to the demise of the casual player in WvW. I wonder if Anet has any hard data on this?

Same here, i play mainly WvW. Started last Monday, the 13th. Far worse NA EST times 8am to 5 pm. After 8pm EST the problem seems to fade away, only to return the next morning. The same issue also occurs with forums, release notes, and wiki pages, when the game is loaded and running (or trying to) I'm on Comcast from South Florida.

I assume you've seen this..... https://www.reddit.com/r/Guildwars2/comments/ex7k6n/d912pxy_dx12_for_gw2_now_v20/

https://drive.google.com/file/d/1VoRdyjkbQNTqhNcJm9_Qxv3RLBVH_iyc/view?usp=sharinghttps://drive.google.com/file/d/1RFiCYLKeAJyLaSz1oq55294cy_ARylTR/view?usp=sharing Still no improvement in API hangup issue.

I echo previous posters. PvE and $cash for gems are the way to go.Here are some powerpoint slides I made a long time ago. Warning: Some stuff may be out of date.https://drive.google.com/file/d/109X42ITl1RKCd9fiuC_qxFPLhwzQozrt/view?usp=sharinghttps://drive.google.com/file/d/1jyQe3-8bVZw4cTlrPfwqOmlEuQnl9WR7/view?usp=sharing Currently I am running the Maguuma Wastes Reward Track for the zone currency to buy clay, and make Clay Pots (1 per day) which sell for 7 gold, and take seconds to make.

Ticket #7950788

https://drive.google.com/file/d/19n4XSrBc-UissJg07Eok6quPsPLSj24F/view?usp=sharinghttps://drive.google.com/file/d/1H0qeqbhz0PWac9yfrXme2EDWxOx9kG7a/view?usp=sharingLatest Data Set: NA Reset to Monday @ Noon, 23Nov2020 No improvement in results. From now on, all results will be posted at https://sites.google.com/view/gw2-wvw-for-beginners/wvw-liveI guess I am naive in expecting Anet to fix something that is broken 25% of the time.

Somewhere in the distant past, folks complained that servers with 24/7 coverage had an advantage over servers that also had good numbers but only over a time zone such as NA-East. So, as I recall, and maybe I'm wrong, WvW was changed so that what happens over a single skirmish matters to the overall scores. Are we asking to change it back? Remember, 80% of war score is PPT.

Looking at the Gaussian distribution around 25 consecutive identical values.~ 3200 events of avg 23 entries duration times 2.2 minutes per sample = ~162,000 minutes in 48 hours.dividing by (9 matches 4 maps 3 teams * 2(kills and deaths)) 216 individual data streams.= avg 12 hours of downtime for each stream in 48 hours. So, if my math is right, 25% of the time, the WvW API is hung up and not working.I hope my math is wrong.

https://drive.google.com/file/d/1pRq1o6ZvtoV1HcJy-aG8tNKJ8iW5CuXT/view?usp=sharinghttps://drive.google.com/file/d/1xdlexlxbZapYcgZfeHJzPFVZ7ruxawbS/view?usp=sharing New Data Set: Wednesday 18Nov to Friday 20Nov.Things definitely to a step backwards for this data set.Maximum length of consecutive identical values is 107, 235 min, ~4hours, 2 skirmishes.

https://drive.google.com/file/d/1bU91QwktR7E_-_HIf4IJ9M37NXviLFjx/view?usp=sharinglatest data: Patch day to Wednesday @ Noon

I think we all use cliches in WvW, whether in Voice Comms, or in squad chat, to help rookies learn the game, or just to express frustration.Below are a few of mine. What are your favorites? Don't be a Bag, Stay on the tag.Join Voice Comms for the jokes.Have Fun. It's a game.Put away your mini.You have 2 ears, and one mouth. Listen twice as much as you talk.

New data set, NA Reset to Monday @ Noon. Things seem to be improving.... https://drive.google.com/file/d/1pn4oN43sYjLPmMPCVuNJ6hiUk-j9ug3w/view?usp=sharing https://drive.google.com/file/d/1QCAo39ietvp9aRu5iGGPAs5aQWJKjxQ-/view?usp=sharing

https://drive.google.com/file/d/1AHWrjSqAUDIewHFQaMBptqW-ZaDdYwHm/view?usp=sharingSorry, here is today's basic histogram of all the data.Still have the local minima at 15 or so, and local maxima at 27.However, the maximum number of consecutive identical values has dropped significantly. 160 -> 65!Thanks Anet!

https://drive.google.com/file/d/1bC6AB1XKoqYVlT-EAXsxsdfZk4PwQjB5/view?usp=sharingNew data set. Wednesday at Noon to Friday at Noon.Good News, the maximum number of consecutive identical values has dropped from 160 down to 65. In the plot above, we limit the data set to sequences of 25 or more consecutive identical numbers of kills. For each identified such sequence, we plot it against the number of consecutive identical deaths at that time. The takeaway is that because the resulting scatter plot is a line, whenever the sequence of kills stops being updated, the sequence of deaths also stops being updated, for the same amount of time. I think this rules out the game engine as the place where the lock up occurs, because the running list of kills and deaths are different processes in the game engine. I think that leaves either the transfer of data from the game engine to the API data base, or the API data base itself as the source of the lock up. Comments?

[snip, snip] Sounds like you want to ride the coat-tails of a full squad, comped to take on an enemy full-squad, and you sneak inand claim all the credit for the kills. Sounds like my sterotype of thieves.

I wonder if it isn't the transfer of data between the game engine, and the database that supports the API that hangs up?I'm curious.

The links were updated to reflect a new data set, Monday @ Noon, to Wednesday @ Noon. Guessing this is old news...

I think it is important to choose a server that is active during the times you play most (seems obvious in hindsight) . Tracking guild claims can be thought of as a proxy for activity. https://sites.google.com/view/gw2-wvw-for-beginners/wvw-guild-claims has plots of guild claims versus time for each of the servers.It might help you with your search.

https://sites.google.com/view/gw2-wvw-for-beginners/wvw-guild-claims Just wanted to add pictures of when servers are busy, as measured by flipping and claiming objectives.Data is from the most recent NA reset, to the update time listed at the top of the page.

Has anyone else seen this? Is it old news? I spent some time looking at the time interval between updates to the # of kills, and # of deaths, for each match, map, and team in the API. I sampled the API every 2 minutes give or take a few seconds to account for the time it takes the API to respond each time through the loop. I then step through each list of data to determine the number of consecutive identical values, and plot the results in a histogram. For example, if list_kills=[120, 122, 122, 122, 126, 134, 134, 179], list_consecutive_values= [1, 3, 1, 2, 1]. There are over 45k entries of consecutive identical values, where data was collected from Saturday @ Noon to Sunday @ 22:30 New York City time. https://drive.google.com/file/d/1hG8Z7w4YFx50uPca9UtNEi5YuhIbm1mY/view?usp=sharing The plot above shows the vast majority of API updates to the # of kills, # of deaths corresponds to 1 or 2 consecutive values, or approximately 4 minutes or less. This lines up well with the 5 minute RI timer for flipping objectives, assuming the API updates objectives status, war score, # of kills, and # of deaths at the same time. The large number of 1 consecutive values indicates that the API has the potential to update every 2 minutes, but does not always do so. Zooming in on the y-axis shows a collection of values in the 15 to 30 range. This corresponds to time intervals of 30min to 60min between updates to the API reporting # of kills and # of deaths. I cannot explain the local minima at 15, and local maxima at 27. There are two possibilities, one is map inactivity, and the second is a minimum threshold before the game engine updates the API server. It is, in my experience, not un-common for maps to be completely inactive for periods of time. This would lead to consecutive identical values of # of kills, and # of deaths, with the API being updated at regular time intervals. A second possible explanation is a minimum number of new kills, such as 5, must occur before the game engine updates the API. There are probably other explanations too, and I am interested in learning what people think. https://drive.google.com/file/d/1Q2M4RoZYv2Kd-Yyh-iriJ_mGKKlity8T/view?usp=sharing Zooming in further on the y-axis, and expanding the x-axis to max values yields the plot below. https://drive.google.com/file/d/1I8KvZY_MejXvruwd9IAKt1zt28ix4BHB/view?usp=sharing This is the plot that confuses me the most. 120 consecutive identical values corresponds to 4 hours. There is no way a map has no kills or deaths for a period of 4 hours, and so this time interval between API updates of # or kills (or deaths) has no explanation I can think of. Even 40 consecutive identical values, 80 minutes, of no kills seems very unlikely to me. Comments and Questions Welcome.Pemb.

Can anyone help me get this to work?I tried adding the latest Schema version, and an API key to no avail. https://api.guildwars2.com/v2/wvw/matches/stats/2-1/teams/green/top/kdrAny help will be appreciated

Can anyone help make this work?Adding the latest schema version, and/or api key do nothing https://api.guildwars2.com/v2/wvw/matches/stats/2-1/teams/green/top/kdr any help at all will be appreciated.

haven’t seen this mentioned, so here is my 2 coppers....This is going to kill WvW 50 on 50 fights dominated by skill lag. How can you time spell casts as required above when your servers can’t keep up? Also, what happens to players who have 300 ping? With shorter durations of channeled casts, what happens in the client when the server thinks the spell cast is over before the animation has begun? What about players whose hardware has a FPS of 25 in Zerg on Zerg fights? How can they time spells?Players in OCX and SEA time slots just got screwed. While the proposed changes may be good for sPvP, and 1v1 roamers, map queue on map queue fights are screwed.