Asteroid Storm

From Elite Wiki
Revision as of 14:44, 10 January 2010 by JazHaz (talk | contribs) (Overview & Download Link: added note about the current version not working in 1.74+)

Overview & Download Link

Large asteroids can provide rich pickings for miners.

This OXP adds more models and textures for asteroids to the game. The graphics for the new types of asteroids are based upon asteroids in the Real Life Sol System.

Some of the new types of rocks are really big, requiring a sustained laser volley to pulverize and are marked by your ID computer as a "Large Asteroid". In the native game there are two types of asteroid. If you play with this OXP installed then more variety is added to the shapes and sizes of the asteroids you encounter as they have 15 different textures and models. The chance and number of boulders being formed when an asteroid is destroyed also varies for each type of asteroid.

The OXP also adds an asteroid related mission, well suited to a novice commander in Galaxy 1. You are docked at a station near Lave, in a system well known to suffer from asteroid storms. Sure enough, as you drop off your cargo, you hear the sound of small asteroids glancing off the Station's shields. Suddenly all hell breaks loose, Commanders running for their ships leaving their cargo behind!

A vast asteroid has been detected approaching the Station. It is so massive that if it strikes, destruction of the mighty Dodec is certain. Will you stay and help or get out of Dodge? The mission has three possible endings depending on your actions. The mission will trigger when you are docked at a certain system within 7 light years of Lave and are ranked at least "Above Average". Checking your F7 screen will give you a clue as to where the mission takes place.

The OXP was scripted by LittleBear, featuring new asteroid models and textures by Charlie.

Version 3.52 is an updated version to work with Oolite 1.72.1+. (It will also work with 1.65 and 1.71 but none of the other versions). Note: this version will stop working in Oolite v.1.74+.

Asteroid Storm 3.52 Updated to V3.52 on 22th February 2009.


Asteroid Mining Tips

An asteroid can be destroyed with any weapon and a small bounty is paid by GalCop for ridding the space lanes of a navigational hazard. When an asteroid is destroyed it often splits into chunks of rock, identified by your ID computer as a “boulder”. These boulders are too large to fit through the mouth of a Fuel & Matter Scoop. Commanders who merely vaporise boulders are however missing out on a potential source of wealth. Canny Commanders cut "boulders" into “splinters” and scoop them!

This is where a Mining Laser comes into its own. Fire on a boulder with a combat laser and you are likely to vaporise it. A Mining Laser will however cut the boulder into “splinters”, which are small enough to be scooped with a Fuel & Matter Scoop. An Ore Processor is highly recommended to extract the most valuable materials from the splinters scooped.

Standard Mining Guild procedure is to fit a Mining Laser to the starboard or port view. First fire on the asteroid with your fore mounted combat weapon to weaken it. Then use your Mining Laser to split the asteroid into boulders. Cut the boulders into splinters with your Mining Laser, and these small chunks of rock can be dredged aboard with a Fuel & Matter Scoop. If you have an Ore Processor fitted, the materials from the splinter can be further refined.


Difficulty Rating

"Noob". The new asteroids are no more a threat to the player than standard asteroids; the OXP just adds a greater variety to the graphics and makes some asteroids more valuable to mine. The mission featured by the OXP should not put a young Jameson in any great danger, although to complete the mission you would probably need a Beam Laser or better and a couple of Standard Missiles.


Update Notes

Version 3.45 is an updated version over the version on Oosat2, fixing a few minor bugs, adding new features, and enhanced scenarios for Oolite 1.70 and above using Javascript. Commander Eric Walch’s mission clash prevention code is added to make sure the OXP does not clash with other OXPs which display mission briefing screens. Texture name files are also re-named (so as to avoid a case-sensitivity bug on Unix). Displaced small asteroids can be seen whizzing though the spacelanes of the system suffering from "deadly asteroid storms" and a greater than average number of asteroids also appear in this system, making a trip to it a little more worthwhile for miners.

Version 3.46 is a further updated version which fixes a bug. In the previous version only the Large Asteroids had a role. This meant that only these appeared in game (oops)! On the old version, only one new type of asteroid was added even though the OXP has the graphics and models to add 12 different types. The new version now works as intended and you will see a greater variety to the shapes and sizes of all asteroids in the Ooniverse. Only the graphics are changed, rocks are still rocks! With this version all of Charlie's asteroids now appear, rather than just one of them.

Version 3.50 is adapted to work with version 1.71 and with 1.72.1+ (version 1.72.0 is excluded and will give a warning). No change in functionality but previous versions will not work with 1.72 anymore.


Installing and Playing

To play the OXP, unzip the download file. This will create a folder named "AsteroidStorm3.50". Open this folder and you will see a folder named "AsteroidStorm.oxp" and a readme. Move the AsteroidStorm.oxp folder to AddOns. As with all OXPs, it’s the folder ending .oxp that you need to put in Oolite's AddOns folder, otherwise Oolite will not read it.

If you are updating from an old version of Asteroid Storm OXP, then the first time you load up Oolite after installing hold down the SHIFT key until you see the rotating Cobra Mk III on the start screen. This ensures that Oolite’s cache is updated.

This OXP is compatible with Oolite 1.65 and 1.71 or above. You can still play Asteroid Storm on Oolite 1.68 till 1.70, by changing a file inside the OXP's folder. Please follow the instructions in the included readme.