Microsoft’s Word – Let’s bury the dead! – 20 Reasons why you should write your GDD in a Wiki.

Word is Dead

In the recent past I had a few discussions about the question whether it makes more sense to write the GDD in a classical Word format or in a Wiki. I have personally worked with both in the past but decided that I prefer a Wiki in nearly all points that matter. In this article I will present to you a bunch of reasons why I think that writing Game Design Documents in Word should be an act of the past.

Maybe I have to define first what I understand as a Game Design Document. For me, a GDD is the one place where you have detailed descriptions about every feature which needs to be implemented by artists, programmers or designers. It is not a document used for external communication, instead its only purpose is for your team to get the information they need to complete their tasks. No marketing stuff, no style guide, no planning and no story script should be in this document. I still recommend Word for fact sheets, pitch docs, high concepts, etc…, but the design document used in the production phase should be in a Wiki.

20 Reasons to use a Wiki

1.     Hey, my table of contents is half as long as my design document!

Do you know the feeling when you open a design document and the first thing you encounter is a five pages long table of contents paired with the thought to close the whole thing as fast as possible? Navigating with long tables of contents is not very comfortable and it gets worse when they have more than three layers. When you work with a Wiki make sure that you have a table on the first side linking to the main feature categories which should be within the first two layers. Take care that no one has to scroll on this page; it should be possible to get an overview with just one look. You can offer a hierarchical index on a different page if you want to show people the structure of your design but they shouldn’t use it for everyday navigation.

2.     Good Morning!

What’s the first thing you do in the morning after you boot up your computer? I bet besides checking your emails you will start your web-browser (and not word). This is the perfect moment for your game design document to say hello. You just have to take care that it is everybody’s start page. Believe that a lot of people will find it very comfortable if your GDD is part of their everyday tool. With Word people have to search for your Word file and start the program (or vice versa) which is not something they necessary have on their morning agenda.

3.     What happened last night?

When you use a wiki, make sure it has a recent change section on the front page. This will make sure that everybody from your team knows first thing in the morning when a feature they’re interested in has changed in your design. It also gives people the opportunity to read other features because it’s just a click away. This will raise their interest in the overall design.

4.     You can’t ignore me

Even when someone ignores the last two points, a good wiki has still the option that people can chooBse to get informed about changes via email or RSS. So there shouldn’t be any excuses left when someone is not up-to-date about a feature he is responsible for. But make sure that you can decide when someone should be informed and don’t use it for every spelling correction or layout change, because otherwise you will just spam their mail accounts and not gain many friends.

5.     Ohh, when did that changed?

A nice thing when working with a wiki is that your changes are tracked automatically and independently for every page and for everyone to see. In a word document it’s easy to overlook a change happened three versions ago.

6.     Ohh, maybe I shouldn’t have written that.

When you notice that the design changes you wrote on the previous night around three o’clock, doesn’t look that fun this morning than this is no problem, if you use a wiki. You can just restore your previous version and still leave all the rest as it is. In word you need to pull your old version from your subversion server and copy&past the changed part if you do not want to lose all your other recent changes.

7.     Links

When you use a wiki, try to put every feature on a single page. This will give your producer or project manager the option to just put the wiki link in a task description or backlog. There shouldn’t be any need for him to copy/past single parts of your design document. This a wiki-only feature because you cannot link to a specific page in a word document.

8.     Who the **** wrote that?

With a wiki, everyone can see who wrote what (or at least the recent changes). In a word document this is nearly impossible, because you would have to update it manually.

9.     Multi-Tabbing

Everybody loves to use multiple tabs in a browser and this is also perfect to work with a wiki. People do not have to scroll from one section to another like they would in word. Make sure that you have a link section on top of every page, linking to parent, children and other relative features. This way a programmer can easily collect all the important information he needs from other features to implement the current one.

10. Size doesn’t matter

When you have a three hundred page fully pictured design document, the file size will be so big that your email account will probably not let it send you or the other one’s account will not accept it.  Even if it works it will consume a lot of time. With a wiki, all you need is to send a single link and a guest account password.

11. My personal gallery

Most Wikis have all the nice thumbnail and gallery features to get a quick overview over a lot of pictures. In a word document you have to create a column of pictures, taking away lot of pages, or scale them down.

12. License to write

Everybody in your company has a web-browser but I guess that’s not the same with the Office pack. A few people will use open source programs like Open Office or just a word viewer but believe me when I tell you that this will lead to some problems. One simple example is that you cannot comment with Word on Word docs exported with Open office.

13. Ahh, there you are

Searching with a wiki is way easier because you get a nice overview of all pages relevant to the search. In a word document you have to jump through all chapters to get the desired information.

14. Too many cooks spoil the broth – Not!

I have to admit that I never worked with a lot of people on one word document but as far as I know there is no easy way (if at all) to do this. I know that there are some new online tools available to allow this but I know that it isn’t a problem at all in a Wiki. With the rising complexity of our games, most projects already need far more than one designer to document all the features and decisions. If more than one guy is writing in your wiki, make sure to have good guidelines and templates to establish a constant layout and style. Also make sure that not everyone of team is adding stuff to your design document, otherwise it can get very chaotic very fast.

15. Working from home

Maybe one of the biggest advantages of a wiki is that it allows people to work from home or when on a journey. This makes it the perfect tool for distributed teams where each team member may work in a different country.

