Bill (aka gocrawford) has created a comprehensive unit and terrain pdf guide, based on the information available on the wiki. Looks really good and is certainly a handy tool for every strategist – Download the pdf.
This entry was written by alex and posted on July 4, 2007 at 13:29 and filed under Uncategorized with tags Tips. Bookmark the permalink. Follow any comments here with the RSS feed for this post. Comments are closed, but you can leave a trackback: Trackback URL.
Looks good! But are the terrain effects accurate? They don’t seem to mesh with what is seen when you mouseover things in the game. For example, I thought putting Raiders in forests gives better defense against infantry.
I’d really like to know which Java basic infrastructure design you chose, since I’m deciding between pure stateless (POJOs with Struts 2.0 on Tomcat) and stateful (EJB 3.0 via SEAM on JBoss) for a major application refactoring. I’m impressed with WeeWar and would welcome a quick email on the architecture you chose. I’m leery of re-entering the EJB world. Thanks.
@odupont It should be working now. Took some time to allow free trials to players who previously had pro. Let us know if it doesn't work now 1 year ago
All trial players can now get a FREE 3-month pro subscription! Current pros get an automatic 3-mo. extension! http://ow.ly/1Wut91 year ago
Bill (aka gocrawford) has created a comprehensive unit and terrain pdf guide, based on the information available on the wiki. Looks really good and is certainly a handy tool for every strategist – Download the pdf.
4 Comments
Looks good! But are the terrain effects accurate? They don’t seem to mesh with what is seen when you mouseover things in the game. For example, I thought putting Raiders in forests gives better defense against infantry.
Well, doesn’t it? The less dots, the worse for you (actually for the unit occupying a hex):>
Alex,
I’d really like to know which Java basic infrastructure design you chose, since I’m deciding between pure stateless (POJOs with Struts 2.0 on Tomcat) and stateful (EJB 3.0 via SEAM on JBoss) for a major application refactoring. I’m impressed with WeeWar and would welcome a quick email on the architecture you chose. I’m leery of re-entering the EJB world. Thanks.
Would anyone be so kind as to update the PDF? It’s immensely handy :)