(repost) New User Experience (NUX) - Spoon's QA Feedback - Path of Love()

So I just went through with a new player, and all of the feedback and bugs reported in my New User Feedback from R34 are still valid:
https://www.shroudoftheavatar.com/f...ce-nux-spoons-qa-feedback-path-of-love.64099/



That feels a bit disheartening.

 

So @Attenwood do you want me to ditch the feedback and just log all of the bugs (about 20 or so, of which 5 are worldbuilding stuff) in that report one-by-one instead so that it was not all for nothing?

 

Funny - we could dismiss Charlotte Gray so that she wouldn't be in any danger and then after escorting Edvard get the reward for her anyway.

 

Great stuff, I really think at least 90% of this polish should be applied before release... **fingers crossed**

 

@Spoon I'm going to do a pass on some of this but bear in mind just because you report something doesn't mean we agree it should be fixed. Richard and the QA team have been iterating on these experiences pretty heavily, and we are also limited in terms of functionality for some of your suggestions. Please note also we are a small team and just because something is reported does not mean it can be fixed that cycle; especially minor fixes will be bumped frequently.

That being said:

Things going in as fixes for R37:
- suggestions on bank/safety deposit wording
- rephrasing initial hint when learning about conversations
- fixing New Britannia typo in Arabella/Cataclysm keyword
- deactivating Arabella's beckoning when saying goodbye after having recieved instructions
- clarifications within the Oracle's dialog on archetype creation

The vast majority of your feedback though was either opinion on how a tutorial *should* work (which we may disagree with - Richard in particular demanded several things you disagreed with such as keeping the chat window unpinned by default for new users and not going back and forth to Arabella) or wishes on how the scene should work in general (combat or inventory on Isle of Storms not being supported, for example, when we intentionally do not support that until the next scene), or simply breaking the tutorial sequence entirely by wandering off somewhere.

Honestly this is probably why there was no JIRAs submitted for this - while there were some good actionable items I took from this, I had to go through a LOT of suggestions/demands/wishes to get to them. They should be feedback, not bug reports expecting action and then complaints that none was taken.