Quote:
Originally Posted by Dr. P.R. Park III
From experience, exactly what kind of format/information is helpful to Markus to market something like this to him?
|
I don't know if one way is better than any other, but offhand, my main suggestion would be to make your proposal as detailed and specific as you can. That is, sit down and think about what
exactly you want the feature to do, considering the implications of any options included with the feature, and then write up as a final proposal/suggestion.
The more precisely you can describe what you want to have happen with the feature, the easier it is for Markus to understand it and see how it works, and have a design plan which he can follow.
The dialog between you and Nutlaw in this thread is effectively doing that, as you are both working out the details of how you'd like the purchasing of contracts to work for this version of the game. Your suggestion in post #39 and Nutlaw's replies in posts #43 and #46 are good examples of refining the concept to a specific method of operation. A little more discussion and I think you'll have it figured out. Then just write it up and post it as its own post, introducing it by saying something like, "This is how the feature could work." (Or you could send it to Markus as a PM and referencing this thread.)
I'd say the biggest problem for a lot of suggestions is that they lack detail. It's easy enough to say put X into the game or implement Y, but often, there's a lot of ways X or Y could work, and without some sort of guideline, it's left for Markus to try and figure out. If you instead supply a well thought out roadmap, getting to the destination is much easier. Of course, this requires the user put it more time and effort to work out the ins and outs of a given feature suggestion, but I think it's worth it if it means a better chance of feature being adopted.