Kothoses Rothenkisal wrote...
Eldred wrote...
Ye that is how I see it as well but from how I understood you on the video is that you also wanted the fan to come up with the solution. I'd say good feedback would be sufficient to have information like;
Ideally yes that would be the best response, but listing what you felt was wrong and why is not a bad response, just not the ideal, in my opinion.
I'm with Kothoses on this one. Indicating that something is wrong is useful feedback, but without explaning the why, describing what the underlying problem (and valued bits) are or indicating a good way to address it risks developers highlighting a problem and then providing the wrong solution which may, in fact, create a new (worse) problem as a result.
For example;
A) I don't want to spend ages trying to work out where I should be putting points in my characters and companions.
Dev: Hmm, okay. Maybe we should reduce the number of stats down to three and fix companion values.
Dev: Ah, right. Then we'll have armour that levels up with you, stars to indicate quality rating, link key stats to certain careers and remove some of the 'flavour' resistances and attack types so its all more straightforward.
C) I don't want to spend ages trying to work out where I should be putting points in my characters and companions, it wastes time if I'm worrying that I'll make poor decisions and struggle later on in the game. I like the variety you've offered and the different choices and don't want you to change that, but it would be great if you could show the effect of decisions on the level up and character screens, e.g. if I put 2pts in Dexterity, what does that actually do for my attack and defence rating against the enemies I'm facing.
Dev: Gotcha. We'll leave all the stats and companion choices as they are, but we'll display the to hit / be hit values for Dexterity (and other stats) so you can make an informed choice.
Same person. Same grumble. Three different proposed solutions - only one of which would actually please them.
Plus, describing a possible solution also helps flag what you're actually trying to address. Working back from the requirements of the solution is one way to highlight the criteria you need to test against to make sure your solution is working as designed.





Retour en haut




