Folgende Warnungen sind aufgetreten:
Warning [2] Trying to access array offset on value of type null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Trying to access array offset on value of type null - Line: 14 - File: inc/plugins/cookielaw.php(272) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/cookielaw.php(272) : eval()'d code 14 errorHandler->error_callback
/inc/plugins/cookielaw.php 272 eval
/inc/class_plugins.php 142 cookielaw_global_intermediate
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key "sniplist" - Line: 254 - File: inc/plugins/jsnips.php PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/jsnips.php 254 errorHandler->error_callback
/inc/class_plugins.php 142 jsnips_show_snips
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key "jsnips_file_h" - Line: 256 - File: inc/plugins/jsnips.php PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/jsnips.php 256 errorHandler->error_callback
/inc/class_plugins.php 142 jsnips_show_snips
/global.php 100 pluginSystem->run_hooks
/showthread.php 28 require_once
Warning [2] Undefined array key "master_snippet" - Line: 23 - File: global.php(958) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/global.php(958) : eval()'d code 23 errorHandler->error_callback
/global.php 958 eval
/showthread.php 28 require_once
Warning [2] Undefined array key "last_snippet" - Line: 25 - File: global.php(958) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/global.php(958) : eval()'d code 25 errorHandler->error_callback
/global.php 958 eval
/showthread.php 28 require_once
Warning [2] Undefined variable $unreadreports - Line: 33 - File: global.php(961) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/global.php(961) : eval()'d code 33 errorHandler->error_callback
/global.php 961 eval
/showthread.php 28 require_once
Warning [2] Undefined property: MyLanguage::$bottomlinks_forumteam - Line: 2 - File: global.php(1047) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/global.php(1047) : eval()'d code 2 errorHandler->error_callback
/global.php 1047 eval
/showthread.php 28 require_once
Warning [2] Undefined property: MyLanguage::$ratings_update_error - Line: 5 - File: showthread.php(797) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php(797) : eval()'d code 5 errorHandler->error_callback
/showthread.php 797 eval
Warning [2] Undefined array key "classicpostbit" - Line: 68 - File: inc/plugins/aui.php PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/inc/plugins/aui.php 68 errorHandler->error_callback
/inc/class_plugins.php 142 aui_post
/inc/functions_post.php 885 pluginSystem->run_hooks
/showthread.php 1118 build_postbit
Warning [2] Undefined property: MyLanguage::$post_deleted_error - Line: 21 - File: showthread.php(1617) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php(1617) : eval()'d code 21 errorHandler->error_callback
/showthread.php 1617 eval
Warning [2] Undefined variable $forumjump - Line: 89 - File: showthread.php(1617) : eval()'d code PHP 8.1.2-1ubuntu2.14 (Linux)
File Line Function
/inc/class_error.php 153 errorHandler->error
/showthread.php(1617) : eval()'d code 89 errorHandler->error_callback
/showthread.php 1617 eval




Themabewertung:
  • 0 Bewertung(en) - 0 im Durchschnitt
  • 1
  • 2
  • 3
  • 4
  • 5
Summerevent MWO@OPT - Infos zu den Mechs
#1
Exclamation 
Folgende Trial Mechs können für das Turnier verwendet werden:
[Bild: 0_Trials_zpsta9x2red.png]

Raven
[Bild: th_1_Raven_zpsmp9sjcth.png]
Lore
The Raven was a light-weight electronic warfare BattleMech which, when it first debuted after the end of the Third Succession War, was not just one of the first truly original 'Mech designs produced in centuries, but also represented humanity's refusal to slide back technologically. Originally the Capellan Confederation had attempted to recreate the sophisticated technology once common during the Star League era, specifically the Guardian ECM Suite. While the resulting electronic warfare device was a technical success, it proved too large and bulky to be installed on any existing 'Mechs. Desperate for any force multiplier, the Capellans decided to build an entirely new 'Mech around the electronics, creating the first prototype Ravens.
Many were captured by the Federated Suns during the Fourth Succession War, and the design would languish as just another light 'Mech until the recovery of the Helm Memory Core allowed Hellespont to create a production version, the RVN-3L, equal to the prototype's ambitiousness.
While heavily associated with House Liao, the Capellans were also forced to sell a number to the Free Worlds League and Draconis Combine, the larger share going to the former. The Federated Suns and Lyran Alliance also acquired smaller numbers of Ravens through other means including salvage, and a large number of variants were eventually created.

Tips
Sniper mit ECM, kann nur aus nächster Nähe als Ziel erfasst werden.
TAG deaktiviert allerdings das ECM
Die beiden ER-Larger Laser haben eine hohe Reichweite, sind schön hoch montiern, erfordern kein Vorhalten, sind aber nicht zu übersehen.
Gut geeignet für unbemerktes Aufklären (Ziele erfassen), lenken von indirekten LRM Beschuß (per Teamspeak LRMs auf Target A-L anfordern) und Snipern wenn der Gegner schon unter Beschuß steht.

Wolfhound
[Bild: th_2_Wolfhound_zpsjgiqpyu0.png]
Lore
A light, rugged, and dependable design, the Wolfhound made its first appearance in 3028. Due to their fierce loyalty to House Steiner, the Kell Hounds were the first unit chosen to field test the Wolfhound in combat, followed shortly thereafter by Wolf's Dragoons. The design received its baptism of fire during the Fourth Succession War where it exceeded all expectations and performed brilliantly. This was especially true when the Wolfhound faced its intended targets, hitting the Jenner beyond its ability to return fire while closing the distance on the Panther to get within the minimum range of its primary weapon. With the successful end of the war the Federated Commonwealth ordered larger numbers of Wolfhounds to outfit its military and the design was used again during the War of 3039. Wolfhounds suffered far fewer casualties than other 'Mechs during that conflict and a mere handful fell into the hands of the Combine.

Tips
Schneller Mech mit kurzer Reicheweite der schnell überhitzt, aber hohe Feuerkraft hat.
Den Pulslaser im rechten Arm sollte man auf die rechte Maustaste legen und bevorzugt für Schnellschüße verwenden, die Mediumlaser auf die linke Maustaste und diese nur Feuern wenn man einen sauberern Schuß hat.
Ideal zum killen von Snipern, Scouts und für schnelle Vorstöße gegen geschwächte Gegner.

Phoenix Hawk
[Bild: th_3_PhoenixHawk_zpsqsq5meax.png]
Lore
First introduced by the Terran Hegemony in 2568, the Phoenix Hawk was one of the most well known BattleMechs in the Inner Sphere. The 'Mech began life when Orguss Industries realized that it could reinforce the Stinger chassis to create a larger version, one with the same speed and maneuverability as the Stinger but with superior armor, firepower and electronics. Though not without its own drawbacks, the Phoenix Hawk quickly became the standard by which all other reconnaissance 'Mechs were measured.
Originally a staple of the Star League Defense Force, Phoenix Hawks remained common within the armies of the Successor States after the fall of the Star League. At first Phoenix Hawks were grouped together to form powerful recon lances, but as they started reaching their various deployments, their full potential as command 'Mechs was discovered and many were reassigned to instead lead units of smaller recon 'Mechs.By the middle of the thirty-first century the Phoenix Hawk was still in production at factories on Keystone, New Avalon, Coventry, Jarett and Satalice. Its commonality made it an early candidate for the use of recovered lostech following the Helm Memory Core recovery, and a variety of upgraded variants were produced in time for the Clan Invasion.

Tips
Schneller und stärker gepanzert & bewaffnet als der Wolfshound, zusätzlich mit ECM und Sprungdüsen ausgestattet.
Die drei Mediumlaser im linken Arm sollte man auf die linke Maustaste legen, die drei im rechten Arm auf die rechte Maustaste und diese Waffengruppen nur abwechselnd feuern.
Sind beide Arme ab ist der Phoenix Hawk entwaffen, anders als der Wolfshund der auch Waffen im Torso hat.
Ideal zum killen von Snipern, Scouts und für schnelle Vorstöße gegen geschwächte Gegner.

Kintaro
[Bild: th_4_Kintaro_zpsqiqqolmw.png]
Lore
Introduced in 2587 for the SLDF, the Kintaro was designed with one sole mission: tagging enemy units with a Narc Missile Beacon. As such, it is a 'Mech that is intended to work in a team with a missile-heavy lance.
Unfortunately, the Succession Wars saw the last known Narc factory destroyed in 2792, and the advances made during the Star League era became lostech. The loss of Narc beacons rendered the Kintaro's role unnecessary, and it became just another missile-armed 'Mech. By the Third Succession War the Kintaro was nearly extinct, but in the end was saved when General Dynamics rebuilt a Kintaro factory on Ozawa, though they could only produce the downgraded KTO-18 variant.

