Guild Wars 2

What does everying think about adjusting the game so that the number of points you received at the end of an hour were proportional to the number of enemies on the maps?

Points awarded at the end of a tick could be:

point value * (maximum number of enemies on during tick / maximum number of enemies on during the day).

This would greatly reduce the effect of capping objectives while the server is asleep.

Arena Net won’t change this I am afraid.

That being said, I have no clue how people enjoy spending 100% of their WvW time fighting doors and then thumping their chests with +600ppt screenshots on the forums lol.

I agree change is unlikely.

I was just thinking about the problem and trying to find a good way to address it. Capping an objective should count for something, but there’s very little skill in staying up later than everyone else.

Major downfall of WvW. They reward people for all stacking on one server. My question is, if they aren’t going to change, why did they even have EU and NA servers? They should have just mixed everyone in one pot.

This has been highlighted so many times, but as usual Anet will not agree to it until its too late, in this case death of many servers.

This is also a far bigger problem in EU than in NA as EU has just 1 timezone and even 1 server with good russian coverage(SFR now) becomes almost unbeatable. ans the same situation with NA with oceanic coverage,

I really think the points should be allocated on % basis of active wvw population rather than the usual 15 min tick which we get.

So how do you manage that. Lets say prime time is 7pm-10pm GMT.

Server A has 100 people at ‘prime time’. But only 30 from 10pm-2am
Server B has 30 people at ‘prime time’. But 100 people from 10pm-2am

Quite plausible, my server is quite like this at times. We have many from eastern EU, Australia and some Americans too. So it isn’t their fault what their prime time is, is much of EU’s night time.

How do you change the scoring in this match-up to be balanced? If you say night time for GMT is worth less points (say keeps are worth 15 instead of 25 per tick and so on), then server A will win every time, despite being guilty just as much of playing in server B’s off-peak hours.

If you simply change the score system to be proportional to the number of enemy players online, first that is a pain due to having a 3 way match-up and second, you made 0 impact on the end result in the above scenario.

In that case, I would say that over a 24 period (previous 24 hours???) Server A has a max of 100, Server B has a max of 100. So the denominator for each is 100.

Assume that capping something is worth 25 points.

During “Prime time”, Server A gains 30/100 * 25 (or 7.5) for anything capped, server B gains 100/100 * 25 (or 25) during prime time. From 10pm to 2am the values are reversed.

My thought was that the number of enemies would be equal to the enemies from server A and server B combined, for both the numerator and denominator.

Of course, any suggestion would have to be fair to everyone.

Edit: of course you raise an interesting point, because the combined point value for that match would be diminished. This could mess up rankings. I’ll have to think about that.

Rankings should be gotten rid off. Every week just totally randomize the fights. After all the mists is supposed to be an every changing series of connections with other worlds. How do we get the mist feel when we see the same people for months?

You’ll see the populations spread out when there is no longer any rankings to fight for.

However, rankings should be based on points/active wvw population. As many of the current tier 1 would be incapable of putting up a proper fight if they have to go 30v30 with the lowest tiers. Back when we could freely swap servers, I jumped to the lowest tiers just to get a feel for different wvw situations, they are much tighter down there than in the upper tiers. The upper tier solution to EVERYTHING is throwing more people at it…it gets old fast, but I’m happy where I’ve always been on TC…a lil bit o everythign gets tried on TC.