Re: Olympia Turn Length

From: cedman@714-725-3177.nts.uci.edu (Carl Edman)

Date: Sat, 30 May 1992 02:45:20 +0000

Well, while we are talking about significant changes to
the update schedule and as my previous suggestions have
proven so popular :-), let me throw in my favorite
solution to this problem: Do away with the artificial
updates completely (or at least as far as reasonably
possible).

This may sound drastic, but I think would not involve that
many actual code changes. What in effect would happen is
that there would be a mini-update (let's say 4 days to a
week, to suit the tastes on pace) every single night.

If anything of interest happend to a player he would have
the update report in the morning. The actual update
report would of course have to be shrunk a lot. Much of the
information in the update report would move to server
requestable files and some redundancy would have to be
removed. An actual update report would not have to be
longer than a page at most (if any is generated at all).

For this to work it would of course also be necessary to
automate the turn processing further - nobody can expect
Rich to spend _every_ night doing update reports by hand.

Another advantage of this change would be that a
programing language for Olympia would become much less
of an issue. If you can correct orders by hand every few
days there is no need for lots of complicated conditional
commands.

Nothing would prevent players who preferred the old
style to continue to send in orders once a week or even only
once a month. They could even get an option to send them
update reports only that frequently. But players which
prefer a more interactive game could take advantage of
this change.

Does _anybody_ agree ?

Carl Edman, BtA [801]

References

Olympia Turn Length
M22367@mwvm.mitre.org
Fri, 29 May 1992 18:59:52 +0000

Referenced By

Olympia Turn Length
M22367@mwvm.mitre.org
Fri, 29 May 1992 18:59:52 +0000