Yet it would also be egotistical to expect to win in a game with Serdoa, Seven, Kyan, Thoth and Ichabod (with novice as dedlurker). Can't have it both ways.
|
[SPOILERS] Krill smokes some weed - PBEM50
|
|
Also, thanks to simulation found a decent opening build. Kinda risky though, but that's inherent to not having a plains hill (worker>grow to 2 on warrior has so much utility).
Pictures aren't showing up on my phone, anyone else having trouble?
Completed: RB Demogame - Gillette, PBEM46, Pitboss 13, Pitboss 18, Pitboss 30, Pitboss 31, Pitboss 38, Pitboss 42, Pitboss 46, Pitboss 52 (Pindicator's game), Pitboss 57
In progress: Rimworld
May 26th, 2013, 11:31
(This post was last modified: May 26th, 2013, 11:32 by Fintourist.)
Btw, you could add the link to your blog into your signature (or let PBEM50-signature lead directly to it). It's just really about one extra click and a second of browsing but...
May 26th, 2013, 11:52
(This post was last modified: May 26th, 2013, 11:52 by Fintourist.)
(May 26th, 2013, 11:33)Krill Wrote: Would it make more sense to link to the turn report index? I don't know, my forum behavior goes something like this: 1. I check "Civilization" or e.g "Play by Email" forum overview 2. I notice an interesting update by someone 3. I click the link to the particular post This time the procedure led me to your "updated" post and I just wondered how do I get to read the latest update in the easiest way.  Anyways, I'm sure I'll find my way via turn report index just fine so no worries. Probably it makes more sense for a reader who wants to catch up e.g couple of turns that he/she has missed.
OK, what I'm going to do then is every time I post a turn report, I'll post here to confirm the update and give a link to the specific turn report.
One issue is that in the future I may end up reporting multiple games on the blog, so I want to make it possible for a lurker to read the turn reports to a specific game, even if they are disallowed from reading the reports to other games. I think giving specific links in updated posts, and a turn report index should solve that issue. |
