The Recon officer herein posts the official list of Hammer related WWW sites. This list is accurate as of 01/06/96. An HTMLized version can be found at http://www.io.org/~bauyeun/phpl.cgi?pages/eh.html. If you have (or know of a) Hammer related page that is not listed here, mail me at bauyeun@io.org so it will be included in the next newsletter.

Two more squadrons have put up WWW pages. Sigma and Vulture squadrons now have their own little space on the WWW, thanks to CEO Dan of Dagger Engineering Corporation.

The URLs are:

If you have or know of a Hammer WWW page that has not yet been mentioned by me in this section, don't hesitate to let me know. Mail me at bauyeun@io.org.

RO

The Recon officer has been putting his time and effort into the creation of a Hammer newsgroup. Preliminary posts have already been posted to alt.config proposing the creation of alt.clubs.emperor's-hammer. If all goes well, the hammer should have it's own newsgroup by the end of the month. (Widespread creation of the newsgroup is not expected for at least 1-2 months after that)

RO

Due to the large number of complaints that the ftp.wustl.edu, the site on which the Hammer's newsletters are stored, is far too busy and impossible to log onto, the Recon officer has discovered a "back door" to the FTP site. The Washington University FTP server is connected to a WWW server, and the two can access each other. So, instead of accessing ftp://ftp.wustl.edu/pub/MSDOS_UPLOADS/tie to download the newsletters, hammer members are advised to use http://wuarchive.wustl.edu/pub/MSDOS_UPLOADS/tie instead, since WWW servers do not have the same user limit as FTP servers do.

For some unknown reason, there has been an alarming increase amount of Rebel communications traffic in this sector. The communications stations on both the Avenger and on the M/CRV Phantom have picked up a flurry of encrypted Rebel communications. In fact, they have even become so bold as to contact some Hammer members via their HoloNet accounts or on Message boards. The Recon officer herein posts the guidelines for contact with rebels:

If a Rebel should contact you via Electronic mail, he/she will almost certainly be doing one of the following:

1. Attempting to con you into becoming a Rebel agent.

-or-

2. Verbally abuse you for being an Imperial.

Case #1:

If a Rebel is attempting to turn you to their side, simply tell them to go bother someone else, or play along with them and find out as much as you can about which organization they are in, and how many are in their group. In either case, after initial contact, report the incident to the Communications Officer and/or the Recon Officer, and send them a copy of the original transmission sent.

If a Rebel begins verbally abusing you, bite back -- although one should attempt to keep the dispute in the spirit of Star Wars. Try not make remarks about their parents, gender, sexual orientation, I.Q, mental/physical state, etc, etc. That is a tactic that they will use. We, in the Imperial navy are above such insults. That is the difference between us and them. In the event that the Rebel continues to harrass you, send them a polite note asking them to stop. If they refuse, report the incident to the Communications Officer, who will also ask them nicely to stop. If this does not work, a letter will be sent to the person's Internet Service Provider, informing them of the misconduct of the Rebel in question.

You have no reason to contact a Rebel. Don't start a flame war because the Rebel will harass you for a long time, and could tarnish the image of the Hammer. Any contact with Rebels (except for responses to flames from Rebels, see above) is forbidden, without expressed consent from a Command Officer.

The Recon Officer and the incoming Flight Officer, AD Yoni are in the process of creating a FAQ (Frequently Asked Questions list) which should be released in the next Newsletter (No. 29). It will be in a searchable Windows Help file, but will probably also be released in text for all you non-Windows users. If you have any questions you have always wanted answered, but were too embarassed to ask, or simply have a list of common questions you hear from other members, don't hesitate to send them in to either myself at bauyeun@io.org, or the incoming FO at LTSaber@aol.com. This FAQ will help cut down on a large amount of mail and questions asked, and which are not currently covered in any of the Fleet manuals.

RO

To:

Grand Admiral Ronin, Fleet Commander, Emperor's Hammer Strike Fleet

Fleet Admiral Adams, Executive Officer, Emperor's Hammer Strike Fleet

