Aller au contenu

Photo

Things to consider while making suggestions.


  • Veuillez vous connecter pour répondre
5 réponses à ce sujet

#1
Azrus

Azrus
  • Members
  • 201 messages

Alright, I was going to reply to a particular thread with this but upon reflection decided this was really something that was best said outside the context of any one issue.  So, these are just some things I think the community needs to think about while we're discussing changes we'd like to see.

 

1. The state of the game and the community is going to change as time goes on.  Yes, loot plays a big role in progression right now, and yes, it is very, very random.  However, as time goes on more and more of the community is going to find decent gear and content is going to get progressively easier as a result of it.

 

2. A lot of the recent recommendations/suggestions are largely based off of problems caused by bugs.  Some examples of this are the zombie-pots and losing XP due to crashes/disconnects/kicks.  When the bugs behind these issues are dealt with, the severity of these problems is going to be much lower.  I'm not saying we shouldn't make suggestions or recommendations on these elements of the game, all I'm saying is that we should think about what exactly we've got a problem with, and if that is being caused or exacerbated by current bugs.

 

3. I actually only had two items I wanted to mention, but I feel like things go better in threes.

 

So, that's it.  If anyone has anything else they'd like to mention, by all means, go ahead.



#2
Shadohz

Shadohz
  • Members
  • 1 662 messages

2. A lot of the recent recommendations/suggestions are largely based off of problems caused by bugs.  Some examples of this are the zombie-pots and losing XP due to crashes/disconnects/kicks.  When the bugs behind these issues are dealt with, the severity of these problems is going to be much lower.  I'm not saying we shouldn't make suggestions or recommendations on these elements of the game, all I'm saying is that we should think about what exactly we've got a problem with, and if that is being caused or exacerbated by current bugs.

In the tech field when we provide a solution to a very egregious problem(s) before we can formally address it/tem long-term we call it.. a workaround.



#3
Azrus

Azrus
  • Members
  • 201 messages

I'm not talking about "Hey, you know if you bunny hop it lets you move quicker while rubberbanding.", I mean "Hey, zombie-pots are annoying.  They should patch it so that we can continue to target them after they reappear".  One is a workaround, the other is asking for design changes to fix a problem that only exists because of a known bug.

 

By all means, share methods of managing bugs until they get fixed.  Asking for patches to address problems that only exist, or are only as severe as they are due to reported bugs which will presumably be fixed is just... kind of pointless if you ask me.  Why would we expect BioWare to expend resources towards creating a workaround instead of addressing the bug in the first place?



#4
Shadohz

Shadohz
  • Members
  • 1 662 messages

 

You're talking about an end-user workaround ("hey I found a way around this bug in your program"). I'm talking about an in-house created workaround ("hey let's give them a workaround for now so that we have time to properly address it later."). A workaround doesn't always have to run the same formal process as enhancements and bug fixes. A workaround doesn't become a "design change" until or unless the company decides NOT to act on it (too costly, too risky, too time-consuming, end of life cycle) or they pull a Microsoft ("working as intended").

It's not pointless to ask a company to address and issue, offer suggestions, or ask on an ETA on a major problem. For liability purposes, an employee doesn't have to provide any in-depth reasoning how something works, how they operate, why something can or can't be fixed a certain way.



#5
golyoscsapagy

golyoscsapagy
  • Members
  • 541 messages

I disagree with your first point. If the drop rate of a good weapon is 0,01%, guess what - of all the weapons 0,01% will be good. That's about the number of players who will actually stay to play as well. Getting level 1-5 white drops for 100k worth of chests is frustrating and gets old really fast. So no, if there's no guaranteed progression of any kind I have serious doubts this game will have even quarter of the longevity of ME3MP.


  • pejot82 aime ceci

#6
veramis

veramis
  • Members
  • 1 956 messages

Workarounds are often significantly easier to implement than real solutions and should sometimes even be used regardless. To illustrate, it would take less than an hour to write some code to reduce or eliminate the xp penalty when a crash is detected or to replace vases with gold or chests, but it may take hundreds of hours to deal with the major causes of crashes or the underlying reasons for self-repairing vases. The former can be done in a day easily, the latter may take weeks, months, or even never occur if corporate commander at EA says screw the customers.

 

Let's think about it a bit, just how often do people leave in the middle of DA3MP games because they are trolling, frustrated by lag or bad players, or just have to go? And how often do people leave them because they were forced out by bugs? Let's be generous and say it's 50/50, in which case a crapload of players are being punished because of bugs, and will likely continue to be punished by bugs while bioware diddles around. The purpose of XP penalty for "leaving the game" is obviously to deter people leaving in the middle of the game, which is orders of magnitude less detrimental to players than innocent people losing hours of gameplay due to bugs. In such a situation, bioware should have released ON DAY ONE a patch to reduce or eliminate the XP penalty for crashing, or even for manually leaving the game through normal UI, and then they can remove the workaround after the crashes are fixed if they want.