{{
`${userDetail.user.displayName}${userDetail.user.cachedBungieGlobalDisplayNameCode ? `#${standardizeBungieGlobalCode(userDetail.user.cachedBungieGlobalDisplayNameCode)}` : ""}`}}
{{getUserClans()}}
10/15/2014 4:41:12 PM
2
I like this idea and I support it, but I do want to bring up some potential problems this could pose.
1. If people discover a particular exploit in a particular strike that makes it super easy to speed run through than you'll get a lot of people wanting to always do that strike over and over and over again.
2. I've seen this happen in Halo, people will leave a game simply because they didn't get the strike they voted for.
These problems are very small and as more and more strikes get added it would become even less of a problem, I just wanted to be clear on the potential risks of such a system.
English
-
Speaking on your number 1, I stated that the strikes that come up for voting CAN'T be the one you just finished. Strikes that haven't been done yet take priority in the voting list. I do see problems with this system but at least it would be easier to have a leaver at the start rather than in strike then matchmaking doesn't get you a 3rd or leaves you alone. Thanks for the support!
-
I understand, I was imagining people would leave the matchmaking and re-enter to try and get a new list, but if the system keeps a hard list on what strikes have been done recently and strictly avoids them than I suppose it really isn't an issue.
