Compare commits
9 commits
Author | SHA1 | Date | |
---|---|---|---|
![]() |
61518e980e | ||
![]() |
3d8f52e7d8 | ||
![]() |
b9af3f297d | ||
![]() |
4b108b8270 | ||
![]() |
e5cfb014de | ||
![]() |
69fff893ee | ||
![]() |
7d42a777de | ||
![]() |
07c9a24529 | ||
![]() |
e82c2058b0 |
4 changed files with 1046 additions and 928 deletions
1955
Dreadnought.xml
1955
Dreadnought.xml
File diff suppressed because it is too large
Load diff
|
@ -6,18 +6,21 @@ An automated aetherhunting system for Lusternia, written in Lua for the Mudlet c
|
|||
Installation
|
||||
----------
|
||||
|
||||
1. Click on the `releases` button above and download the latest `Source Code (zip)` file for the latest Dreadnought release.
|
||||
0. Make sure that the GMCP is enabled before installing. You can double-check by clicking on the `Settings` button within Mudlet, and within the `General` tab there is a checkbox to "Enable GMCP". If not checked off, check that box, click "Save", then restart Mudlet.
|
||||
1. Click on the green button above labeled `Clone or download`. From the dropdown that appears, click `Download ZIP`.
|
||||
2. Extract the zip file somewhere on your computer (such as your Downloads folder).
|
||||
3. Open Mudlet. On the Menu Bar, click on `Package Manager`.
|
||||
4. Click on `Install`, navigate to the folder where you extracted the zip file, and select the `Dreadnought.xml` file.
|
||||
5. Click `OK` to close the Package Manager window.
|
||||
6. Restart Mudlet to make sure all variables are instantiated properly.
|
||||
|
||||
Updating
|
||||
--------
|
||||
|
||||
1. Open up Mudlet's Package Manager.
|
||||
2. Select the `Dreadnought` package and click `Uninstall`.
|
||||
3. See the above Installation instructions.
|
||||
3. Restart Mudlet to clear out all existing variables.
|
||||
4. See the above Installation instructions.
|
||||
|
||||
Documentation
|
||||
-------------
|
||||
|
|
|
@ -3,6 +3,8 @@ Combateer
|
|||
|
||||
The combateer has two different modes: callout and auto, with the difference being how the system acquires targets. In callout mode, the Captain will automatically call out the target and the system will pick it up. Auto mode, on the other hand, will automatically acquire and fire upon targets.
|
||||
|
||||
Once you lock into the turret, the turretting mode is automatically set to `call`ing mode. See below for the exact commands to switch turretting modes.
|
||||
|
||||
It's important to note that the combateer system will automatically target karibideans when they arrive.
|
||||
|
||||
Commands
|
||||
|
|
|
@ -6,7 +6,11 @@ Much of the magic behind the empathing system takes place automatically, without
|
|||
Commands
|
||||
--------
|
||||
|
||||
- `gm` - Sends the `grid modules` command, which is set up to automatically assess the current damage done to each module.
|
||||
- `gr [reset]` - If for whatever reason the repairing process stops, this will restart it. Also, should you give the optional `reset` option, the repairing queue will be cleared.
|
||||
- `gr [all|reset]` - By default, will check and repair any damaged modules as long as they're occupied by someone. Passing in the `all` parameter will repair all modules on the ship, regardless if they're occupied.
|
||||
- `gsliv` - Will check for any slivven infecting the ship and announce their presence upon the ship's aether.
|
||||
- `gc` - Will clarity the command chair at the next available opportunity.
|
||||
- `gc` - Will clarity the command chair at the next available opportunity.
|
||||
|
||||
Crew Commands
|
||||
-------------
|
||||
|
||||
If you're a crew-member, you can trigger the Empath to repair the entire ship by calling out `Repair` on the Ship Aether.
|
Loading…
Add table
Reference in a new issue