A guide to making suggestions
This is a short-ish guide on making suggestions, to help you make better suggestions. Remember that these are my opinions though.
Any suggestions to make this better are welcomed, I didn't spend a lot of time writing this.
Anyway, onto the subject at hand:
Suggestions should be well explained simply, they shouldn’t be confusing or complicated, having good spelling and grammar/punctuation helps a lot too. When suggesting new items it’s not a good idea to give specific stats but rather suggest what the item should be like, E.G. if I wanted to suggest a new weapon I’d say something like:
Quote:
Surgical damage pulse which is fast, low tracking, high RoF, medium DPS, built from a BP that drops from X (at Y).
Keeping things quick, clean and simple makes reading the suggestion a lot easier and quicker (obviously).
Suggesting nice fancy content zones can be nice, but big zones take lots of time to make and get them working correctly.
If you do have a big suggestion, break it up into smaller sensible parts, remember to have a summary/tl;dr (even use these as an opening paragraph, if you wish). Don’t suggest silly/broken things, because it’ll just waste our time reading it and your time typing it.
If you want to suggest content for an event (Halloween, Easter, etc), the best time is 2-3 months before the event to give time for the work to be done, although if you suggest them any time of year I’ll take note.
Most of the things I’ve commented on so far are content related, because that’s what I do. When it comes to programming changes, remember that Star Sonata 2 release is very soon, so suggesting something big for the current client isn’t going to get implement. Also remember programming new features isn’t always possible due to the way stuff has been done in the past.
Remember that although we may not always comment, doesn’t mean we don’t read, adding a comment saying “Can we have a dev response?” makes no real difference, because either we see it or we don’t and the opinions we give are our own.
Things to generally avoid suggesting is new classes, unless you can find a rather large niche they can fill. Also as I already said, avoid suggesting stats or all the stats. Some stats are proportional to each other (like size, reflectivity and visibility on ships), so suggesting values for all three of these is not a good idea. Also avoid getting in derailing arguments about things, it just doesn't look good.
Just remember KISS for your suggestions,
Keep
It
Simple,
Stupid.
Another great thing for suggestions is feedback! So remember to give some of this too, including suggestions to make this better.