·Imhotep·
Legendary Builder
Ladies and Gentlemen,
LKendter posted in one of his SGs that he is tired of warfare as being the optimal route to victory. Indeed rushing is a valid and often optimal strategy to get an early landgrab and cripple your opponents. In this SG we're not going that route, but instead are enjoying the good ol' builder's lovefest - lots of wonders and other neat stuff. That does not mean we can't wage war at all, but we'll have a nice restriction on it:
Two World Wonders gain one free war declaration.
If we don't meet this requirement we can only defend ourselves and in any case not cross our borders with our units. The same two World Wonders grant only one free declaration, after a DoW they are obsolete for that purpose.
DM SG etiquette applies.
The use of the BUG Mod version 3.0 or higher (from the SVN) is not mandatory, but recommended.
The game: BtS 3.17
The leader: Ramesses II. of Egypt
The map: mysterious wonderful map
The difficulty: Monarch
The Speed: Normal
Roster duty:
1. Imhotep
2. LKendter
3. ZPVCSPLFUIFDPEF
4. The King of himself
5. berserks01
6. MyOtherCar
Players may apply for a roster spot now, but for this SG I'll not go first come, first serve - please don't be furious if I put another player instead of you on the roster.
Imhotep
LKendter posted in one of his SGs that he is tired of warfare as being the optimal route to victory. Indeed rushing is a valid and often optimal strategy to get an early landgrab and cripple your opponents. In this SG we're not going that route, but instead are enjoying the good ol' builder's lovefest - lots of wonders and other neat stuff. That does not mean we can't wage war at all, but we'll have a nice restriction on it:
Two World Wonders gain one free war declaration.
If we don't meet this requirement we can only defend ourselves and in any case not cross our borders with our units. The same two World Wonders grant only one free declaration, after a DoW they are obsolete for that purpose.
DM SG etiquette applies.
Spoiler DM SG Etiquette :
Alpha: The quality of your report outweighs the quality of your play. We’re here to have fun, and, of course, winning is fun, but losing in style is preferable to a boring win. Remember, your report should be a new reply to alert other players.
Bravo: Reports should be detailed, with plenty of screen shots and player commentary, explanations, musings, etc; an auto-log dump will not suffice. Shots of the F9 screens and overview shots of the empire are nice too, once in a while.
Charlie: Punctuality rocks! “24/48” means post a "got it" within 24 hours of when the last save was posted, and play within 48 hours of that ‘got it.’ Waiting 47 hours to ask for a skip is lame. Punk out two times in a row, and you’ll be dropped from the roster. Skips and swaps are fine, but try to let us know sooner, rather than later.
Delta: Major game decisions (war/peace declarations, religion swaps, city placement, etc) should be arrived at via group consensus.
1. If the team disagrees with you, either argue your case better, or do it their way. Do NOT just blow them off and do it your way because it's your turn.
2. However, if there’s no consensus and you’re up, do it your way and explain why. Conversely, if someone else is up, don't whine when they do it their way.
3. Similarly, overruling techs or city builds is rude and should be done via consensus, barring an emergency.
4. In extraordinary situations, sometimes an opportunity presents itself that the group didn't foresee. If the consequences of it are great, players should stop, and refer the question to the group.
Echo: Being a better player does not give you the right to belittle anyone else or their play. Other people are going to disagree with you on major decisions; get used to the idea, and play nice. If not, take your ball and go home.
Foxtrot: Thread spam is good. Trash talking, poking fun, gentle ribbing, virtual noogies, and generally horsing around are all encouraged, but don’t be rude.
Golf: Automate sparingly.
1. Workers should almost never be automated, except perhaps late-game or building a trade network. However, if you have to, set your game options to “disallow automated worker forest chopping” and “keep previous improvements.”
2. Use of the “Emphasis” buttons is fine, but let the group know and explain your reasoning (specialization is a major game decision). If you prevent growth in a city, let the group know and remind them to take it off. Do NOT let the governor select build orders.
3. Sending units on go-to routes that last beyond your set is acceptable only if they’re heading for a rally point or if you otherwise inform your teammates. NEVER fortify Great People.
Hotel: There is no Hotel.
India: Sign spamming is rude. Signs can be helpful reminders, but too many signs makes them easily ignored. Once a sign is no longer valid, delete it.
Bravo: Reports should be detailed, with plenty of screen shots and player commentary, explanations, musings, etc; an auto-log dump will not suffice. Shots of the F9 screens and overview shots of the empire are nice too, once in a while.
Charlie: Punctuality rocks! “24/48” means post a "got it" within 24 hours of when the last save was posted, and play within 48 hours of that ‘got it.’ Waiting 47 hours to ask for a skip is lame. Punk out two times in a row, and you’ll be dropped from the roster. Skips and swaps are fine, but try to let us know sooner, rather than later.
Delta: Major game decisions (war/peace declarations, religion swaps, city placement, etc) should be arrived at via group consensus.
1. If the team disagrees with you, either argue your case better, or do it their way. Do NOT just blow them off and do it your way because it's your turn.
2. However, if there’s no consensus and you’re up, do it your way and explain why. Conversely, if someone else is up, don't whine when they do it their way.
3. Similarly, overruling techs or city builds is rude and should be done via consensus, barring an emergency.
4. In extraordinary situations, sometimes an opportunity presents itself that the group didn't foresee. If the consequences of it are great, players should stop, and refer the question to the group.
Echo: Being a better player does not give you the right to belittle anyone else or their play. Other people are going to disagree with you on major decisions; get used to the idea, and play nice. If not, take your ball and go home.
Foxtrot: Thread spam is good. Trash talking, poking fun, gentle ribbing, virtual noogies, and generally horsing around are all encouraged, but don’t be rude.
Golf: Automate sparingly.
1. Workers should almost never be automated, except perhaps late-game or building a trade network. However, if you have to, set your game options to “disallow automated worker forest chopping” and “keep previous improvements.”
2. Use of the “Emphasis” buttons is fine, but let the group know and explain your reasoning (specialization is a major game decision). If you prevent growth in a city, let the group know and remind them to take it off. Do NOT let the governor select build orders.
3. Sending units on go-to routes that last beyond your set is acceptable only if they’re heading for a rally point or if you otherwise inform your teammates. NEVER fortify Great People.
Hotel: There is no Hotel.
India: Sign spamming is rude. Signs can be helpful reminders, but too many signs makes them easily ignored. Once a sign is no longer valid, delete it.
The use of the BUG Mod version 3.0 or higher (from the SVN) is not mandatory, but recommended.
The game: BtS 3.17
The leader: Ramesses II. of Egypt
The map: mysterious wonderful map
The difficulty: Monarch
The Speed: Normal
Roster duty:
1. Imhotep
2. LKendter
3. ZPVCSPLFUIFDPEF
4. The King of himself
5. berserks01
6. MyOtherCar
Players may apply for a roster spot now, but for this SG I'll not go first come, first serve - please don't be furious if I put another player instead of you on the roster.
Imhotep