Tips
Die LRMs (Long Range Missles) erfordern eine Zielaufschaltung die man auch nicht verlieren darf bis die Raketen einschlagen. LRMs kann man auch auf Ziele aufschalten auf die man keine Sichtlinie hat, dabei sollte man vor allem Ziele auswählen die schon im Gefecht mit eigenen Scouts stehen.
Unter 180 Meter richten die Raketen keinen Schaden an, der ER-Large Laser den der Kintaro als Sekundärbewaffnung trägt hat diese Schwäche nicht und eine hohe Reichweite. Da der ER-Large Laser im rechten Arm verbaut ist sollte man ihn zusammmen mit dem TAG auf die linke Maustaste legen.
Das TAG sorgt dafür das die Raketen schneller aufschalten - auch die von anderen Mechs der eigenen Seite. Allerdings braucht er wie den ER-Large Laser eine direkte Sichtlinie. GeTAGte Gegner sind am Fadenkreuzsymbol zu erkennen - die sollte man als LRM Schütze bevorzugt erfassen wenn kein Scout hilfe benötigt.

Orion
[Bild: th_7_Orion_zpsfvpztzsb.png]
Lore
The Orion was built in 2456 as the first true heavy BattleMech. Originally designed for the Terran Hegemony to maintain its dominance and built on Hesperus II, the Orion is a dependable workhorse design that can handle almost any combat role, thanks to its mix of long- and short-range weaponry and its respectable armoring. After the K model was introduced in 2525 the 'Mech first saw combat during the Reunification War and continued to serve the Star League and its Member States for the next few centuries.

After the fall of the Star League Kali Yama Weapons Industries took over production of the Orion, building new models from their factories on Kalidasa. This left the Free Worlds League as the only producer of new Orions during the Succession Wars, although the other Successor States were capable of building spare parts to repair their 'Mechs, and meant the Free Worlds League Military was the largest Orion user. When Kali Yama merged to create the Kali Yama - Alphard Trading Corporation Orion production was started up on Kendall as well. The League's dominance in new Orions began to change during the Clan Invasion when the Successor States met on Outreach and agreed to work together to combat the Clans. Kali Yama/ATC was among those companies which agreed to sell war materiel, including the Orion, to the other States undergoing Clan attacks. In spite of the design's age it still finds itself utilized extensively on the modern battlefield and new variants continue to be produced.

Tips
Auch der Orion ist mit Raketen bewaffnet, aber die SRMs (Short Range Missles) benötigen keine Aufschaltung. Sie sind schneller als LRMs und machen mehr Schaden, haben aber nur 270 Meter Reichweite. Die Autokanone des Orions haben die gleiche Reichweite, deswegen sollte man beide Waffensystem auf die rechte Maustaste legen.
Auf die linke Maustaste sollte man die Medium Laser legen - auch die haben 270 Meter Reichweite, aber benötigen keine Munition oder Vorhalten und sind deswegen für Schnellschüße geeignet.

Warhammer
[Bild: th_6_Warhammer_zps2bi6fhdc.png]
Lore
The Warhammer BattleMech was introduced by StarCorps Industries in 2515 to be "a mobile 'Mech with enough firepower to destroy or severely damage any 'Mech of the same weight class or lower." In the mission it was designed for, the Warhammer proved to be a very capable 'Mech, and for centuries practically defined the entire class of heavy 'Mechs. Boasting incredible firepower and respectable armoring, the Warhammer served prominently in the Star League Defense Force and was one of the premier 'Mechs in the Gunslinger Program.
After the fall of the Star League, the Warhammer continued to serve in the armies of the Great Houses during the Succession Wars. Its longevity was helped by the large number of Warhammer factories spread across both the Inner Sphere and Periphery, despite relatively low production rates; Ronin Inc. was never able to build more than five Warhammers a year from their Wallis factory. The recovery of the Helm Memory Core would spur on the creation of many new Lostech-using Warhammer variants by Inner Sphere manufactures, while the Periphery continued to build original models for mercenaries and black marketeers.
The design found a new lease on life after the Clan Invasion when StarCorps decided to revitalize the ancient 'Mech with the latest in technological improvements.

