votings

LT18/LTXVIII - disable the Great Library in case of no diplomacy?

What to do with the GL in case of no diplomacy?

The Great Library is already overpowered in big games, even if you can counter it by a tech trading alliance.

no
67% (6 votes)
yes
33% (3 votes)
Total voters: 9

LTXVIII - techlosing

This is a revote on Maho's tech losing patch.

  1. tlgive=90,tlrecv=30 (write-in) (60%)
  2. tlgive=0,tlrecv=0: (current setting - no tech is lost when transferring), tlgive=0,tlrecv=100: (tech cannot be stolen from you)
  3. tlgive=90,tlrecv=10 (write-in)
  4. tlgive=100,tlrecv=0: (you lose the tech when it is stolen from you), tlgive=100,tlrecv=100: (you both lose the tech when it is stolen)
Total voters: 10

LTXVIII - decrease steepness (# of mountains/hills)

I suggest decreasing the # of mountains and hills. The current value of steepness is 30 (30% ?) which I think is too high.

  1. 30 (58.3%)
  2. 20, 60 (write-in)
  3. 10
  4. 33 (write-in), 50 (write-in)
Total voters: 12

LTXVIII - Increase fortress build time.

I suggest we scale fortress build time to compensate for the increased unit movement rates in longturn.

  1. 9 (58.3%)
  2. 6
  3. 12
  4. 3
Total voters: 12

LTXVIII set diplomacy

What should the diplomacy setting be for LTXVIII?

0 = diplomacy is enabled.
4 = diplomacy is disabled.

Poll deadline: 2010-01-24

4 = diplomacy is disabled.
82% (9 votes)
0 = diplomacy is enabled.
18% (2 votes)
Total voters: 11

LTXVIII - Alter the effect of the Eiffel Tower wonder.

I suggest we alter the effect of Eiffel Tower because it is currently unused in longturn games.

Yes
75% (9 votes)
No
25% (3 votes)
Total voters: 12

password sharing - what to do with Kryon and Dev

# (zgrep " lt" /var/log/xxxxxx.gz;grep " lt" /var/log/yyyyyyyy ;grep " lt" /var/log/zzzzzzz) | egrep -i "(kryon|dev): connected"| perl -pe "s/^(\w+\s*\d+\s*\d+:\d+:\d+).*\s(lt[\w\d]+):.*\(\d+\) (\w+): connected \[(.*)\]/\4 | \1 | \3 | \2 /" | sort
c-68-38-24-164.hsd1.pa.comcast.net | Dec 28 22:01:29 | Kryon | ltxvii
c-68-38-24-164.hsd1.pa.comcast.net | Dec 29 01:11:18 | Kryon | ltxvi
c-68-38-24-164.hsd1.pa.comcast.net | Dec 29 02:39:22 | Kryon | ltxvii
c-68-38-24-164.hsd1.pa.comcast.net | Dec 29 20:58:46 | Kryon | ltxvii
c-68-38-24-164.hsd1.pa.comcast.net | Dec 29 21:13:21 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Dec 30 13:47:33 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Dec 30 13:48:12 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Dec 31 02:11:27 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Dec 31 02:20:49 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Dec 31 02:39:57 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Dec 31 17:21:48 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Dec 31 17:24:43 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 03:38:23 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 03:48:06 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 04:20:27 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 06:14:39 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 08:28:41 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 16:13:01 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 16:18:38 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 1 19:29:53 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 04:32:49 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 04:37:10 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 11:17:00 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 11:17:30 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 11:28:53 | dev | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 11:29:11 | dev | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 16:54:51 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 2 16:55:50 | dev | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 3 07:15:37 | Kryon | ltxvii
c-68-50-171-21.hsd1.md.comcast.net | Jan 3 07:20:36 | Kryon | ltxvi
c-68-50-171-21.hsd1.md.comcast.net | Jan 3 07:44:26 | Kryon | ltxvi
c-68-57-156-168.hsd1.va.comcast.net | Dec 27 22:31:22 | dev | ltxvii
c-68-57-156-168.hsd1.va.comcast.net | Dec 30 00:18:31 | dev | ltxvii
c-68-57-156-168.hsd1.va.comcast.net | Jan 1 00:28:12 | dev | ltxvii
c-68-57-156-168.hsd1.va.comcast.net | Jan 2 04:46:55 | dev | ltxvii
c-68-57-156-168.hsd1.va.comcast.net | Jan 3 00:07:03 | dev | ltxvii
c-68-57-156-168.hsd1.va.comcast.net | Jan 4 03:40:09 | dev | ltxvii
c-68-57-156-168.hsd1.va.comcast.net | Jan 4 23:26:06 | dev | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 4 02:36:05 | Kryon | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 4 02:48:10 | Kryon | ltxvi
c-98-218-116-105.hsd1.md.comcast.net | Jan 4 03:11:37 | Kryon | ltxvi
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 01:19:07 | Kryon | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 01:20:47 | Kryon | ltxvi
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 02:25:36 | Kryon | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 02:26:19 | Kryon | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 09:52:01 | Kryon | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 09:54:27 | Kryon | ltxvi
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 12:25:54 | Kryon | ltxvi
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 12:56:04 | Kryon | ltxvii
c-98-218-116-105.hsd1.md.comcast.net | Jan 5 16:23:35 | Kryon | ltxvi

It's evident cheating.

What should we do with Kryon and Dev?

Voting time: 5 days

  1. nothing (62.5%)
  2. remove from LT XVI and LTXVII
  3. remove from LTXVII
  4. make a site rule on penalties first
  5. Put Kryon in his own team of 1 (write-in), suspend both from 1 next game or prevent a couple turns from this game :-) (write-in), other, remove Dev from site, remove Kryon from site, remove Dev from LT XVI and LT XVII, remove Kryon from LT XVI and LT XVII, remove from site
Total voters: 16

Site rules - starting team game with incomplete teams

Proposition of new rule:

13. when team game start time arrives, and teams are still incomplete, administrator will remove players who make team conflicts or are not members of any team, in following order:
a. players which are without team,
b. those players, removal of which will make 2 or more teams conflict resolved (conflicting players).
c. if there is more than one conflicting player for given conflict - administrator has right to choose which one will be removed.
c. if (b) won't elimitnate all conflicts - remaining players which are member of conflicting teams.
14. list of players mentioned in previous point will be sent as a comment to game node, day before removal.
15. game start date will be announced in one week advance or sooner.

yes
67% (8 votes)
no
33% (4 votes)
Total voters: 12

LTXVII - Starting units - number of settlers

(Question and options modified by Maho)
I suggest we decrease the number of starting settlers in LTXVII.

  1. ccwwxx (61.5%)
  2. ccwwx (write-in)
  3. cwwxx
  4. ccccwwxx
  5. cwxxxxxx (write-in)
  6. cccccwwx
  7. cccwwxx
Total voters: 15

LTXVII set diplomacy

What should the diplomacy setting be for LTXVII?

  1. =3 (73.3%)
  2. =0, =4
Total voters: 15
Syndicate content