Auto Server Scripts for VSK5

Auto servers for VSK5, powered by AutoHotkey (AHK), have been around for years, providing a foundation for automated racing. Building on this concept, we have refined and enhanced the scripts, integrating them with Google Apps Scripts and Google Drive. This combination enables automatic scoring, live online leaderboards, and remote control functions that allow players to start or restart races and manage the server remotely.

24/7 Racing for Maximum Flexibility

Designed to run continuously, these auto servers support racing around the clock. They can operate on predetermined time loops or be controlled remotely, making them ideal for players in different time zones. This flexibility allows racers to join at their convenience, whether for casual practice or scheduled regattas. With the ability to run all day, players can familiarize themselves with race tracks before official events, enhancing competition readiness.

Advanced Automation and Customization

Our scripts accommodate a wide range of race formats, from long-distance endurance races lasting over 30 minutes to fast-paced 5-minute time trials. The automation ensures seamless race management, and the integration with Google Apps Scripts takes auto servers to an entirely new level by synchronizing race data with live leaderboards.

Best of all, these scripts are fully customizable, allowing players to tailor the system to their specific racing needs.

Full & Semi Automatic Vsk5 Servers

Our auto servers are divided into two main types: Full Automatic Servers and Semi-Automatic Servers, each designed to meet different player needs and gameplay scenarios.

1. Full Automatic Servers

These servers are designed to run completely independently, providing a seamless, hands-free racing experience.

• Operation:
  Full Automatic Servers operate on a predetermined time loop, allowing races of varying lengths to run continuously (e.g., 5 minutes, 15 minutes, 25 minutes, 35 minutes, etc.).

• Key Features:

  • 24/7 Availability: These servers are always online and require no player input to start or manage races.

  • Automated Race Start: Races begin automatically at the scheduled intervals, ensuring consistent gameplay.

  • Ideal Use Cases: Best suited for casual racing, time trials, and situations where uninterrupted race flow is desired.

2. Semi-Automatic Servers

Semi-Automatic Servers offer flexibility by allowing player control over race management while still running continuously.

• Operation:
  These servers function as "sleep servers"  in lobby mode until activated by a player using the remote control system.

• Key Features:

  • Remote Control System:
    Players with the appropriate password can:

    • Start new races.

    • Restart ongoing races.

    • Reload the next map and begin the race.

    • Return to lobby mode.

  • 24/7 Availability: While the servers are always online, races only start when a player initiates them via the remote control system.

  • Ideal Use Cases: Great for organized events, private regattas, or when flexible race management is required.

Summary

These two server types cater to different needs: Full Automatic Servers ensure continuous, hands-off gameplay for consistent racing, while Semi-Automatic Servers provide control and flexibility for players to manage their races on demand. Both server types are available around the clock, supporting a wide range of gameplay scenarios.

Step 1: Download the Time Sync Server & Track Pack

The pack includes:

• AHK script (sleepserver.ahk) – Automates race transitions by loading and starting the next race.

• 96 AC50 race tracks – Each track has a predefined start time in 15-minute intervals, beginning from 00:00:00 (midnight) to 23:45:00. This is required for a full 24 hour cycle.

Step 2: Set Up the Track Rotation in VSK5

1. Launch Virtual Skipper 5 (VSK5) and start hosting a server.

2. When selecting tracks, start with the track whose scheduled start time is 15 minutes before your intended first race.

3. Continue adding each track in numerical order until all 96 tracks are loaded.

Step 3: Configure Windows Task Scheduler

To automate the script execution at precise time intervals, follow these steps:

1. Open Task Scheduler:

   • Press Win + R, type taskschd.msc, and hit Enter.

2. Create a New Task:

   • In the Actions pane, click Create Basic Task...

   • Name it something like "VSK5 Auto Server"

3. Set the Trigger (Schedule the AHK Script Execution):

   • Choose Daily and set the start date and time.

   • The start time must be 16 minutes and 2 seconds before the first race (e.g., for a 12:00:00 race, set the trigger to 11:43:58).

   • Click Next and select Repeat every 15 minutes for 24 hours.

4. Set the Action (Run the AHK Script):

   • Select Start a Program

   • Browse to locate the "sleepserver.ahk" script.

   • Click Finish to save the task.

Step 4: Start the first race and monitor the server

• Start the first race on your server. Let this race cycle through and wait for Windows Task Manager to start the next race exactly on time.

• The AHK script will automatically execute every 15 minutes, ensuring each race starts exactly on time.

• To stop the server, disable the task in Task Scheduler and close VSK5.

Now your server will run 96 synchronized races per day, keeping all start times precisely aligned to real-world time! 

COMING SOON

Description

1. Batch Files

   • What They Do:

     • Monitor text files in a Google Drive folder for new commands sent from the Google Web App interface.

     • When a command file is detected, the batch file triggers the corresponding AutoHotkey (AHK) script to execute the required server function (e.g., start, restart, load new map).

   • Purpose: Serve as the connection between the command folder and the AHK scripts, automating server actions.

2. Google Apps Script

   • What It Does:

     • Listens for user commands submitted via the web interface (Google Web App).

     • Saves these commands as files in the monitored folder for the batch file to process.

   • Purpose: Acts as a listener and command handler for user input from the web interface.

3. HTML Document

   • What It Does:

     • Provides the web interface (Google Web App) for users to send commands like starting or restarting a race.

   • Purpose: Offers a simple, browser-based interface for interacting with the remote control system.