This package includes a script hooking into Mudlet's mapper so you can map by (mostly) just walking around an unexplored area.
It works fairly well on all existing planets. It's based on room vnums, which means it will consider each ship to be fully unique rooms.
### Local System Map
![Image of UI with ground map](https://github.com/rengawm/lotj-mudlet-ui/blob/main/images/system-map.png?raw=true)
When flying in a system, triggers capture radar output and draw a visual representation of the radar, including zooming in/out and updating proximity of each other entity as your position changes.
### Galaxy Map
![Image of UI with ground map](https://github.com/rengawm/lotj-mudlet-ui/blob/main/images/galaxy-map.png?raw=true)
After initializing it by running various in-game commands, this map will show all publicly listed starsystems, including coloring each government's planets differently. It will also attempt to highlight your current system when known, although that only works while in space.
### Chat windows
Certain types of chat content are scraped from the main console and copied into tabbed chat windows for easier history browsing.
After creating a Mudlet profile to connect to LOTJ, do the following to add the package:
1. Open the Mudlet **Settings**.
1. On the **General** tab, check **Enable MSDP**
1. On the **Special Options** tab, check **Force compression off**
1. Download a release of this package (the `.mpackage` file) from the releases page
1. Open the **Package Manager**
1. If present, uninstall the **generic-mapper** package. It conflicts with the one provided here.
1. Select the `lotj-ui-<version>.mpackage` file you downloaded before for installation
1. Restart Mudlet and reconnect. The UI should populate fully once you log into a character.
## Contributing
The source for this package is structured to use [muddler](https://github.com/demonnic/muddler) to package it into a Mudlet package.
You can, of course, just modify the triggers/aliases/scripts directly within Mudlet if you want to test local changes, but they'll be overwritten if you want to update to future versions of this package.
To change the source for this package, modify the JSON files and associated Lua scripts inside the `src` directory, then run `muddler` to regenerate the package. The resulting `.mpackage` file will be inside the `build` directory.
If you have Docker set up, it can be easiest to run a command like this to regenerate the package, from the root of the repository: