Post by Azherae on 2021-07-28 07:01:41
Even so, that's not even the definition of the 'problem'.
MMO design isn't a monolithic perfection state that one is striving towards. It's a requirement from effectively, a customer.
It's not as if the fact that there are other groups with years of experience in games results in the games being 'better' in the way that we all end up enjoying either.
A simple example is that in my old company, the CTO was the only person with a specific skillset, and I was the only one with a different specific skillset. Without us, there was a project that would have taken a year to be done, and would probably still have been done incorrectly.
Similarly, when a new 'specification' presents itself, the CTO still has to spend months designing it, and still asks both the customer, and even junior developers, for help and insight, and often, that turns out to be helpful.
Could it have been done alone? Actually, for some parts of it, no. Lots of it is 'asking the user exactly how they want something to be', and then having to come up with a whole new way of doing something because they want a combination of features that has never been done before and there's no framework. Sometimes they can provide the framework for you.
That's partially why I have the perspective I do on this sort of thing. I've been in that place, asking the client multiple times for their input, and wishing they didn't just go 'well I don't know, you're the experts, you do what seems best'. Not even because they all complain later, but simply because what they end up getting is 'generic version of product' that is nowhere near the best fit for them.
Tell them your best fit.
MMO design isn't a monolithic perfection state that one is striving towards. It's a requirement from effectively, a customer.
It's not as if the fact that there are other groups with years of experience in games results in the games being 'better' in the way that we all end up enjoying either.
A simple example is that in my old company, the CTO was the only person with a specific skillset, and I was the only one with a different specific skillset. Without us, there was a project that would have taken a year to be done, and would probably still have been done incorrectly.
Similarly, when a new 'specification' presents itself, the CTO still has to spend months designing it, and still asks both the customer, and even junior developers, for help and insight, and often, that turns out to be helpful.
Could it have been done alone? Actually, for some parts of it, no. Lots of it is 'asking the user exactly how they want something to be', and then having to come up with a whole new way of doing something because they want a combination of features that has never been done before and there's no framework. Sometimes they can provide the framework for you.
That's partially why I have the perspective I do on this sort of thing. I've been in that place, asking the client multiple times for their input, and wishing they didn't just go 'well I don't know, you're the experts, you do what seems best'. Not even because they all complain later, but simply because what they end up getting is 'generic version of product' that is nowhere near the best fit for them.
Tell them your best fit.