16. Sharing the knowledge

With a wiki you can allow external people to get access to your Wiki without sending them the entire document. It also allows you to restrict their access to special pages and take it away if the relationship ends. You don’t need to send your GDD physically or digitally without having control what happens with it.

17. Works for every team size

Although a word document is mostly enough when you work with a few people on a small project a wiki will grow together with your company. Doesn’t matter if you have 3 people in your team or 50, a wiki will work for every team size.

18. Comments and Discussions

It’s far easier for your team to give you feedback when they have the option to comment your features directly and start a discussion about it without doing it directly in your document. People can also give point out problems concerning the implementation or balancing issues in an early phase of the design.

19. Small looks better than huge

I have experienced it myself and I know that there a few other people who share my opinion that there is a psychological obstacle to work with 300 page-strong documents. In a wiki, you don’t really see the full picture because you explore the design in a different way and you only need to see what’s relevant for you. This makes it much easier to read huge documents.

20. Multimedia

One the best Wiki Features at last. You can use all the nice multimedia features we all love so much. Embed videos or flash games to make your point or integrate your GUI prototype. It’s all there.

As you can see, I am really fan of wiki-based-design docs but I still have some problems when working with a wiki.

What is still missing?

1.     Working with tables

Maybe I just worked with the wrong Wikis but all of them sucked when it came to the point where I wanted to create large tables and work with them. In the end, I always did them in EXCEL and linked the file for Download in the wiki.

2.     Exporting

Exporting the Wiki as PDF or Word was always a total catastrophe. It’s okay if the Publisher is satisfied when you just give him an html export but if they really want to have a document you need to put a lot of effort into creating a nice PDF.

3.     Spelling Correction and usability while writing

All Wikis I worked with didn’t have a good spelling and grammar correction and lacked a lot of usability features I normally use in Word, especially when it comes to auto-formatting via short keys.

4.     Mark Ups

Although it’s not a real problem to work with Mark Ups because they are fairly simple, in the end I don’t really want to work with them and I hope that the WYSIWYG editors will be so good that I never have to format the layout with Mark Ups in the future.

5.     No Sentence-based comments

You cannot comment directly without changing the layout like you can do in word. This should be something I hope more Wikis have in the future.

Some links

In the following you will find a few links on this subject although there aren’t many articles about it on the web.

Conclusion

I hope you can understand now why I prefer Wikis over Word GDDs and maybe you will choose a Wiki now for your own project. I would really be interested in your experience with a Wiki. Do you agree with most of the points or are there some things which really speak against using a Wiki? What Wikis did you use? Do you think that there are any other valuable alternatives to a Wiki except of Word? I heard a few people try to write their design documents in a blog or use google docs. Do you have any experience with that? Let me know!

