BattleDamage

From Elite Wiki
Revision as of 15:42, 1 May 2012 by Smivs (talk | contribs) (New page-first draught)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Overview

A player's damaged Smivs' Python heads for the system Main Station for urgent repairs

Battle Damage OXP

This OXP adds an immersive factor into the game. When your shields are gone, your opponents' lasers are directly hitting your hull, but in the 'core' game this has no obvious impact or repercussions. This OXP adds this 'realism' into the game by causing damage to your ship's hull, which if not repaired promptly will lead to problems such as fuel leaks and mis-jumps. If you take an un-shielded hit, a console message will alert you to the fact with a warning:- 'WARNING! HULL DAMAGE' and further hits will be notified with another console message:- 'Hull taking further damage'. Upon docking, someone will point out this damage to you and urge you to have emergency repairs made at the Ship Outfitters (F3). Here you will find 'Emergency Hull Repairs' offered for 75Cr. These repairs are fairly basic and consist of new Duralium plates welded over the damaged areas to ensure structural integrity and airtightness where needed. Repairs will take around six to eight hours of game time, after which your ship will be spaceworthy again. If you are offered a Maintenance Overhaul, this WILL include any emergency repairs. 'Emergency Hull Repairs' will also be offered, so you can still make repairs even if you wish to defer the Overhaul at this time. Choose one or the other. Any damaged equipment will need to be repaired seperately. If you do not have repairs made, you may experience mis-jumps or fuel leaks as a consequence of the damage. If you launch damaged the station staff will sometimes overlook this if the damage is not too severe although you may be reminded about the damage when you next dock. Sometimes the station you are leaving will point out the damage but let you go on your way, or you may encounter problems on launching and be urged to re-dock immediately for repairs, and you might even get a telling-off from one of the Dock officials and a small fine.

Full details and screenshots can be found on Smivsonline.

Extra notes for the 'forSmivses' edition.

This OXP will work with both 'Add' and 'Replace' versions of Smivs'Shipset v4.1.2. As well as the features above, this version also adds visible damage to the player ship if it is one of the Smivs'Shipset core ships*. Your ship will appear damaged as soon as it takes an un-shielded hit and will remain damaged until repairs are made.

If you are flying a Cobra Mk III with a custom texture made using the 'kit' supplied with Smivs'Shipset, you will need to make a 'damaged' version of your custom texture. Make a copy of your custom texture and open it in your image editing software (Gimp, Photoshop etc). In this OXP's Textures folder you will find an image file called "damage-overlay.png". Drag and drop this onto the copy of your custom texture. Save the result as 'smivs'-player-cobra3-damaged.png'. You will find a file with this name already in the 'Textures' folder of this OXP. This is the default blue player Cobra. Either remove this and keep it somewhere for future use and move your new texture into the Textures folder, or over-write/replace it with your new texture. This will then allow you to see the damage on your own custom ship. This is only necessary for custom-textured Cobra 3s, all other player ships will use the in-built 'damaged' textures from Smivs'Shipset.

Installation

The download file contains two versions of Battle Damage OXP. Read the information notes before installation.

If you fly a ship from Smivs'Shipset, use the 'forSmivses' version, if not use the Universal version. Place the appropriate .oxp folder in your Oolite AddOns folder.

Licence

This work is licensed under the Creative Commons Attribution-Noncommercial-Share Alike 3.0Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-nc-sa/3.0/ or send a letter to Creative Commons, 171 Second Street, Suite 300, San Francisco, California, 94105, USA.

Author

The OXP was developed by Smivs.

Download

here.

Credits

Many thanks to Capt. Murphy for suggestions, help and advice on the code and scripting, and for testing. Thanks also go to Commander McLane and Cim for further good advice, and to Solonar for testing.

Oolite Forum thread

Any questions, problems or bug reports should be posted on this OXP's BB thread here