Pemberly.6305
-
Posts
30 -
Joined
-
Last visited
Content Type
Forums
Events
Articles
Gallery
Posts posted by Pemberly.6305
-
-
-
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=sharing
https://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=sharing
https://drive.google.com/file/d/1H0qeqbhz0PWac9yfrXme2EDWxOx9kG7a/view?usp=sharing
Latest 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-live
I 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=sharing
https://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=sharing
latest 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=sharing
Sorry, 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=sharing
New 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]
> > > running an all thief guild, trying to get a decent server for bag farms and zerg busts
> Everyone here is SEA time but i just cant find a good wvw server for bag farming.
>I want to work with skilled guilds as an arrangement.
Sounds like you want to ride the coat-tails of a full squad, comped to take on an enemy full-squad, and you sneak in
and claim all the credit for the kills. Sounds like my sterotype of thieves.
-
> @"Dayra.7405" said:
> Hm, it's known:...**[snip, snip]** .... and I think it's the API and it hangs
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/kdr
Any 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.
-
>
> ### Cooldowns and Durations
> We want cooldowns to be felt. Longer cooldowns promote more calculated usage of skills; if skills are used poorly it should create an opportunity for the enemy to push their advantage. Shorter durations of high impact buffs have a similar effect. Skillful timing is going to be rewarded, and poor usage is going to be exploitable by enemies. In some cases, it’s still going to make sense to have a longer duration attached to a longer cooldown, but most of the time we’re looking at shorter durations for things like stability, protection, quickness, high might stacks, among others.
>
> ### Instant Skills and Passive Traits
> Counterplay is important. Skills that have a major impact on an enemy player should allow that player the opportunity to react, which means that we want to avoid instant skills that do large amounts of damage or hard cc. In general, this means that instant skills are going to deal less damage or focus more on a secondary effect where applicable. Traits that fire instant skills, or that trigger an offensive effect under easy to fulfill conditions (on hit, on crit, mid-high health threshold, etc.) received similar considerations.
>
> We’ve also done a pass on traits that provide automatic defensive triggers. Traits that negate incoming CC or grant hard damage mitigation are getting large cooldown increases. Lesser defensive procs (protection on cc, auto condition cleanse, etc.) are also receiving longer cooldowns or reduced effectiveness, though not as extreme. We want to promote more active gameplay and this update is a good opportunity to make heavier adjustments to these passive traits.
>
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.
-
With the Jan 2019 patch (lw4e5) , T4 PUG fractals in my time zone (New York) have dropped off 50% or more.
I speculate this is due to the Mistlock Instability changes.
So, unless you have a steady group of a balanced 5, farming T4 for Gold has gotten much harder.
Current DirectX versions
in API Development
Posted
I assume you've seen this.....