Hola Javier



si Talandir al final no acepta el hueco en tu partida, yo también estaría
interesado.

Ya me dirás como queda el asunto.



saludos

Fran.



_____

De: vgaplanets@yahoogroups.com [mailto:vgaplanets@yahoogroups.com] En nombre
de Javier Sedano
Enviado el: martes, 10 de junio de 2008 21:06
Para: vgaplanets@yahoogroups.com
Asunto: [vgaplanets] Hueco en partida



Ni siquiera sé si la lista sigue viva, porque de vez en cuando me llegan
correos del "área de ficheros", pero no veo moviento... en fin...

Tengo un hueco para una partida.

-PHost, PList3.1, universo pobre
-Versión registrada
-PLS (revisar el archivo de la lista y el adjunto, si llega, para más
detalles; básicamente, el número de planetas que posees indica cuántas
naves puedes tener; por lo tanto, no hay ni habrá cola de construcción)
-Turno 29 (256 naves construidas)
-Raza 2. Va 9ª en los scores, con 12 capitals, 10 cargueros, 40 planetas
y 1 base. No sé cuán buenas son las naves, porque también soy jugador y
no quiero mirar lo que tiene, pero no creo que sea tan catastrófico como
parece (por ejemplo, los pájaros tiene básicamente lo mismo y van en 4ª
posición... pero tienen 4 bases; o los cylons van 3º, y también tienen
un número parecido de naves). Ver el adjunto, si es que llega. El
jugador dice que lo deja por falta de tiempo

Si hay algún interesado, que me mande un email.

Saludos,
J

----------

PLS (Planet Limits Ships)
-------------------------

An addon for PHOST, the VGAPLANETS portable host (http://phost.
<http://phost.de/> de/)

THE 500 SHIPS LIMIT

If you are new to VGAPLANETS, you neeed to know that, once there are 500
ships in game, no more ships can be built (phost may raise this limit to 999
ships, but the limit is still there). Once a ship is destroyed (usually in
combat, or using the mission Colonize), a "ship slot" is freed and a new
ship can be built.

But... who builds that new ship? All the 11 players want to do so.

Phost provides several mechanism to determine it: PBQ, PAL, FIFO,... neither
of them are a real solution. Read about those queue mechanism in the phost
documentation.

PLS

PLS is an addon which, instead of giving 500 ships for the 11 players, gives
each player a number of ships slots equal to the number of planets he
controls (in fact, the number of slots is equal to the number of planets the
player controlled _last_ turn). VERY IMPORTANT NOTICE: contrilling a planet
is not the same than owning it; see below.

This way, the game does not need to decide who builds next: you can only
build if you have a free slot. Beautiful.

This is supposed to provide:

-A fairer distribution of the ships in the game, since larger empires will
get more ships. As in many other strategy games. As in real life.

-A more aggresive game, since players will tend to fight to conquer more
planets, and own more slots.

-A more aggresive game, since players will not mind to lose a ship in combat
(if they have a slot and a strong economy, it will be built again).

-Added value for planets, even amorphous or 99 degrees planets.

-More ships to be usable, since players will not build yunk just to fill
slots.

-Stronger ships, since in the late game players will destroy weak ships to
build stronger carriers and battleships.

In summary, a funnier game.

RULESET

[CONFIGURABLE] means that the default value is shown here, but the hoster
may choose another value; ask for the pconfig.src configuration file to your
hoster.

-PLS will do nothing at all until 450 ships [CONFIGURABLE] exist in the
game. However, it will send information messages to the players from the
begining, containing the number owned planets, the number of controlled
planets and the ships limit.

-Owner of a planet vs. Controller of a planet: the controller of a
planet is the player that, in the last 9 turns [CONFIGURABLE], owned the
planet for most turns.

-Ship-limit: the number of ships you can own is the number of planets you
controlled at the end of the previous turn, modified by the RaceBalance
parameter (see below). A minimum of 1 ship [CONFIGURABLE] is allowed, even
if you control less planets.

-TransferOwner stage: if player is using "give ship" or "gsX" friendly code,
the receiving player MUST use "rsX" friendly code in the receiving planet or
ship. Otherway, the ship is returned back to the previous owner.

-BaseMissions_1 (Force Surrender), Combat and BoardingParties stages: if a
captured ship takes a player above the limit, the ship may be _destroyed_
[CONFIGURABLE] (in ship ID order; lower IDs are destroyed first). Default
behaviour is not to destroy the ship, but the hoster can change it.

-Before ShipBuilding_1 and ShipBuilding_2 stages: two actions are taken.
1) If the number of owned ships is above the limit, some of them are
destroyed. Ships are choosen to be destroyed by:
1) PDx friendly codes [CONFIGURABLE] in order (PD1 to PD9 for
PriorityDestroy1 to PrioriryDestroy9).
2) At random or by "battle order" (that is, lower battle orders are
destroyed first) [CONFIGURABLE, default to Random].
EXCEPTION: if a fuelless would be choosen to be destroyed, it is actually
choosen only with 20% probability [CONFIGURABLE].
2) Build orders that would take the player above the limit are removed
from the build queue in "battle order" order (higher "battle orders" are
kept).
NOTE: clone orders are only accepted during ShipBuilding_1, ignored during
ShipBuilding_2.

RACE BALANCE

PLS can be configured so each different race has a different "adjustment
coefficient" for the relation slots/planets. It is used to favour some races
that may need more ships to be competitive.

The default value is 100,100,100,100,100,100,100,100,100,100,100 , which
meand that every race gets 100 ship slots for every 100 controlled planets.

Ask your hoster for the configuration file so watch this balance.

WHAT DO I HAVE TO DO?

Nothing. Just act knowing about this ruleset. It does not need client
support.

[Se han eliminado los trozos de este mensaje que no contenían texto]





[Se han eliminado los trozos de este mensaje que no contenían texto]