@HelloProject said in UX: It's time for The Talk:
I highly doubt you or anyone else would go "Well, shit, I miss when my syntax had needless complications".
Actually in my experience that is exactly what people say. Because you have people who have been playing this hobby for 20 years who know that syntax and are used to it the way it is. In a world where people avoid playing on MUX or Penn because the channel system is different, this is not an effect you can discount and expect to be successful.
@Roz said in UX: It's time for The Talk:
For the record, even the +combat commands in FS3 can be simplified. I know because on X-Factor where I used to staff, we aliased simplified versions of them. (Such as adding an "attack" command to alias to +combat/attack and whatnot.)
That comes down to UX style though. Consistency versus simplicity. When everything is +combat/foo it's easier to remember IMHO, as opposed to when some things are +combat/foo and other things are just foo. If having aliases works for you, great. But I would not call it a universal preference.
@HelloProject said in UX: It's time for The Talk:
don't make it a complete mess that needs 5 help files to explain how to use something.
You seem to be fixating on the number of help files. If there are a lot of features to document, and you do a good job explaining not only the syntax but when and why to use them, you're going to get more help files. That's not a bad thing.
FS3 Combat is involved. But there are levels to the documentation: an Interactive Intro Tutorial, a Quick Reference Guide, and then the full Documentation for those who really want to dive into the details.
It's the quality of documentation and the ease of use that matters, not the number of pages. (Btw, I'm sure the documentation can be improved. Just using it as an example.)
As @Ganymede and @Seraphim73 have mentioned, with Ares I've made a concerted effort toward UX while preserving the user experience of Penn/MUX as much as practical. People generally seem to be pleased, but there's always room for improvement. The help files for AresMUSH are all online. You can find them here. Pick a system. Tell me how to make it simpler without sacrificing functionality. (Of course if you ditch features you can simplify the syntax.)
Doesn't need to be (and probably shouldn't be) done in this thread, but I'm completely serious. I'm open to feedback here. Good UX on a MUSH is not some rainbow unicorn.