SlipChat

Trigger the in-game custom order feature via a local API

Listens for an HTTP request and, after validating the message and other checks, sends a custom order to your crew!

Send a GET request to http://localhost:8001/sendchat?message=Hello%20World to trigger an announcement of "Hello World" in-game.

In addition to raw HTTP requests, there is also a Stream Deck Plugin to make custom orders. You can download it from the Elgato Marketplace or use the manual download button. Inside the zip should be a file ending in .streamDeckPlugin you can use to install the plugin. The default settings should work, just need to add a message.

Current requirements to send a custom order:

• Must be Captain or First Mate of the ship.
• Must be at the Helm station.

In addition, you can use special $variables to automatically replace these with values from in-game:

Crew Variables:

• $captain: The display name of the Captain
• $randomCrew[id]: A random crew member's name, replace [id] to keep it consistent in the message (ex $randomCrew1)
• $crew[id]: The crew member with that numeric id, replace [id] with a number (ex $crew0)

Fight Variables:

(These will be blank if no fight is occurring)

• $enemyName: The name of the enemy ship
• $enemyIntel: The intel of the enemy ship
• $enemyInvaders: The invaders from the enemy ship
• $enemyThreat: The threat level of the enemy ship
• $enemySpeed: The speed of the enemy ship
• $enemyCargo: The cargo of the enemy ship

Run Variables:

• $campaignName: The name of the campaign (ex Pluto)
• $sectorName: The name of the sector (ex Pluto Outskirts)

Misc Variables:

• $version: The version of MoCore (for debugging purposes, no real purpose)

v1.0.1

Updated to MoCore v2.0.2, which means the default port has changed to 8001. The defaults in the Stream Deck plugin have been updated to match, but existing actions will need to be updated to use the new port.

The path has also changed to /slipchat/sendchat, so the new URL to send a message is http://localhost:8001/slipchat/sendchat?message=<insert message here>.

v1.0.0

First major release!

Updated to support the latest game version.

v0.1.1

Updated to support First Mate sending orders, and marking as compatible with the v1.90.0 update.

Also added MoCore to enable the ability to manage compatible versions without having to make a new release every time.

Known Issue

• If the first mate and captain are both on the helm (so the first mate cannot see the helm screen) they can still send messages.

v0.1.0

Initial (Testing) Release!

I got it working! Time to get it in the hands of the community so they can break it.

Check the main README page for for a list of everything you can replace in a message using variables.

I have not had time to test every single variable and I'm sure there's something that will break, but I feel it's ready enough for people to start coming up with ideas on how to use it.

For this test I've setup two easy ways to send announcements:

Stream Deck Plugin

If you click the "Manual Download" button to download the zip file, inside should be a file ending in .streamDeckPlugin you can use to install the plugin. Most of the default settings should work, just need to change the message.

Streamer.bot / MixItUp / HTTP request

You can make a get request to http://localhost:8002/sendmessage?message=<insert message here> to attempt to send a message. This is also called "Fetch URL" in Streamer.bot.

An easy idea for inspiration: Combine with SlipStreamer.Bot's existing actions StartFight for automatic announcements of fight information. (Remember Streamer.bot does not need you to be live for things to run. Offline ships could do this too.)

Known Issues:

• If you use a varible such as $captain but include anything else after (ex: Hello $captain! or Hi $captain.) then the variable will not work.