Guild Wars 2

Wouldn’t seem more fair for everyone if the portal could only drop once per account?

EDIT: (Like once your account gets beta access that your account becomes disqualified from further portal drops)

Having it drop like any other rare item feeds the multiple rng conspiracies floating around and it is flat out disheartening for those players who believe them to any degree.

It’s not like there’s a finite pool of portals. Unless that’s your choice of conspiracy.

And really, doing anything to make “those players who believe them” happy would be bad.

Even if 1 person gets 500 portals it doesn’t mean you get less of them.

Olba.5376:

It’s not like there’s a finite pool of portals. Unless that’s your choice of conspiracy.

And really, doing anything to make “those players who believe them” happy would be bad.

It isn’t going to make them happy more so than not kitten them off as much. Because they’ll most likely start thinking “Well those players are done with their hunt. Guess its my turn now.” which is better than “Lovely RNG system giving all the good stuff to the 1%! **** HoT”

How about this for an idea – have it set so that after “x number” of kills or events the portal is set to drop guaranteed for the player, but not to let the player base know this – so it is still thought of as random – that way those who are committed and show dedication and effort to obtain one would get it and be rewarded and not feel demoralized and destroyed at wasted efforts – but still have the impression its a random drop. so it not like they are aware of having to do it x number of times.

And if more players are ‘dedicated’ than the Beta can accommodate? What then? A random drawing from the pool of those that got the drop? Back to square one, I’d fear.

I would say that anet have an idea of the number they want for the beta test – once that number is reached then stop the event – maybe not set a time limit initially. that way players are in the clear about when it would drop and not waste effort once its finished

It should also be noted that, multiple portal drops on one account would not effect anets idea number. Its not like, if there were 5 spots, and I got 4 portals, and one random person got 1, that it would just be me and them in the beta.

I don’t think anet has a set number for the closed beta. I do think that they did it this way purposefully but what purpose that is is up in the air.

yolo swaggins.2570:

I don’t think anet has a set number for the closed beta.

Of course they do. They know how many players their test server can accommodate, they know how many beta testers they need, so they will do what they can to attain a number close to that, give or take a few.

That’s why they increased the drop rate after a day they started the event. They saw that with the drop rate they put at start they would not get the number of beta testers they wanted.

The drop rate could again be modified up or down if they see there are too many or too few drop before the event’s end.

And if players keep getting multiples there is a chance they are not going to get their numbers either. That’s why I suggested the lock out.

They can determine how many different players got portals. If one has more than one portal, it won’t kitten up Anet’s statistics.

Thanathos.2063:

They can determine how many different players got portals. If one has more than one portal, it won’t kitten up Anet’s statistics.

Locking the portal drops to 1 per account is not going to change that.

Sure, but it hasn’t any valuable effect. You can’t even look into other player’s inventory, so there’s not even an indirect effect.

yolo swaggins.2570:

Locking the portal drops to 1 per account is not going to change that.

That would require to add unrequired coding to the game,, test it to be sure it does not bug, pay employees to do all that, employees that can be more useful working on something else (like the expansion, for example)

As they did it, they simply had to add an item to the drop tables. The system is know to work without bug since more than two years, and it requires no further coding and testing.

Blanche Neige.7241:

yolo swaggins.2570:

Locking the portal drops to 1 per account is not going to change that.

That would require to add unrequired coding to the game,, test it to be sure it does not bug, pay employees to do all that, employees that can be more useful working on something else (like the expansion, for example)

As they did it, they simply had to add an item to the drop tables. The system is know to work without bug since more than two years, and it requires no further coding and testing.

Exaggeration. You know how easy it is to put a switch like that into the game? Its a single item interacting with coding that can be blanketed.

- Add a value to accounts. Value can either be 1 or 0. Value default is at 1.
- Add a conditional statement that changes the value of the account value from 1 to 0 when the account becomes officially flagged for beta.
- Add another conditional statement to the portal item where account’s portal droprate = account value(original droprate of portal)
- Integrate it into the game.

Now it might not be that easy due to lack of information but something as simple as a switch could not take a team more than 2-4 days to get it written and tested. And after the event stops the coding can be removed.

yolo swaggins.2570:

Now it might not be that easy due to lack of information but something as simple as a switch could not take a team more than 2-4 days to get it written and tested. And after the event stops the coding can be removed.

2-4 days that could be spent on something, anything else.

yolo swaggins.2570:

Now it might not be that easy due to lack of information but something as simple as a switch could not take a team more than 2-4 days to get it written and tested. And after the event stops the coding can be removed.

And then you would have players not dropping the portal after they farmed for it for XXX hours say that the code is bugged and that it flagged their account as having dropped a portal already while they have not and bla bla bla….

Thanathos.2063:

yolo swaggins.2570:

Now it might not be that easy due to lack of information but something as simple as a switch could not take a team more than 2-4 days to get it written and tested. And after the event stops the coding can be removed.

2-4 days that could be spent on something, anything else.

Believe it or not anet is working on everything at once. Taking 2-4 days max away from something as mentally taxing as working on the same large project for months on end would be a break for them. Still work, but a break nonetheless.

Blanche Neige.7241:

And then you would have players not dropping the portal after they farmed for it for XXX hours say that the code is bugged and that it flagged their account as having dropped a portal already while they have not and bla bla bla….

Account flags and portal drops are two different things. People will complain about drops vs hours anyways but at least they wont be spouting about how Mr. Smith got 5 portals after XX minutes and he’s standing there with [Truth] thinking the game is trying to tell him to stop. Tie the small bunch of code to account flag status and the only ones who will not be getting the portal are the unlucky, the ones who have beta access and those who gave up.