Admiral Tav Briel`lya, Tactical Officer, Emperor's Hammer Strike Fleet

Cc: Vice Admiral Doomsday, Communications Officer, SSD Avenger

Subject: Proposed T-72 Starkiller Heavy Blastboat

HoloAttachments: X:\STRFTRS\R&D\EMPIRE\EMPHAMM\T-72\T72DEMO.OVL [Holographic data file]

Message Text:

Gentlemen,

The following is the data for the proposed T-72 Starkiller Heavy Blastboat. Note that is is still in it's development stages. If there is anything we can do to change it, let us know. I believe that Vice Admiral Doomsday has briefed you on our current financial situation. I can only tell you that it is probably as bad or worse than he has stated. I urge you to accept our contract. We have put a lot of effort into developing this starfighter for you. I have attached an OVL holographic data file containing all of the information concerning the T-72.

I hope you make the right decision.

Johl Rantar

Chief Executive Officer, Incom Starfighter Industries

At first glance, the T-72 appears to be a standard TIE Bomber. This couldn't be farther from the truth. While the T-72 was, in fact modelled after the highly successful TIE Bomber spaceframe, it is approximately 3-4 times the size of the TIE Bomber. There are also many structural differences -- for example, the Missile Rack is now mounted under the fuselage. The hull casing which on the T/B contains the Warhead launcher holds the powerful Incom Industries ILc407-r light fusion reactor needed to power the craft, as well as the Vulcan Plasma Pulse Generator.

Role: The T-72 Starkiller has been designed to be a patrol craft, and area defense craft, and support fighter. It has been designed to be specifically coupled with the A-9b Vigilance Interceptor, or TIE Advanced. It's main purpose is as Capital Ship killer. While Missile Boat-type craft would be more proficient at this job, they are limited in efficiency by the number of warheads they can carry, and are not designed for extended duty (i.e: Area defense, engaging multiple targets over a Six-hour period). In addition, the Missile Boat is not cheap. It is probably the most expensive starfighter to produce. The T-72 is an easy to replace craft, and costs about one-eighth that of the Missile Boat, with the same amount of quality. With this reduced cost, the T-72 can also be deployed in large numbers (8:1 ratio vs. Missile Boat), giving them superiority with numbers. Here is how the T-72 would fill the above described roles:

1. Area Patrol -- The T-72 would fill this role by patrolling a large area (such as the Aurora Area) with A-9b's. The A-9b's would eliminate any incursions by enemy fighters, while the T-72 would destroy any Capital ships accompanying the fighters. The T-72's would also supress any missile or laser fire put up by the CapShips, while the A-9b's (or T/A's) would protect the T-72's from fighters while they made their runs.

2. Area Defense -- An Installation such as an X/7 Factory, a Planet (or even a Platform if it has no fighters) that does not have a large fighter compliment has very little defense against enemy Capital ships. They have Turbolasers, but would never stand up to a direct assault from an enemy Capital ship (Such as an MC-80) or the Wing of fighters that can be put up by a ship such as an MC-80. In addition, the Platform could not hit the Capital Ship if it resides just out of range of it's weapons and launches fighters and Warheads. The T-72 would extend the range of the Installation's defenses enormously. Just four T-72's and four escorts would be required to boost the Installation's defenses by 100%. The T-72's would go out and meet the intruders before they got in range, or attack them in concert with the weapons of the Installation.

3. Support Fighter -- The T-72 could easily replace the TIE Dragon in the role of support fighter. In large engagements, the T-72 would single out specific targets (Assault craft such as Transports, Escort Shuttles, Light and Medium sized Capital Ships, or even Large Capital ships if no MISs are available) while fighters perform mop-up. Again, A-9b's or T/A's would be called upon to protect the T-72s.

Propulsion: Because of it's Incredible weight, the T-72 is propelled by two new and extremely powerful Pritt & Whattney 540 KTU Ramjets, very similar to the type found on the IFV-5 System Patrol Craft. The two Ramjets give a total thrust of 1080 KTU, which may seem like a lot, but you must bear in mind that the engines must support the extreme amounts of hull armor, the fusion reactor, and all the separate weapons systems.

Powerplant: In order to accomodate the addition of the P&W Ramjets, the four Vulcan PPGs, and the new Tachyon gun, as well as all of the ships other systems (sensors, life support, etc) Incom reviewed all existing Solar Ionization reactors and, after finding that none of them could generate even half the power needed, Incom was forced to design a new reactor. It was determined that a Solar Ionization reactor could never generate enough power to supply the T-72, in the tiny available space. Undaunted, Incom designed a new fusion reactor to fill the role. While it may be dangerous to carry a fusion reactor on board a craft with no shields due to it's nasty tendancy to explode when hit, this light reactor is different because it contains hundreds of emergency failsafes and is protected by it's own structural integrity field. In addition, the extremely thick armor surrounding it is more than enough to protect it. The final product -- the ILc407-r light fusion reactor...the first starfighter mounted fusion reactor.

The following is the recommended procedure for attacking Capital ships:

1. At >5.0km, open fire with projectiles.

2. Close to 2.5 km, and if warheads are exhausted, open fire with Tachyon Guns.

3. At <1.0km, open fire with PPG, unless Jammer beam is out of comission, in which case continue with Tachyons.

After it was decided that no more power could be squeezed out of the reactor without compromising the offensive systems or speed of the T-72, the proposed shield generators were scrapped, in favour of increased amounts of armor. The armor on the hull varies from in excess of 55 centimetres (~22 inches for those using the Imperial system) at it's thickest points around the fusion reactor and the cockpit, to about 20 centimetres (~8 inches Imperial) at it's thinnest points, around the fins and warhead launcher. If it should be needed, the craft can be fitted with a set of forward/rear projecting shields rated at less than 100 SBD, but would result in the loss of half the missile load. The shields were designed only to protect the ship's stems from strays, and to provide limited protection from capital ship that requires multiple passes to destroy. For example, when a run is made on a large capital ship, such as an ISD, the T-72 closes in on it's target firing it's weapons and jamming the targit with it's jammer beam. When the T-72 passes the target or turns around for another run, the jammer beam is no longer active, as the emitter is in the front. The enemy ship may now fire at will, often taking out/damaging the engines, making the T-72 a sitting duck. The shields were designed to protect the T-72 untill it reached at least 2km from the target.

A storage bay has been made available for the mounting of a beam weapon. It is our recommendation that you leave the slot for a jamming beam, instead of the tractor beam, as it is not likely that this craft will be doing any serious dogfighting due to it's lack of maneuverability. When sending the T-72 on missions, it is imperative that you send heavy fighter escort as the T-72 will not be able to defend itself against anything more maneuverable than a B-Wing.

More details will follow as prototype development progresses.