Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Delete previous core mods on update #81

Closed
GeckoEidechse opened this issue Jan 8, 2024 · 3 comments
Closed

Delete previous core mods on update #81

GeckoEidechse opened this issue Jan 8, 2024 · 3 comments

Comments

@GeckoEidechse
Copy link
Member

Introduction

To my knowledge VTOL currently simply overwrites existing files on Northstar updates. While this has been fine so far in terms of update stability, it is somewhat limiting for upstream Northstar.

In particular, given our past recommendations of simply overwriting files when updating we could never ship an update that removes a script source file for one of the core Northstar mods (Northstar.{Client,Custom,CustomServers}) again.
This made development somewhat cumbersome as adding any script file had to be carefully considered due to not being able to remove said file again once shipped.

As such our recommendations for (manually) updating Northstar have since changed to first clearing existing Northstar.* mods folders and only then adding the new script files from the release.
(Similarly FlightCore was also updated accordingly.)

This finally allows upstream Northstar to push out an update that also removes script files from core mods again.

How VTOL falls into this

Given that a large chunk of Northstar players use VTOL to maintain their installation, I'm hoping VTOL can follow suite on this, so that we can ensure that no players encounter any issues on future updates that might remove script source files again.

Note that we don't have an exact time frame on when such an update might release, however it's probably best to already have the change in VTOL implemented and shipped in order to avoid any stress once such an update should hit ^^

TL;DR

Before extracting a new update into Titanfall2 folder, delete any existing Northstar.Custom, Northstar.Client, and Northstar.CustomServers folders in the mods directory.
For future proofing (e.g. when Northstar.Coop surely releases one day), it's probably to even just delete all Northstar.* folders in the mods directory before applying an update.

@BigSpice
Copy link
Collaborator

on it

@BigSpice
Copy link
Collaborator

finished

@BigSpice
Copy link
Collaborator

finished

image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants