|
Mekton Zeta to SilCore Conversion Notes |
|
|
|
|
Written by Wil
|
|
Friday, 02 November 2007 |
|
The following are very loose notes for converting Mekton Zeta designs to SilCore. Because of the flexibility of both design systems, some amount of judgment has to be used to insure the design keeps in the spirit of the original.
- Target size is determined by reversing the formula on pg. 77 of the
SilCore Deluxe ([cube root of mass]/3)-0.5, based on the listed Mekton Zeta weight.
- Armor Rating is determined by taking the average armor protection,
in Kills, of the Mekton Zeta design and multiplying it by 125 to get the equivalent
thickness in mm, then taking the square root of that to obtain the Armor
Rating.
- Crew size should already be known, unless a variant is being built
that has more or less crew.
- Movement Systems can be converted straight over using the listed kph
speed (if not unlisted, or unsure how to obtain this, consult the Speedlines
table on pg. 64 of Mekton Zeta). KPH speeds can be rounded to obtain even MP
values. Most Mekton Zeta thruster systems will translate to both Flight and Space movement modes in SilCore,
dividing the MA of the MZ unit by 8 to get the Gs of acceleration for
SilCore Space MP. Thrusters normally have no stall speed in Mekton Zeta, although
one can be assigned (especially for Astrofighter forms). GES systems are
Hover unless it has been kludged to represent something else, such as
wheels.
- Maneuverability should be determined by getting a feel for the vehicle's
design. In general, taking a slightly higher maneuver rating (by two or three) than the
Mekton Zeta Maneuvera Value should do fine.
- Deployment Range & Reaction Mass can use the fuel range in km
of the MZ unit, but it may be better to tweak this according to the unit's
design parameters. The same goes for Burn Points...although Mekton Zeta mecha can technically
operate in both atmosphere and space, some were never intended for space
use and it may be better to not assign any Burn Points for them. A good rough guide is for Burn Points to be between 1/2 and 3/4 the deployment range. The fuel type used is completely
dependent on the Mekton Zeta setting that the unit is being brought from, though
most fusion or plasma thrusters will use light or very light gases.
- Sensors can be a sticky point. Generally the listed sensor range from Mekton Zeta can
be used, with any bonuses depending on the Recon Systems installed. Generally
I would give a +1 each for ASP, Gravity Lens and Magnetic Resonance Lens;
combos of any other system might also rate a bonus. Remember that in SilCore the sensor and commo range is greatly increased in the air and in space...spotting
radar as listed in Mekton Zeta <em>greatly</em> increases the value in SilCore. How
this affects the sensor range in the SilCore vehicle will depend on
the vehicle's mission. Aquatic sensors should have their range set according
to the designer's wishes...this will almost always be lower than the mecha's
regular range. Given the increase in sensor ranges for air and space, I
have taken to dividing the listed commo range listed by 10 or 100 depending
on what purpose the Mekton Zeta mecha was originally designed for. Commo bonuses
will likewise depend on the unit's mission.
- Perks & Flaws should be determined based on observations from
the Mekton Zeta design. Neural links (such as in Starblade Battalion) that don't rate any special
cockpit systems in Mekton Zeta may still be worth a Mind Link Thought Interface system.
A mech with one location more heavily armored than the rest may rate reinforced
location armor or some such (the same applies for a design that had weaker
armor in one or more location). Humanoid mecha that fly often have the
Flaw Cannot Glide and possibly a Maximum Ceiling.
- Offensive and defensive systems are a fairly straightforward conversion. The Damage Multiplier can be determined the same way as for armor above, and can be subject
to some tweaking by the designer based on what the characteristics of
the weapon will be in SilCore.
|
|
Last Updated ( Sunday, 04 November 2007 )
|