Matrixcvd
Rionnag Alba
Triumvirate.
   |
Posted - 2008.02.19 17:38:00 -
[1]
Lots of good comments in here about how the interaction between Dev and community has been strained so i will try to hit some different ideas. 1 thing to remeber, as a Dev poaster, you are the face of the company. If you don't measure your text, revise it and check to make sure its as concise as possible, you will get flamed. Just cause you are working for the company does not absolve you from the heckle the rest of us can indure. Calling Carriers the swiss army of eve is about the dumbest line of text since 19-0. Getting rid of alt poasters and allowing 1 forum account per IP/creditcard check would do wonders
2. I always see the "As Dev's we use math"... WHile raw output of ship stats are important, the human factor is almost as equally important. And the final factor, there are 3, are game limitations. You guys have made an incredible game for 1000 people to play. The game is great for 10,000 people to play. The game is kinda cool at 30k, and uhm... probably ok but a drag and frustrating at 40k...
Too many times decisions are made without taking into consideration human factor and server/code limitations. And lets be honest people, testing on sisi is not really testing. The nerf/buff only gets their real test when people start playing with their own iskies. I am tired of hearing, "well we tested it on sisi, and this is what people are doing" Thats absolutely ratarded. That type of engineering analysis is like GIVING people corvettes and judging how they do on the track, instead of actually looking at paying customers and how they use it.
Finally, lets address all this math you speak of. The decision to change dictors is like askin those pilots pay to put themselves in a floating coffin. I like the aggession added to bubbles, makes sense, but here is where you have struck down the effectiveness of a class of ships. SO if you have ALL this data, instead of rudely telling us its math adn stats. SHOW US THE STATS. I have to assume that you have rolling statitics on a variety of ship kills from every possible angle, like an american baseball box score. Publish this in a clear format so we can see, its our kills and deaths anyways. Farm the data and give it back to the people! I want some pie CHARTS!
So to recap
 1. Express only substantial, thoroughly worked out concepts, or put giagantic disclaimers that this is some hair-brained idea that i crocked up and wrote on beer coasters.
2. Take the three aspects of this game, raw statistical output, human factor, server/client consequences into consideration before you even think of touching anything. And stop thinkin sisi is the end all be all place for testing. What happens on sisi, doesn't translate to TQ as the real money is on TQ. Idiots are gonna say "its all we got" NO you got TQ. Have a 2 or X week TQ trail run. The point is that if changes aren't functioning its better or easier for the community to swallow if there is some sense of humility in decisions and that even tho it has hit TQ its not written in stone, cause we know you guys aren't michaelanglo, nobody is.
3. When publishing game changes, publish data used to help carry the point with the community, or do this regularly, come up with a unified list of stats that can be disseminated to the community and tracted appropriately. Give us the data in concise format, spend some money and time showing us whats going on TQ. Even if you think this is a market risk, its better than having 100 page forum threads pop up arguing about everything AND the kitchen sink...
done
|