1 |
[q]Team stall compensation takes place before overdrive. So a person who only spams cloakers can prevent you from overdriving with your singus.[/q]
|
1 |
[q]Team stall compensation takes place before overdrive. So a person who only spams cloakers can prevent you from overdriving with your singus.[/q]
|
2 |
This isn't how it works. Someone spamming cloakers [i]does[/i] reduce team overdrive, but that is only because overdrive energy is
|
2 |
This isn't how it works. Someone spamming cloakers [i]does[/i] reduce team overdrive, but that is only because overdrive energy is
|
3 |
{{{
|
3 |
{{{
|
4 |
Team net income * Team current storage / Team storage capacity
|
4 |
Team net income * Team current storage / Team storage capacity
|
5 |
}}}
|
5 |
}}}
|
6 |
There is some fiddling around for players with zero storage, but this is the basic idea. A situation where this much energy is not sent would be a bug.
|
6 |
There is some fiddling around for players with zero storage, but this is the basic idea. A situation where this much energy is not sent would be a bug.
|
7 |
\n
|
7 |
\n
|
8 |
The
equation
above
is
all
we
need
as
far
as
economy
balance
is
concerned.
See
[url=https://zero-k.
info/Forum/Thread/35321?postID=250570#250570]the
design
principal
of
player
ownership
being
irrelevant
to
the
simulation[/url].
The
energy
is
made
up
by
having
each
player
with
positive
net
income
contribute
their
energy
in
proportion
to
their
net
income.
Any
energy
they
cannot
store
overflows
to
the
rest
of
their
team.
I
recall
making
the
overflow
proportional
to
how
much
free
storage
each
player
has,
up
to
a
maximum
of
500.
|
8 |
The
equation
above
is
all
we
need
as
far
as
economy
balance
is
concerned.
See
[url=https://zero-k.
info/Forum/Thread/35321?postID=250570#250570]the
design
principal
of
player
ownership
being
irrelevant
to
the
simulation[/url].
But
on
a
per-player
level,
the
required
energy
is
made
up
by
having
each
player
with
positive
net
income
contribute
their
energy
in
proportion
to
their
net
income.
This
works
because
the
sum
of
the
positive
net
incomes
of
the
players
on
the
team
is
always
at
least
the
net
income
of
the
team.
Any
energy
they
cannot
store
overflows
to
the
rest
of
their
team.
I
recall
making
the
overflow
proportional
to
how
much
free
storage
each
player
has,
up
to
a
maximum
of
500.
|
9 |
\n
|
9 |
\n
|
10 |
The upshot is that if we have the following two person team:
|
10 |
The upshot is that if we have the following two person team:
|
11 |
* Player A has a Singu, full storage, and no expenditure.
|
11 |
* Player A has a Singu, full storage, and no expenditure.
|
12 |
* Player B has empty storage and no energy income or expenditure.
|
12 |
* Player B has empty storage and no energy income or expenditure.
|
13 |
Then half of Player A's income will be sent to Player B. This isn't due to any innate sharing, rather, Player A is only sending half their income to overdrive because the total energy storage of the team is only half full. The extra energy flows to Player B because it has to go somewhere.
|
13 |
Then half of Player A's income will be sent to Player B. This isn't due to any innate sharing, rather, Player A is only sending half their income to overdrive because the total energy storage of the team is only half full. The extra energy flows to Player B because it has to go somewhere.
|
14 |
\n
|
14 |
\n
|
15 |
At least, this is what I recall from when I wrote the latest version, plus a quick glance at the code. I don't mind what the code does as long as
|
15 |
At least, this is what I recall from when I wrote the latest version, plus a quick glance at the code. I don't mind what the code does as long as
|
16 |
{{{
|
16 |
{{{
|
17 |
Team net income * Team current storage / Team storage capacity
|
17 |
Team net income * Team current storage / Team storage capacity
|
18 |
}}}
|
18 |
}}}
|
19 |
holds on a team level, and the energy distribution within teams works on a social level. Someone looking closely at the code could probably find edge cases and bugs.
|
19 |
holds on a team level, and the energy distribution within teams works on a social level. Someone looking closely at the code could probably find edge cases and bugs.
|