Does anyone read the GalCiv2 Wiki?

I put some effort into making a nice "bugs and features" page. Has anyone else looked at it?

I also made some contributions to some of the strategy pages.

In particular, has anyone from Stardock looked at it? (I mean, if I'm wasting my time, I'll just forget about it.)

https://www.galciv.wikia.com/wiki/Bugs_and_Requested_Features
16,515 views 13 replies
Reply #3 Top

Yep, I do too.

For me, the data and strategy tips have been quite helpful in learning the game.

Reply #4 Top
I found the wiki too outdated, the forums were a better source of information for me.
Reply #5 Top
The Wiki has been very helpful to me. I really appreciate people updating the pages! Keep up the good work.
Reply #6 Top
Even though it may be outdated in parts, it's far more structured than random forum posts and has some very interesting info on the underlying mechanics such as how morale works.
Reply #7 Top
I check it occasionally, especially when a post here mentions a page there. I agree that the structure there can make finding info easier than rooting around these forums, and I'm grateful that a few GC2 folks make time to work on improving it.
Reply #8 Top
Excellent primer on many aspects but, i agree, somehow "outdated".

This kind of information(s) isn't really available anywhere else (in a sense that well organized data may be easier to read!).

Some Tips & Tricks should really get a dedicated section where anybody would find "rare" bits about hidden/complex/undocumented/etc features.
Just the "modding tool" by CariElf found here is a very useful resource and also must get updated to much more recent values (thinking DA stuff).

Besides, anyone serious about "learning" the essentials has to look around that wiki... even if only to get particulars on numerous subjects.

Eventually, that place will need a TA part, too! ;)

Overall, i'd say keep up the fantastic work for such a great complimentary asset.

- Zyxpsilon.
Reply #9 Top
It was very useful to me. Like anything else it needs more user support. I'm so new to gaming that I wouldn't be a good source for useful info. But, I've been reading posts from what I believe are power players, who could add extremely useful data. Try replying to their posts and ask for their help. Maybe a few will even like the chance to teach what they know to others. This could greatly increase the value f the game.  
Reply #10 Top
Hi!
In particular, has anyone from Stardock looked at it?
End of quote

IMO not. I remember reading a post from Brad, that said GC-2 wiki is user-made, and SD doesn't support it. That's IMO a pitty. Since lots of game mechanics is hidden or non-obvious, I'd really like to have someone familiar with the game code to confirm the "hard" facts stated there.

BR, Iztok
Reply #11 Top
I check the wiki for something at least once a day.

Now (after reading the bugs and requested features) I'm wishing that they'd just axe ship designs from the tech tree entirely, and unlock appropriately sized templates when you research the technology to build that hull size.

Plus, integrate Kyro's hull mod as part of the game.

I don't ask for much, honest. :)
Reply #12 Top
I remember reading a post from Brad, that said GC-2 wiki is user-made, and SD doesn't support it. That's IMO a pitty.
End of quote


I posted something that made Brad reply along those lines some time ago, not sure if that's the one Iztok is recalling here.

I surely agree that the lack of a wiki-Kryo is a pity, but I have a shred of sympathy for Brad's POV as a user of scarce resources when it comes to Stardock labor spent on GC2.

Part of what makes the wiki more useful for me is also what makes it more demanding to build and maintain--it wants to be structured hypertext. Even if all you want to do is work as a minor cleanup person, you'll still need to sign in separately and take care to avoid breaking any of the wiki tags around the text you want to tweak. That surely keeps a fair number (most?) of the "power players" who post here from doing regular work over there.
Reply #13 Top
Kyro = Kryo. Stupid typos.