Light Trains Quickstart Guide - Light-Trains/Documentation GitHub Wiki

Light Trains Quickstart Guide

Welcome to our Discord server! This guide will help you understand how to get started, manage roles, and participate in scouting and running trains.


Roles

  • Joining the Server
    After joining, wait for a staff member to assign you either the Light or Chaos role.

  • Choosing Additional Roles
    Once you have your initial role, head over to the roles channel to pick additional roles like scouter, conductor, and choose a color!


Locations Channel

For Conductors

  1. Check Scheduling
    Before starting, ensure you have checked the scheduling.

  2. Access Locations
    Click one of the available location links.

  3. Copy or Export Routes
    Use the "Copy Routes" or "Export" button (depending on the site) to access the marks.

  4. Use Coordinates
    Echo the coordinates in-game or refer to the Plugins/Macros documentation for easier methods.

  5. Cleanup
    Once done, delete the message corresponding to the server(s) you shouted.

For Scouts

  1. Track Mobs
    Use a tracker to record mob locations. A popular option is Bear Toolkit.

  2. Post Details
    Include the link, expansion, world, and FFA status (if applicable).
    Example:
    ``Bear :7x: Raiden 12/12 FFA``

  3. Remove Embeds
    Clean up your messages by removing any embeds after posting.

  4. Despawn Management
    Delete your message if a server despawns.


Important Expansion Abbreviations

  • 7: Dawntrail (Default if no expansion is specified)
  • 6: Endwalker
  • 5: Shadowbringers
  • 4: Stormblood
  • 3: Heavensward
  • 2: ARR

Bot & Status Changes

  1. Database
    The old spreadsheet has been replaced with a proper database.

  2. Expanded Tracking
    The bot now supports shouting for all expansions using their respective patch number. The bot supports scout tracking for 5-7 (Shadowbringers -> Dawntrail). Lower expansions won't work for scout commands.

  3. No More .cancel
    The .cancel command is removed. Use the new .undo command to remove a status.

  4. New Commands

    • .history shows the last 10 statuses for a server.
    • .undo removes (undoes) a status.
    • .reboot is used for resetting a server’s status when there’s an in-game maintenance reboot.
  5. Expansion Parameter
    Commands that use an expansion parameter no longer accept l. Use the expansion number instead. The default is 7 (Dawntrail).

  6. Time Parameter
    All commands that accept a time parameter allow you to set the time up to 9 days in the past or future using a format like:

    • 13:37-1 (13:37 Server Time yesterday)
    • 12:34+2 (12:34 Server Time the day after tomorrow)
  7. Status Backend
    The new status backend shows the status with the largest (most recent) timestamp as the current status.

    • If you set a status for an older time than a more recent one, it will not appear unless you .undo the newer one.

Scouting and Running Trains (Bot Commands)

Below is a simplified list of our updated bot commands. For more details, you can always use the .help command in Discord.

Command Purpose
.help Shows help and usage info for commands.
.scout Begin scouting a world/expansion. Usage: .scout (world) (expansion?).
.scouted End scouting a world/expansion. Usage: .scouted (world) (expansion?).
.start Start (mark as running) a train. Usage: .start (world) (expansion?).
.end Finish a train. Usage: .end (world) (time?).
.undo Undo a previously set status (like “cancel”). Usage: .undo (statusID?).
.advertise Advertise your train with an auto 10-minute timer.
.advmanual Advertise your train manually (no timer).
.speculate Check the server’s status (spawn times, etc.).
.status View train status for a world.
.history Get the last 10 statuses for a world.
.adjust Adjust the timestamp of a previous status.
.mapping Check mapping data from Sonar.
.health Check the last seen data from Sonar.
.reboot Set a reboot timer after game maintenance.
.sonarcleanup Clean up Sonar data older than specified.
.cleanup Manually clean up statuses older than 7 days.

Note

  • (expansion?) is optional. If omitted, 7 (Dawntrail) is used by default.
  • When providing a time parameter, you can specify exact times plus or minus days as explained above.

Example Workflows

  • Scouting

    1. .sc Zodiark
      (Begins scouting Zodiark for Dawntrail by default.)
    2. .scend Zodiark 5
      (Ends scouting Zodiark for Shadowbringers.)
  • Running & Ending

    1. .start Zodiark 6
      (Marks a Endwalker train as running on Zodiark.)
    2. .end Zodiark
      (Ends the train on Zodiark, Dawntrail by default.)
  • Undoing a Mistake

    1. .history Zodiark 5
      (Shows the last 10 statuses for Zodiark's Shadowbringers, each with an ID.)
    2. .undo 12345
      (Removes the status entry with ID 12345.)

Shout Commands

  • .sh (world) ("message") (expansion): Shouts your train with a 10-minute timer, automatically setting the world to running.
    Automatically appends:
    [World] Hunt train starting (in 10 minutes) at <your message>
    (Conductor: Discord Nickname)

  • .msh ("message") (expansion): Shouts your train with a custom message. No timer is set automatically.
    Automatically appends:
    (Conductor: Discord Nickname)

Tip: In order to include a timer with your .msh command, you can use this site and include it.

After using .sh or .msh, a preview embed will appear. If correct, react with a check mark. A doggospin emoji indicates the message is sending. Your initial message will have a check mark once sent, and the preview will be deleted.


Handling Mistakes

  • Keep Messages
    If something goes wrong, do not delete your messages. This helps Staff troubleshoot.

  • Use .undo
    Use the .undo command to remove or revert a status if you made a mistake.

  • Need Help?
    Unsure how to fix an issue? Ping the @Staff role for assistance.

⚠️ **GitHub.com Fallback** ⚠️