Server Configuration Settings

G

Guest

Guest
Archived from groups: rec.games.empire (More info?)

Could someone briefly point me in the direction as to how to best configure
a server for one update a day at a designated time. Do you leave the
"BLITZ" server option enable?

Thanks, Kelly


--
=================================================================
"One day I will come back, yes, I will come back. Until then, there must be
no regrets, no tears, no anxieties. Just go forward in all your beliefs,
and prove to me that I am correct in mine. Goodbye, Susan."
The Doctor, in "The Dalek Invasion of Earth"
 
Archived from groups: rec.games.empire (More info?)

On Thu, 03 Jun 2004 22:00:12 -0400, Kelly Miller wrote:

> Could someone briefly point me in the direction as to how to best configure
> a server for one update a day at a designated time.

(I'm referring to "econfig" here, not "build.conf" . . .)

To have one update a day at a set time, change update_policy and
uptime_times. For example, for retro:

# 0 - normal, 1 - update_times, 2 - blitz, 3 - demand only
update_policy 1

# Number of ETUs per update
etu_per_update 24

# Times when updates occur under policy #1. Must coincide with schedule.
update_times "13:55"

> Do you leave the "BLITZ" server option enable?

"option BLITZ" just means that food won't be required and BTU's get reset
to the maximum each time the player logs in. Check out "info Options" to
see what all of the options mean.
 
Archived from groups: rec.games.empire (More info?)

Mark Ballinger wrote:

> On Thu, 03 Jun 2004 22:00:12 -0400, Kelly Miller wrote:
>
>> Could someone briefly point me in the direction as to how to best
>> configure a server for one update a day at a designated time.
>
> (I'm referring to "econfig" here, not "build.conf" . . .)
>
> To have one update a day at a set time, change update_policy and
> uptime_times. For example, for retro:
>
> # 0 - normal, 1 - update_times, 2 - blitz, 3 - demand only
> update_policy 1
>
> # Number of ETUs per update
> etu_per_update 24
>
> # Times when updates occur under policy #1. Must coincide with schedule.
> update_times "13:55"
>
>> Do you leave the "BLITZ" server option enable?
>
> "option BLITZ" just means that food won't be required and BTU's get reset
> to the maximum each time the player logs in. Check out "info Options" to
> see what all of the options mean.


Thank you will give it a try! Kelly


--
=================================================================
"One day I will come back, yes, I will come back. Until then, there must be
no regrets, no tears, no anxieties. Just go forward in all your beliefs,
and prove to me that I am correct in mine. Goodbye, Susan."
The Doctor, in "The Dalek Invasion of Earth"
 
Archived from groups: rec.games.empire (More info?)

Mark Ballinger <uesugi@wolfpackempire.com> writes:

> On Thu, 03 Jun 2004 22:00:12 -0400, Kelly Miller wrote:
>
> > Could someone briefly point me in the direction as to how to best configure
> > a server for one update a day at a designated time.
>
> (I'm referring to "econfig" here, not "build.conf" . . .)
>
> To have one update a day at a set time, change update_policy and
> uptime_times. For example, for retro:
>
> # 0 - normal, 1 - update_times, 2 - blitz, 3 - demand only
> update_policy 1
>
> # Number of ETUs per update
> etu_per_update 24
>
> # Times when updates occur under policy #1. Must coincide with schedule.
> update_times "13:55"
>
> > Do you leave the "BLITZ" server option enable?
>
> "option BLITZ" just means that food won't be required and BTU's get reset
> to the maximum each time the player logs in. Check out "info Options" to
> see what all of the options mean.

It also lets players see who's logged in, which is quite inappropriate
for a `real' game.
 
Archived from groups: rec.games.empire (More info?)

Markus Armbruster wrote:

> Mark Ballinger <uesugi@wolfpackempire.com> writes:
>
>> On Thu, 03 Jun 2004 22:00:12 -0400, Kelly Miller wrote:
>>
>> > Could someone briefly point me in the direction as to how to best
>> > configure a server for one update a day at a designated time.
>>
>> (I'm referring to "econfig" here, not "build.conf" . . .)
>>
>> To have one update a day at a set time, change update_policy and
>> uptime_times. For example, for retro:
>>
>> # 0 - normal, 1 - update_times, 2 - blitz, 3 - demand only
>> update_policy 1
>>
>> # Number of ETUs per update
>> etu_per_update 24
>>
>> # Times when updates occur under policy #1. Must coincide with schedule.
>> update_times "13:55"
>>
>> > Do you leave the "BLITZ" server option enable?
>>
>> "option BLITZ" just means that food won't be required and BTU's get reset
>> to the maximum each time the player logs in. Check out "info Options" to
>> see what all of the options mean.
>
> It also lets players see who's logged in, which is quite inappropriate
> for a `real' game.

Kelly Miller wrote:

Ah ha! Is it the "BLITZ" setting then that let's me see who is logged on?

Thanks, Kelly


--
=================================================================
"One day I will come back, yes, I will come back. Until then, there must be
no regrets, no tears, no anxieties. Just go forward in all your beliefs,
and prove to me that I am correct in mine. Goodbye, Susan."
The Doctor, in "The Dalek Invasion of Earth"
 
Archived from groups: rec.games.empire (More info?)

"Kelly Miller" <fkmiller@comcast.net> wrote in message
news:IPKdnb7revxQTF7dRVn-> Kelly Miller wrote:
>
> Ah ha! Is it the "BLITZ" setting then that let's me see who is logged on?
>
> Thanks, Kelly
>
You can always see allies and dieties who are logged in as well
 
Archived from groups: rec.games.empire (More info?)

Kelly Miller wrote:

> Markus Armbruster wrote:
>
>
>>Mark Ballinger <uesugi@wolfpackempire.com> writes:
>>
>>
>>>On Thu, 03 Jun 2004 22:00:12 -0400, Kelly Miller wrote:
>>>
>>>
>>>>Could someone briefly point me in the direction as to how to best
>>>>configure a server for one update a day at a designated time.
>>>
>>>(I'm referring to "econfig" here, not "build.conf" . . .)
>>>
>>>To have one update a day at a set time, change update_policy and
>>>uptime_times. For example, for retro:
>>>
>>># 0 - normal, 1 - update_times, 2 - blitz, 3 - demand only
>>>update_policy 1
>>>
>>># Number of ETUs per update
>>>etu_per_update 24
>>>
>>># Times when updates occur under policy #1. Must coincide with schedule.
>>>update_times "13:55"
>>>
>>>
>>>>Do you leave the "BLITZ" server option enable?
>>>
>>>"option BLITZ" just means that food won't be required and BTU's get reset
>>>to the maximum each time the player logs in. Check out "info Options" to
>>>see what all of the options mean.
>>
>>It also lets players see who's logged in, which is quite inappropriate
>>for a `real' game.
>
>
> Kelly Miller wrote:
>
> Ah ha! Is it the "BLITZ" setting then that let's me see who is logged on?
>
> Thanks, Kelly
>
>

And the BLITZ setting allows use of the "sanc" command.

gz
 
Archived from groups: rec.games.empire (More info?)

Kelly Miller <fkmiller@comcast.net> writes:

> Ah ha! Is it the "BLITZ" setting then that let's me see who is logged on?

Precisely.