*snort*
And could we make planets if they aren’t added to the map? Or is it only for weapons etc?
Adding custom planets to the map has always been optional. So you can already do that - I don't see why this would change if we had a wiki.
And could we make planets if they aren’t added to the map? Or is it only for weapons etc?
Would there be any rules on subs being finished/editing in things later at whim (thinking of instances with pvp, someone editing a weapon/tech they are using mid-fight to try and gain the upper hand in a fight they are losing)? Or just, full wild west?
Adding custom planets to the map has always been optional. So you can already do that - I don't see why this would change if we had a wiki.
I remember a Wiki project from back in the day and I'd say - heck yeah, let's do it!And double down on a proper wiki and just let people go ham?
remember a Wiki project from back in the day and I'd say - heck yeah, let's do it!
Hello all,
I don't really contribute to the public/community side of this site. Not really my thing.
But, in this area, I may be able to offer some humble guidance. As a Wookiepedia contributor, former low-level Wookiepedia Mod, and with several thousand edits and page additions to Wookiepedia (I've seen some of you using my Turadium, Songsteel, and other material and tech entries over the years), I might be able to offer some do's and dont's if you choose to go forward with this as a site.
1) Security concerns.
Some of you were concerned about your wiki being potentially wiped out. While that was a major issue when wikis first launched, most wikis now incorporate a history system that makes it easy to reverse most changes - a top level admin theoretically has the ability to recover the entire site, provided they weren't the one who goes ham and deletes everything. You can even deploy wikibots to make curating and article reversal decisions pretty easy and automated.
2) Absolute must - Manual of Style
Most people don't realize it, but Wookiepedia has an extensive manual of style. We try not to use contractions, we use past tense, and depending on the subject there's a proper format to writing an article. If you make a wiki, implement a basic manual of style that needs to be adhered to; you really run the risk of your wiki looking like a mix-mash of randomness otherwise, which is a good way to motivate disinterest and disuse.
3) Promote cross-integration
A lot of people have their main site, and then they have their wiki. That really splits traffic between two sources and weakens traffic (Imagine, the ones who really love factory and codex work spend all their time on the wiki, not on Chaos). While that isn't guaranteed to happen here, it did happen on SW Combine due to the game nature of their site. Try to implement cross-integration. Advertise Chaos on your wiki, such as nominated players, play of the month, events, etc. On Chaos, nominate feature articles, writers on the wiki, etc. Try really hard to make it a cohesive and symbiotic thing, in otherwords, not two separate entities.
That's all! Fading back into the aether now.
- Roth
I only got one dawg in me and she lazy you feel
Well I’m probably echoing what most people think, but I’ll say it anyways. The appealing thing about the current codex/factory system is that it is flexible enough to encourage whatever level of design commitment a player wishes to exercise for their playing style. This, while making it rewarding no matter how much one chooses to put into it. As long as the new wiki system allows for that level of flexibility, it’s likely to be every bit as popular as the current system.There's arguments for "high quality does attract more people" 100% but like, I only got one dawg in me and she lazy you feel
thankless job
thank you for monthly/me stares out window into rain