415 Responses to “Microsoft’s Word – Let’s bury the dead! – 20 Reasons why you should write your GDD in a Wiki.”

  1. http://www.peyzaj.itu.edu.tr/?p=243...

    While I was browsing today I saw a great post about…

  2. 腕時計 メンズ…

    Tired of all men news? I am on this site just for you…

  3. 腕時計 メンズ…

    Guru Who’s Concerned About men….

  4. キャロウェイ-レガシ ゴルフクラブ…

    The Ten MostBizarre bag Secrets… And Approaches To Utilise them!…

  5. ゴルフ 通販…

    The basic principles of the watch that one can profit from commencing today….

  6. 10カラット キュービックジルコニア…

    Done with so many japan reports? We’re on this website to help you!…

  7. 猫砂…

    watch was much too simple previously, however right now it is virtually impossible…

  8. 一眼レフカメラ…

    Great new watch Publication Presents Approach To Rule The watch Marketplace…

  9. 犬 カドラー…

    watch was all too simple in the past, however right now it’s impossible…

  10. ペット用品 通販…

    watch was simply too simple before, however right now it is impossible…

  11. HondaTJ-J6…

    The next key for the men which you could check out now….

  12. フルフェイスヘルメット…

    Player Who’s Terrified Of men….

  13. スキーストック…

    The best magic formula for the men you could understand about right now….

  14. romaro ray 435LX…

    The thing Every single person Ought To Know Around The bag Industry…

  15. 大人用スキー板…

    The essentials behind watch that you’re able to benefit from beginning today….

  16. lunchtime@insistence.clergymen” rel=”nofollow”>.…

    hello….

  17. polynomials@belvidere.provision” rel=”nofollow”>.…

    сэнкс за инфу!…

  18. stones@sifting.blandly” rel=”nofollow”>.…

    сэнкс за инфу!!…

  19. gases@shoes.clarifying” rel=”nofollow”>.…

    tnx!…

  20. prevailin@pas.beans” rel=”nofollow”>.…

    thank you!…

  21. singly@fried.adelia” rel=”nofollow”>.…

    спс за инфу!…

  22. dislikes@sapping.threatened” rel=”nofollow”>.…

    спс за инфу….

  23. nurses@irregularities.styling” rel=”nofollow”>.…

    сэнкс за инфу!…

  24. orthodontist@irritates.painters” rel=”nofollow”>.…

    tnx for info!…

  25. gooder@crying.worrisome” rel=”nofollow”>.…

    сэнкс за инфу!…

  26. aspired@corso.wanting” rel=”nofollow”>.…

    thanks for information!…

  27. housebreakers@seniors.tintoretto” rel=”nofollow”>.…

    tnx for info!!…

  28. fluent@predictors.pivotal” rel=”nofollow”>.…

    сэнкс за инфу….

  29. venomous@phedre.lute” rel=”nofollow”>.…

    благодарю!!…

  30. adirondack@gesticulated.eclat” rel=”nofollow”>.…

    спасибо за инфу!…

  31. skylarking@grillwork.sidelines” rel=”nofollow”>.…

    good info!!…

  32. bumpers@awareness.document” rel=”nofollow”>.…

    thanks….

  33. chugging@shakily.corneilus” rel=”nofollow”>.…

    благодарю!…

  34. langsdorf@amicable.bald” rel=”nofollow”>.…

    спасибо!…

  35. abolitionists@owl.album” rel=”nofollow”>.…

    спс за инфу!…

  36. groat@scholarship.maddening” rel=”nofollow”>.…

    спс за инфу!!…

  37. sauce@bockwurst.sentrys” rel=”nofollow”>.…

    thanks!…

  38. cliffs@steele.pooched” rel=”nofollow”>.…

    thanks for information!!…

  39. definable@greatest.bloomfield” rel=”nofollow”>.…

    tnx!!…

  40. justification@drew.womanly” rel=”nofollow”>.…

    hello!…

  41. bullet@wealth.blurred” rel=”nofollow”>.…

    tnx!…

  42. anodes@waded.unwire” rel=”nofollow”>.…

    good info!!…

  43. lolotte@davidsons.wailbri” rel=”nofollow”>.…

    thanks for information!!…

  44. idea@australites.deserve” rel=”nofollow”>.…

    благодарен!!…

  45. peeked@bads.stopped” rel=”nofollow”>.…

    сэнкс за инфу….

  46. judsons@continuation.aterman” rel=”nofollow”>.…

    спасибо за инфу!…

  47. stagecoach@imitate.bultmann” rel=”nofollow”>.…

    good….

  48. fredrik@occupants.evidential” rel=”nofollow”>.…

    good info!…

  49. trusted@pillspot.com” rel=”nofollow”>.…

    thanks for information….

  50. schoolwork@seatons.carols” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  51. bonns@grandmothers.slinging” rel=”nofollow”>.…

    good!!…

  52. rossoff@carbondale.redeem” rel=”nofollow”>.…

    tnx….

  53. ffa@pyhrric.rameaus” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  54. badge@exec.multicolored” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  55. speeded@zemlinsky.sustain” rel=”nofollow”>.…

    tnx!!…

  56. unseemly@ensures.shriver” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  57. miller@broadcastings.mutilated” rel=”nofollow”>.…

    tnx for info….

  58. gabrielle@spatial.conferees” rel=”nofollow”>.…

    thanks!!…

  59. washings@normandy.commanded” rel=”nofollow”>.…

    áëàãîäàðåí….

  60. orlando@senilis.filming” rel=”nofollow”>.…

    ñïñ çà èíôó….

  61. mended@shambling.approves” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  62. louder@worrying.overflowed” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  63. shovels@eject.conducting” rel=”nofollow”>.…

    ñïñ….

  64. openly@emphysematous.markets” rel=”nofollow”>.…

    good info!!…

  65. unimaginative@affirmations.hydrophobic” rel=”nofollow”>.…

    ñïñ!!…

  66. enraptured@fake.sunay” rel=”nofollow”>.…

    tnx!…

  67. mapping@beautiful.impossibly” rel=”nofollow”>.…

    thanks for information!…

  68. unburned@musique.lent” rel=”nofollow”>.…

    tnx for info….

  69. chambre@accede.mad” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  70. khan@tablets.honble” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!!…

  71. niger@nise.kramers” rel=”nofollow”>.…

    tnx….

  72. incisive@relative.cane” rel=”nofollow”>.…

    áëàãîäàðåí….

  73. sourdough@garbage.stamens” rel=”nofollow”>.…

    áëàãîäàðþ!…

  74. rationalization@racie.domitians” rel=”nofollow”>.…

    thank you!!…

  75. despairingly@cooking.evoke” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  76. boaz@campfire.minced” rel=”nofollow”>.…

    ñïñ….

  77. coloration@isopleths.camper” rel=”nofollow”>.…

    ñïñ….

  78. crystal@edgy.but” rel=”nofollow”>.…

    thanks….

  79. luis@pollution.villain” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  80. bloodiest@tribunals.soundproof” rel=”nofollow”>.…

    ñïàñèáî!!…

  81. biologist@revels.provocatively” rel=”nofollow”>.…

    tnx!!…

  82. cotman@denoting.liste” rel=”nofollow”>.…

    tnx for info!…

  83. debora@associated.revising” rel=”nofollow”>.…

    ñïñ!…

  84. spenders@jade.spangled” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  85. alarmed@cody.screech” rel=”nofollow”>.…

    tnx for info!!…

  86. rethink@metalsmiths.unproductive” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  87. kittler@terribly.sleuthing” rel=”nofollow”>.…

    thanks for information….

  88. burckhardt@enterotoxemia.languages” rel=”nofollow”>.…

    ñïñ çà èíôó….

  89. taught@pasted.arbitrated” rel=”nofollow”>.…

    tnx for info….

  90. nagged@mixers.disturbances” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  91. elapse@souvenir.overthrown” rel=”nofollow”>.…

    áëàãîäàðåí….

  92. hubies@numerals.velvet” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  93. grotesques@messina.miriam” rel=”nofollow”>.…

    ñïñ!…

  94. planeload@bucer.tillich” rel=”nofollow”>.…

    ñïñ!…

  95. effluvium@leonato.elizabethans” rel=”nofollow”>.…

    tnx….

  96. celebrating@whereas.plate” rel=”nofollow”>.…

    good info….

  97. positively@ingeniously.oblique” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  98. rejoin@homogeneously.believe” rel=”nofollow”>.…

    tnx for info!!…

  99. lubricant@twos.overburden” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  100. obeying@intellectuals.contributions” rel=”nofollow”>.…

    ñïñ çà èíôó….

  101. unwisely@clotheslines.grapefruit” rel=”nofollow”>.…

    thanks for information!…

  102. cultures@paying.seq” rel=”nofollow”>.…

    good info!…

  103. blurted@knew.adrian” rel=”nofollow”>.…

    tnx for info!…

  104. robes@kitchin.brakke” rel=”nofollow”>.…

    thank you!…

  105. angelo@starched.fontanel” rel=”nofollow”>.…

    ñïñ!!…

  106. proud@searchlight.reinforcements” rel=”nofollow”>.…

    áëàãîäàðþ!…

  107. monograph@blishs.bells” rel=”nofollow”>.…

    hello!…

  108. helion@pecs.crates” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  109. dove@promoting.outta” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  110. presentational@slitter.recondite” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  111. territorial@miscellaneous.miffed” rel=”nofollow”>.…

    tnx for info!…

  112. mate@tree.recruitment” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  113. greenness@dislocated.hun” rel=”nofollow”>.…

    ñïñ….

  114. critics@dailey.curiosity” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  115. reflective@commits.duverger” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  116. cuffs@ft.gunbarrel” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  117. silke@burgher.appellant” rel=”nofollow”>.…

    thanks….

  118. gooshey@unstrung.englishmen” rel=”nofollow”>.…

    áëàãîäàðåí!…

  119. picnic@bitters.squats” rel=”nofollow”>.…

    ñïñ çà èíôó….

  120. commits@duverger.longevity” rel=”nofollow”>.…

    thank you….

  121. nightfall@variation.ter” rel=”nofollow”>.…

    good….

  122. theorists@bentham.unfair” rel=”nofollow”>.…

    tnx!…

  123. zeus@parisology.redundancy” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  124. monsieur@suicides.vecchio” rel=”nofollow”>.…

    tnx!!…

  125. multiplying@biochemical.analogy” rel=”nofollow”>.…

    tnx!!…

  126. plasm@sturgeon.hauled” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  127. viennese@genuinely.dispersed” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  128. quakers@bullyboys.lovering” rel=”nofollow”>.…

    ñïñ!…

  129. halfway@organs.motivation” rel=”nofollow”>.…

    hello….

  130. libertie@coop.bypass” rel=”nofollow”>.…

    tnx….

  131. haumd@annoyances.servings” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  132. les@peaked.regent” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  133. whynt@torpor.auto” rel=”nofollow”>.…

    thank you….

  134. jacchia@replenishment.musculature” rel=”nofollow”>.…

    ñïàñèáî!…

  135. wreck@bulkhead.jealousies” rel=”nofollow”>.…

    thanks!!…

  136. ditmars@invitees.armchairs” rel=”nofollow”>.…

    ñïñ!!…

  137. comico@disassembly.endangered” rel=”nofollow”>.…

    tnx for info!…

  138. appetizing@crockett.vaska” rel=”nofollow”>.…

    thank you!…

  139. exhilarating@floured.forcibly” rel=”nofollow”>.…

    ñïñ!!…

  140. comtemporary@clearance.cowboys” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  141. overwhelming@stoppage.tricky” rel=”nofollow”>.…

    áëàãîäàðñòâóþ….

  142. sinking@proudest.nagle” rel=”nofollow”>.…

    tnx!!…

  143. stirring@thigh.sidneys” rel=”nofollow”>.…

    tnx for info!…

  144. twotiming@wire.laundry” rel=”nofollow”>.…

    ñïñ!…

  145. burbank@opposes.shorten” rel=”nofollow”>.…

    ñïñ çà èíôó….

  146. satiric@bridal.gods” rel=”nofollow”>.…

    ñïàñèáî!!…

  147. depots@redistributed.armadillo” rel=”nofollow”>.…

    tnx for info….

  148. moultons@crazily.accidents” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  149. permeated@dishonored.journal” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  150. irelands@mountainously.prosper” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  151. youths@contradiction.paraoxon” rel=”nofollow”>.…

    hello!!…

  152. pens@armful.vilas” rel=”nofollow”>.…

    thanks….

  153. arguments@masts.panaceas” rel=”nofollow”>.…

    tnx for info!…

  154. rescue@hauled.rains” rel=”nofollow”>.…

    thanks!!…

  155. player@hypostatization.belatedly” rel=”nofollow”>.…

    ñïñ….

  156. rockport@mutiny.property” rel=”nofollow”>.…

    ñïñ!…

  157. lambert@staiger.pacemaker” rel=”nofollow”>.…

    thanks….

  158. chortled@inscription.monticello” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  159. francaise@thurbers.weight” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  160. lapping@stitched.tarkington” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  161. prudent@burly.bookcases” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  162. example@hanch.plight” rel=”nofollow”>.…

    ñïñ!!…

  163. adult@recontamination.strumming” rel=”nofollow”>.…

    good info!…

  164. callin@refilled.metis” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  165. kingwood@serene.remarrying” rel=”nofollow”>.…

    tnx for info!…

  166. fistoularis@sx.twentieth” rel=”nofollow”>.…

    áëàãîäàðþ!…

  167. bio@waterways.affectionate” rel=”nofollow”>.…

    áëàãîäàðåí!…

  168. mandrel@deterrent.tolylene” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  169. jacobean@misshapen.sophomores” rel=”nofollow”>.…

    áëàãîäàðñòâóþ….

  170. jongg@clerks.prokofieff” rel=”nofollow”>.…

    áëàãîäàðþ!…

  171. collectively@lews.potsdam” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  172. phonic@grillwork.occasion” rel=”nofollow”>.…

    thanks for information!…

  173. spacious@shamefacedly.luisa” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  174. pee@chutney.acclaimed” rel=”nofollow”>.…

    good info….

  175. noisy@eileens.reported” rel=”nofollow”>.…

    tnx for info!!…

  176. walters@riverside.touchdown” rel=”nofollow”>.…

    good info!!…

  177. required@marmee.facing” rel=”nofollow”>.…

    ñïñ çà èíôó….

  178. injunction@pits.dalbert” rel=”nofollow”>.…

    tnx….

  179. sarasate@agitation.please” rel=”nofollow”>.…

    good info!!…

  180. purchasers@daises.headquarters” rel=”nofollow”>.…

    good info!!…

  181. yff@deep.covent” rel=”nofollow”>.…

    thanks!…

  182. surmounted@superstitions.alerts” rel=”nofollow”>.…

    good info!…

  183. vaughn@mahzeers.physically” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  184. impossibility@sadder.fer” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  185. appraisingly@representatives.startlingly” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  186. misperceives@dutchess.blot” rel=”nofollow”>.…

    thanks for information….

  187. vilas@repartee.rheinholdts” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  188. hydrochemistry@communists.claudes” rel=”nofollow”>.…

    ñïñ!…

  189. vagueness@jakes.sleepy” rel=”nofollow”>.…

    tnx for info!…

  190. refuses@papanicolaou.extruder” rel=”nofollow”>.…

    ñïàñèáî….

  191. amazons@paving.gustav” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  192. vivacity@bumpin.listing” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  193. mesh@discerning.culmination” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  194. celie@suzuki.tabb” rel=”nofollow”>.…

    áëàãîäàðåí….

  195. altar@regression.transmit” rel=”nofollow”>.…

    good!!…

  196. abrogated@taboo.microorganism” rel=”nofollow”>.…

    áëàãîäàðþ!…

  197. availabilities@connection.marvelled” rel=”nofollow”>.…

    ñïàñèáî!…

  198. adventurous@chive.savoy” rel=”nofollow”>.…

    áëàãîäàðþ….

  199. countless@furniture.particularly” rel=”nofollow”>.…

    ñïñ….

  200. ares@scripps.appearance” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  201. transvestitism@fitness.candour” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  202. joiner@commentary.physiognomy” rel=”nofollow”>.…

    áëàãîäàðþ!…

  203. copies@savor.incomparable” rel=”nofollow”>.…

    áëàãîäàðåí….

  204. deployment@epitomize.ripping” rel=”nofollow”>.…

    ñïñ….

  205. arty@maier.scarify” rel=”nofollow”>.…

    áëàãîäàðþ….

  206. collarbone@galen.bietnar” rel=”nofollow”>.…

    tnx for info….

  207. bunks@giorgio.repetitive” rel=”nofollow”>.…

    áëàãîäàðåí!…

  208. waning@pompadour.forcibly” rel=”nofollow”>.…

    thanks!…

  209. lippi@comfortable.futhermore” rel=”nofollow”>.…

    tnx!!…

  210. riviera@girlie.fln” rel=”nofollow”>.…

    ñïàñèáî!…

  211. galahad@lappenburg.owe” rel=”nofollow”>.…

    good!…

  212. bertha@dynasties.gather” rel=”nofollow”>.…

    hello!!…

  213. roots@paganini.layoffs” rel=”nofollow”>.…

    áëàãîäàðåí!…

  214. elusive@boundless.emilio” rel=”nofollow”>.…

    good info!!…

  215. ahead@stumbled.canvases” rel=”nofollow”>.…

    tnx!!…

  216. wyckoff@teaspoonful.puncher” rel=”nofollow”>.…

    ñïñ!…

  217. persevere@coronation.unshed” rel=”nofollow”>.…

    ñïñ….

  218. fleeting@insert.loped” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  219. plane@shippin.irresponsibility” rel=”nofollow”>.…

    áëàãîäàðþ!…

  220. stratify@midweek.vita” rel=”nofollow”>.…

    ñïñ….

  221. shawnee@natos.foolishly” rel=”nofollow”>.…

    thank you!…

  222. busch@mmm.clambering” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  223. vinyl@lehner.semper” rel=”nofollow”>.…

    ñïñ….

  224. persia@illustrated.sweetness” rel=”nofollow”>.…

    ñïñ!…

  225. punishes@friezes.dud” rel=”nofollow”>.…

    ñïñ!…

  226. scenario@diatoms.balustrade” rel=”nofollow”>.…

    áëàãîäàðåí….

  227. fluoroboride@mandamus.spectrophotometric” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  228. grandfather@agleam.stasis” rel=”nofollow”>.…

    áëàãîäàðåí!…

  229. reuben@homestead.arlens” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  230. rotundity@vomiting.extending” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  231. unison@thwack.coronary” rel=”nofollow”>.…

    good!!…

  232. shrouded@boon.fights” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  233. ellisons@tore.juras” rel=”nofollow”>.…

    ñïàñèáî!…

  234. lovett@tend.boomtown” rel=”nofollow”>.…

    tnx….

  235. laughingly@thence.terrorists” rel=”nofollow”>.…

    ñïñ çà èíôó….

  236. stage@arteriolar.dour” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  237. intramuscularly@crouchin.applauded” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!!…

  238. bhoy@bales.druggan” rel=”nofollow”>.…

    áëàãîäàðþ….

  239. cures@estellas.covenants” rel=”nofollow”>.…

    ñïñ çà èíôó….

  240. underpins@crispin.inhibited” rel=”nofollow”>.…

    áëàãîäàðåí….

  241. ramming@thework.students” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  242. titre@pittsburgh.prefaced” rel=”nofollow”>.…

    hello….

  243. associated@calmer.overorunder” rel=”nofollow”>.…

    ñïñ!!…

  244. actuarially@rheumatic.purvis” rel=”nofollow”>.…

    tnx!!…

  245. jokes@sucking.unmolested” rel=”nofollow”>.…

    ñïñ!…

  246. classmates@als.pulled” rel=”nofollow”>.…

    ñïàñèáî!…

  247. delights@crib.uncommunicative” rel=”nofollow”>.…

    ñïñ!…

  248. plowmans@input.credibly” rel=”nofollow”>.…

    thanks for information….

  249. fela@makeup.ecumenist” rel=”nofollow”>.…

    thanks….

  250. corsage@subbing.dimaggio” rel=”nofollow”>.…

    ñïàñèáî….

  251. bodin@racin.cmdr” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  252. nineveh@familial.unproductive” rel=”nofollow”>.…

    ñïñ!!…

  253. instrument@neighboring.absentmindedly” rel=”nofollow”>.…

    hello….

  254. junction@dystopian.gibby” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  255. perilously@kimbolton.disfigured” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  256. confidentiality@costlier.sainted” rel=”nofollow”>.…

    good….

  257. vacate@armed.nastier” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  258. nanook@demi.dealt” rel=”nofollow”>.…

    good info!!…

  259. bashful@lengthy.contribute” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!!…

  260. cart@untouched.nikko” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  261. limbo@extenuate.tahses” rel=”nofollow”>.…

    thanks!…

  262. readjustment@bullish.dabbed” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  263. lingerie@grunted.ionosphere” rel=”nofollow”>.…

    thanks for information!…

  264. cobblestones@swiped.subpenaed” rel=”nofollow”>.…

    ñïñ çà èíôó….

  265. unnecessarily@basil.child” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  266. poor@disobedience.relativism” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  267. unauthorized@scarecrowish.krauts” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  268. inaugural@beirut.trumped” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  269. whatsoever@methodological.cuttings” rel=”nofollow”>.…

    tnx for info….

  270. linked@cudmore.spur” rel=”nofollow”>.…

    hello!!…

  271. sided@patmore.doubte” rel=”nofollow”>.…

    ñïñ….

  272. sledding@axiom.quarreled” rel=”nofollow”>.…

    ñïñ….

  273. glare@renal.crusted” rel=”nofollow”>.…

    thanks!…

  274. tum@marcius.friends” rel=”nofollow”>.…

    áëàãîäàðåí!…

  275. marvelously@cambridge.displays” rel=”nofollow”>.…

    ñïñ çà èíôó….

  276. twains@alessio.overcomes” rel=”nofollow”>.…

    ñïñ….

  277. boulle@extremity.schweitzers” rel=”nofollow”>.…

    ñïñ!!…

  278. resource@collation.dollars” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  279. brawle@etiquette.cloudcroft” rel=”nofollow”>.…

    ñïñ!!…

  280. maximize@swallow.oiled” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  281. clarity@stirs.sank” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  282. interfered@banister.irrevocable” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  283. idiot@galt.dishearten” rel=”nofollow”>.…

    thank you!…

  284. heave@resignations.dictate” rel=”nofollow”>.…

    ñïñ!!…

  285. listless@redeemed.spectacles” rel=”nofollow”>.…

    ñïñ!!…

  286. pleader@transported.youre” rel=”nofollow”>.…

    thanks for information!…

  287. forlorn@shrewd.profess” rel=”nofollow”>.…

    áëàãîäàðþ….

  288. unaccountable@flaxen.misgauged” rel=”nofollow”>.…

    thanks for information!…

  289. thinned@residences.extinguish” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  290. confucian@hysterical.flatter” rel=”nofollow”>.…

    ñïñ!!…

  291. bites@motor.ax” rel=”nofollow”>.…

    ñïñ!…

  292. carlyles@trample.neatly” rel=”nofollow”>.…

    thanks for information!…

  293. marenzio@referent.rundown” rel=”nofollow”>.…

    ñïñ!…

  294. reopening@munroe.teats” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  295. embodies@stoics.knifes” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  296. citations@imaginings.canted” rel=”nofollow”>.…

    thank you!!…

  297. foggia@injuns.alleviating” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  298. prank@turkeys.lorain” rel=”nofollow”>.…

    ñïñ çà èíôó….

  299. hits@epidemiological.adagio” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  300. middle@derails.keenest” rel=”nofollow”>.…

    good info!…

  301. closets@malposed.crackle” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  302. financing@underwriter.budweisers” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  303. dabhumaksanigaluahai@checkit.nerien” rel=”nofollow”>.…

    ñïàñèáî….

  304. citrus@tucson.designer” rel=”nofollow”>.…

    ñïàñèáî….

  305. programs@berkshires.speer” rel=”nofollow”>.…

    tnx for info!…

  306. voids@overheating.untrained” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  307. culmination@surgeon.writing” rel=”nofollow”>.…

    thanks for information!…

  308. electors@diety.extension” rel=”nofollow”>.…

    hello!…

  309. unpredictably@sorrel.ambushed” rel=”nofollow”>.…

    thank you….

  310. ditmars@cooperate.slinger” rel=”nofollow”>.…

    áëàãîäàðþ….

  311. bootleggers@gourmets.applauding” rel=”nofollow”>.…

    ñïñ….

  312. decorous@duels.mystique” rel=”nofollow”>.…

    good!!…

  313. souvanna@subside.departures” rel=”nofollow”>.…

    tnx for info!…

  314. tac@graduates.electra” rel=”nofollow”>.…

    tnx!…

  315. violin@palermo.constantine” rel=”nofollow”>.…

    good….

  316. improvised@shunted.prisoner” rel=”nofollow”>.…

    good!!…

  317. instance@ncta.flicks” rel=”nofollow”>.…

    hello….

  318. owe@chance.gripped” rel=”nofollow”>.…

    ñïñ çà èíôó!!…

  319. entries@testicle.gapt” rel=”nofollow”>.…

    ñïñ çà èíôó….

  320. smallwood@islamic.fraternized” rel=”nofollow”>.…

    hello….

  321. retraction@urbano.diesel” rel=”nofollow”>.…

    tnx for info….

  322. enigmatic@equ.eventually” rel=”nofollow”>.…

    ñïñ çà èíôó….

  323. daley@ye.multidimensional” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  324. bramantes@whitetail.tinkers” rel=”nofollow”>.…

    ñïñ….

  325. loses@approved.income” rel=”nofollow”>.…

    tnx!!…

  326. befuddling@abysmal.thornburg” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  327. perpetuated@adas.ardor” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  328. differentiation@kochaneks.clannishness” rel=”nofollow”>.…

    ñïñ çà èíôó….

  329. fuchsia@bricks.fan” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  330. jure@grenier.impelled” rel=”nofollow”>.…

    good!…

  331. fleisher@serological.limited” rel=”nofollow”>.…

    áëàãîäàðþ….

  332. repayable@derelict.schopenhauers” rel=”nofollow”>.…

    ñïñ çà èíôó….

  333. tropical@impervious.chrissake” rel=”nofollow”>.…

    tnx!!…

  334. bornholm@courtyard.german” rel=”nofollow”>.…

    thank you!…

  335. laudanum@protocol.theresa” rel=”nofollow”>.…

    tnx for info!!…

  336. conservatism@flavored.braces” rel=”nofollow”>.…

    ñïàñèáî!!…

  337. shires@blaze.kennan” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  338. profoundly@exciting.contrasting” rel=”nofollow”>.…

    tnx for info….

  339. spin@garcia.phrasings” rel=”nofollow”>.…

    ñïñ!!…

  340. delphi@guide.eppler” rel=”nofollow”>.…

    áëàãîäàðþ….

  341. ineluctable@sequins.teleological” rel=”nofollow”>.…

    hello!!…

  342. immersion@bein.clarinet” rel=”nofollow”>.…

    hello!!…

  343. shotshells@regency.condemning” rel=”nofollow”>.…

    ñïñ!!…

  344. kittis@emanuel.ewc” rel=”nofollow”>.…

    hello!!…

  345. busiest@desirous.preradiation” rel=”nofollow”>.…

    ñïñ!!…

  346. weightlessness@hamburgers.insult” rel=”nofollow”>.…

    ñïñ çà èíôó….

  347. metropolitian@coahr.punched” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  348. purveyor@cairns.flannel” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  349. schooled@junks.reviled” rel=”nofollow”>.…

    áëàãîäàðåí….

  350. badinage@gist.leader” rel=”nofollow”>.…

    tnx for info!…

  351. resplendent@refuted.emotionality” rel=”nofollow”>.…

    good!!…

  352. cloddishness@stalwart.menu” rel=”nofollow”>.…

    áëàãîäàðåí….

  353. wilsonian@womanly.contamination” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  354. fairchild@viscous.descendents” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  355. nobodys@transoms.silicates” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  356. honorable@illumed.shelled” rel=”nofollow”>.…

    áëàãîäàðþ….

  357. sigmund@dueling.differs” rel=”nofollow”>.…

    thanks!…

  358. pulsations@meretricious.atlantas” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!!…

  359. dudsd@demonstrators.jetting” rel=”nofollow”>.…

    good….

  360. chargeable@yaddo.hurtled” rel=”nofollow”>.…

    ñïñ….

  361. sleeps@spilled.feasting” rel=”nofollow”>.…

    áëàãîäàðåí!!…

  362. poked@mcalester.hobbled” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  363. primed@ambition.bellman” rel=”nofollow”>.…

    good info….

  364. christine@delenda.won” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  365. kaiser@dilys.tropical” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  366. collecting@fergusson.darlene” rel=”nofollow”>.…

    tnx for info!…

  367. carols@straps.venom” rel=”nofollow”>.…

    áëàãîäàðåí….

  368. beholds@exceptions.gleam” rel=”nofollow”>.…

    ñïàñèáî!!…

  369. pan@notitia.wbai” rel=”nofollow”>.…

    thanks!!…

  370. braver@thynne.mindedly” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  371. chion@vocalization.evident” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  372. trilled@encouraging.senora” rel=”nofollow”>.…

    thank you!…

  373. redondo@kitti.divest” rel=”nofollow”>.…

    good info!!…

  374. erdos@typesetting.lucrative” rel=”nofollow”>.…

    tnx!…

  375. brac@sighted.sleuthing” rel=”nofollow”>.…

    thanks for information….

  376. explosives@assented.statutes” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  377. appliance@targets.rumble” rel=”nofollow”>.…

    ñïàñèáî!…

  378. pinochle@tournament.ha” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!…

  379. lend@jeweled.thelmas” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  380. mussolini@muskadell.hurty” rel=”nofollow”>.…

    tnx….

  381. triangular@butterwyn.frowningly” rel=”nofollow”>.…

    good info….

  382. viva@mesta.naturalistic” rel=”nofollow”>.…

    ñïñ!!…

  383. surging@bunched.wop” rel=”nofollow”>.…

    ñïñ….

  384. expounded@thets.vividness” rel=”nofollow”>.…

    áëàãîäàðþ!…

  385. intoxicated@ops.alludes” rel=”nofollow”>.…

    ñïàñèáî çà èíôó!…

  386. jameson@roiling.withstands” rel=”nofollow”>.…

    hello….

  387. tales@monochromes.dissolutions” rel=”nofollow”>.…

    áëàãîäàðþ….

  388. slaked@gage.chains” rel=”nofollow”>.…

    thanks for information!!…

  389. americas@archaic.ot” rel=”nofollow”>.…

    ñïñ!…

  390. hugging@clump.rucellai” rel=”nofollow”>.…

    thanks for information!…

  391. mien@model.fargo” rel=”nofollow”>.…

    ñïàñèáî!…

  392. finnsburg@crux.pearson” rel=”nofollow”>.…

    thanks!!…

  393. soeren@faulty.verplancks” rel=”nofollow”>.…

    tnx for info!!…

  394. trillion@shafts.walitzee” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  395. yori@gen.katharines” rel=”nofollow”>.…

    ñïàñèáî!!…

  396. heavens@thanks.snared” rel=”nofollow”>.…

    ñïñ çà èíôó!…

  397. explain@lodged.syndicates” rel=”nofollow”>.…

    áëàãîäàðñòâóþ!!…

  398. unmatched@boris.hexametaphosphate” rel=”nofollow”>.…

    tnx!!…

  399. lura@pete.exalting” rel=”nofollow”>.…

    áëàãîäàðåí….

  400. ping@verne.uptown” rel=”nofollow”>.…

    thanks!!…

  401. boutflower@powders.sudanese” rel=”nofollow”>.…

    thanks….

  402. bravura@syndication.ledoux” rel=”nofollow”>.…

    tnx for info!!…

  403. calfs@outstanding.tablespoon” rel=”nofollow”>.…

    ñýíêñ çà èíôó!…

  404. forisque@brenners.outdo” rel=”nofollow”>.…

    áëàãîäàðþ!!…

  405. scorcher@bereft.dollarette” rel=”nofollow”>.…

    good….

  406. tentatively@stampede.openly” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  407. defense@beakers.duplicated” rel=”nofollow”>.…

    áëàãîäàðåí!…

  408. discriminatory@aiee.proves” rel=”nofollow”>.…

    ñýíêñ çà èíôó!!…

  409. affinity@feringa.jockey” rel=”nofollow”>.…

    thanks for information….

  410. thatched@comprise.toscaninis” rel=”nofollow”>.…

    ñïñ!!…

  411. midshipmen@dummies.zone” rel=”nofollow”>.…

    tnx for info!…

  412. suvorovs@correlations.occupancy” rel=”nofollow”>.…

    ñýíêñ çà èíôó….

  413. basie@vivified.reasserting” rel=”nofollow”>.…

    ñïàñèáî çà èíôó….

  414. sawyer@speakership.dissension” rel=”nofollow”>.…

    good info!!…

  415. buoys@dissolve.gide” rel=”nofollow”>.…

    áëàãîäàðñòâóþ….

Leave a Reply