I've been doing some testing using the Botched Requisition modifier. Since it adds additional weapons to ALL fighters (allies included), allies can, and will, destroy many targets this way without the player's help. It's hard to say how big a timesave this generally is, but I'm able to consistently beat my PB on Coldwar using Botched Requisition by at least 10s. The caveats are:

• Increased risk of getting shot down
• Benefits are limited to levels with allied fighters, the more the better
• An element of luck exists concerning which weapons your allies get and how well they use them
• The abundance of additional railguns reduces FPS and may increase the risk of a crash

Considering that only negative modifiers are allowed on IL runs, would this be appropriate to use? I feel like this offers a benefit.

Hello everyone! Thanks to the hard work of NitrogenCynic and a little help from myself, we now have an Autosplitter, available here: https://github.com/Hilimii/ProjectWingman_Autosplitter

You may have seen the discussion in the other active thread, but I'm posting it here for visibility. NitrogenCynic has merged the Autosplitter into the main Livesplit branch, so you should be able to download and enable it directly through Livesplit.

Features

• Mission Mode: For running IL mission categories. Auto-starts 1.00s after pressing 'Start' to begin mission. Auto-splits once upon 'Mission Complete'. Auto-resets upon restarts or death.
• Campaign Mode: For running any campaign category. Auto-splits at the end of each mission. Auto-starts upon finalising choice of difficulty. Auto-resets when starting a new campaign.
• Mission Start Splits: Optional. Adds a split to the start of each mission when running in campaign mode. Allows you to compare pace to IL mission runs and accurately measure any golds you clip for submission. Mostly relevant to Mercenary difficulty runs.
• Pausing: Pauses the timer whenever you pause during a mission. Optional.
• Crash Protection: Pauses your timer if the game crashes. Campaign only.
• Tunnel Run Split: An optional split at the end of the tunnel in F59 4 Express Lane.

Got any questions? Ask away! Got any issues? Create an issue on the GitHub link or DM me! Have fun and good luck running!

Hi there!

I’ve been running the Frontline 59 tunnel run category and I think I’ve discovered an issue with UI styles that is affecting times (possibly for runs across all mission based categories too!). Longstory short: Those using legacy UI are suffering a 3.0s time loss at the start of missions because the UI becomes visible 3.0s earlier than those using New UI style. This causes those using legacy UI style to start their timers earlier. I don't believe this would affect campaign runs because the point at which the UI spawns in is irrelevant.

Here’s a video which demonstrates it:

I only noticed this because the tunnel run category is very close and I couldn’t for the life of me work out how I could get a sub 2:31 time, let alone sub 2:29 like FalconLuma. I've been adding 1.60s at the start of my runs to account for untimed acceleration and I figured this might be an issue for other runners too.

Before I discovered this I did some analysis of each run here to try and work out what was going on: https://docs.google.com/spreadsheets/d/e/2PACX-1vQ2DvfbAXI-4Y0BC7Gup30rf-VrxCg9kK3DslBcu_d-PUkm9Uf3sdLIH5PHfQisZTZzsKJX2_OWph1G/pubhtml

My conclusion is that those using New UI style should have +3.0s added to any mission-based runs (such as the tunnel run). There is also a chance that hardware factors in, and we should test this via other runners. Details of which runners in this category need time additions is at the bottom of the sheet link above.

Info: Legacy UI style runs can be identified by their UI spawning in before the world and/or cockpit/plane. New UI style runs can be identified by their UI spawning simultaneously with the world and/or cockpit/plane.