I really hope the design team is looking at these informational posts

from GalCiv3 Forums

I really am hoping that the design team for this game are looking at these posts and adjusting the game with the information from all the people testing out this Alpha version. It would be nice to see some replies from the actual design team replying to our posts and interacting with the communities and working together to help create the game with their Fans/Alpha Testers. Just a thought. :)

3,566 views 4 replies
Reply #1 from GalCiv3 Forums Top

They are. But it's the weekend :)

Reply #2 from GalCiv3 Forums Top

Quoting kryo, reply 1

They are. But it's the weekend

They have a lot of reading to do on Monday...  *_*

WindowBlinds - Free yourself of the default settings, customize your desktop.
Reply #3 from GalCiv3 Forums Top

FEEDBACK, first game, first 100 moves. (No constructors constructed yet.)

Gamesetup.  Any chance to pick icon for species, or will icons be locked as in GC2?

Planet picture, with clouds and atmosphere - excellent.

General comments:  Very good looking. Hexes, fog of war, etc., all very good.  Actually a very esthetically pleasing experience.  Way cool!

Specific items:

Ships leaving a planet.  "Eject" ship sounds awkward.  How about "leave orbit" ?

Renaming the GC2 'flagship' to 'survey ship' is excellent.  EDIT: after playing a bit: survey ship gets bonuses to speed, visibility range, etc., which is also imparted (according to description)  to all ships in same fleet. This means the survey ship will become an asset to a fleet.  Given this, it behooves a player to build several survey ships (as long as anomalies are still around) so that once one survey ship gets a few bonuses, it can be assigned to a fleet, while other survey ships acquire bonuses.  Thinking of name that fits with 'survey' but also works for enhancing a fleet.  C n C, ECM, explorer don't work.  What would?

Build queue on planets, specifically trying to build in a specific planet hex, is awkward.  Game engine seems to change hex location when you hit 'build.' 

Reply #4 from GalCiv3 Forums Top


I really am hoping that the design team for this game are looking at these posts and adjusting the game with the information from all the people testing out this Alpha version. It would be nice to see some replies from the actual design team replying to our posts and interacting with the communities and working together to help create the game with their Fans/Alpha Testers. Just a thought.

 

They already have replied to several.  It helps, however, to remember that as much as Stardock has grown, it has only been able to grow because its fans and customers have grown a lot more -- so there are a lot of us to just a few them.  They are very good at taking the time to read posts and interact with us customers on the forums, but there's still a matter of there being quite a lot of customers to just a handful of employees, and they can't spend /all/ day on the forums.  I suggest trying to think of ways to make it easier for them to find what they need in thinking about organizing your posts.  I'm not criticizing here, its just a suggestion, something I try to do to help avoid my posts from getting lost in the noise when I have a particular bug I'm reporting, versus my chitter-chatter posts.

I think a couple tips here might help make it easier for Stardock's crew to pick out what they need:

First (this is hard given how noisy the boards are, a lot of activity with the alpha in progress) see if what you post has been posted before.  Try not to start a new thread if something's already been brought up, but it certainly helps to add to that thread (especially if you produce screenshots or other information to make it easier to track the issue down).

Second, try to think of a useful topic for your post when your post is intended to convey important information such as a bug report.  A common format among public beta testers (and, hey, we're alpha testers! :P) when posting a bug report to a forum like this is to 'tag' the post title with [BUG] and a brief synopsis of the bug in the title, a glitch with [GLITCH], a suggestion with [SUGGESTION], etc.