Tips
Auch die Lasers des Warhammers benötigen kein Vorhalten. Da die Large Puls Laser aber starke Hitze entwickeln sollte man sie auf eine andere Feuergruppe legen als die anderen Waffen.

Stalker
[Bild: th_7_Stalker_zpsiirv3pmx.png]
Lore
The Stalker was first produced in 2594 as a heavy assault BattleMech for the Reunification War. The engineers and designers at Triad Technologies created the Stalker to be a heavily-armored weapons platform capable of handling combat at any range and absorbing a tremendous amount of punishment. Although among the slowest 'Mechs ever built, the Stalker was still fast enough to keep up with other assault 'Mechs and lead major advances, using its firepower to blast holes in the enemy's lines. Its heavy armor and armament also makes it well-suited for urban combat. Indeed a favorite tactic developed by Stalker pilots was to lay in wait inside a building until an enemy 'Mech passes by, then crash through the wall and emerge onto the street behind them.

For nearly two hundred years, the Stalker remained in service in the Star League Defense Force as a workhorse assault 'Mech until the fall of the Star League, where it continued in the same capacity for another two hundred years in service to the Successor States. It also remained in continuous production during this time for, when Triad Technologies was destroyed in the Succession Wars, both Irian BattleMechs Unlimited and Trellshire Heavy Industries began producing Stalkers at their factories on Shiro III and Twycross respectively. Both the Free Worlds League and Lyran Commonwealth were thus able to maintain the largest number of Stalkers in their arsenals, but still the 'Mech was so common throughout the Inner Sphere and Periphery that some pilots lost their fear of it (at least until they had to face one in combat). Its long career also led to a large number of variants.

Starting in the late 3040s, Irian began utilizing newly-recovered lost technology to update the original design, improving upon its weaponry and armor and increasing its heat management capabilities. These new STK-5M models were fielded in time to take part in the Clan Invasion, although even with their upgrades they were sorely tested by the Clans' OmniMechs. The Federated Commonwealth also produced their own variant, the STK-5S, although this was introduced towards the end of the invasion. New variants would continue to be produced in the wake of the FedCom Civil War, one for both of the split nations, and by Irian in an effort to further keep the design alive.

Tips
Ähnlich wie der Kintaro ist der Stalker ein LRM Mech. Nur mit deutlich mehr Firepower. Auch dieser Mech hat ein TAG, trägt aber als Sekundärbewaffnung mehrere Medium Laser.
Stärker bewaffnet und gepanzert als der Kintaro aber langsamer sollte man mit diesen Mech den anderen schweren Mechs Rückendeckung und LRM Support liefern.
Der Stalker überhitzt recht schnell wenn man mit den LRMs Dauerfeuer gibt.

Mauler
[Bild: th_8_Mauler_zpseufndasq.png]
Lore
This 90-ton assault 'Mech is based on the DCMS-MX90-D Daboku which was first deployed along the Draconis Combine border as early as 3038 in selected DCMS units and codenamed Mauler by Federated Commonwealth forces when first encountered. Because the Daboku turned out a design failure suffering from crippling construction flaws, Luthien Armor Works shelved the Daboku and later adopted the FedCom codename Mauler for its redesigned successor in order to avoid the stigma associated with the earlier shameful failure, effectively treating the Mauler as an entirely new, distinct 'Mech.

Tips
Der Mauler überhitzt nie, selbst wenn man Dauerfeuer gibt.
Die Ultra Auto Cannon 5 (Ultra AC5) feuern mit doppelter Feuerrate wenn man die Maustasten schnell klickt, das kann allerdings auch eine Ladehemmung auslösen. Die Waffen haben eine gute Reichweite, erfordern aber anders als Laser das man ein wenig vorhält.
Ist die Munition verbraucht hat der Mauler nur noch als Ziel und Ablenkung brauchbar, da er keine Sekundärbewaffnung hat.
Ab Besten wird er dazu verwendet um den Gegner direkt zu konfrontieren.
CYNIC, A blackguard whose faulty vision sees things as they are, not as they ought to be. Hence the custom among the Scythians of plucking out a cynic’s eyes to improve his vision.
The Devil's DictionaryAmbrose Bierce
[Bild: sig.php?uid=237]
Zitieren




Benutzer, die gerade dieses Thema anschauen: 1 Gast/Gäste